Re: [PATCH] hw: add a number of SPI-flash's of m25p80 family

On 8/11/20 10:37 PM, Igor Kononenko wrote: > Support a following SPI flashes: > * mx66l51235f > * mt25ql512ab > > Signed-off-by: Igor Kononenko > --- > hw/block/m25p80.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/hw/block/m25p80.c b/hw/block/m25p80.c > index 8227088441..bf1f8337

Re: [PATCH] hw/vfio/pci-quirks: Fix broken legacy IGD passthrough

On Wed, Jun 10, 2020 at 3:17 PM Laurent Vivier wrote: > Le 10/06/2020 à 09:50, Thomas Huth a écrit : > > On 10/06/2020 09.31, Philippe Mathieu-Daudé wrote: > >> On 6/10/20 5:51 AM, Thomas Huth wrote: > >>> The #ifdef CONFIG_VFIO_IGD in pci-quirks.c is not working since the > >>> required header co

Re: [RFC v3 1/1] memory: Skip bad range assertion if notifier supports arbitrary masks

On Wed, Aug 12, 2020 at 4:24 AM Jason Wang wrote: > > > On 2020/8/12 上午1:55, Eugenio Pérez wrote: > > Signed-off-by: Eugenio Pérez > > --- > > hw/virtio/vhost.c | 2 +- > > include/exec/memory.h | 2 ++ > > softmmu/memory.c | 10 -- > > 3 files changed, 11 insertions(+), 3

[PATCH 13/13] hw/usb: Add U2F device autoscan to passthru mode

This patch adds an autoscan to let u2f-passthru choose the first U2F device it finds. The autoscan is performed using libudev with an enumeration of all the hidraw devices present on the host. The first device which happens to be a U2F device is taken to do the pass-through. Signed-off-by: César

[PATCH 00/13] Introduce USB U2F key device

This patch series adds the U2F dedicated support to Qemu through a USB U2F key device that can operate in two modes: pass-through and emulated. This work is also part of the GSoC program of this year and follows the proposal I made for the 'Virtual FIDO2/U2F security key' subject, suggested and me

[PATCH 02/13] docs: Add USB U2F key device documentation

Add USB U2F key device documentation: - USB U2F key device - Building - Using u2f-emulated - Using u2f-passthru - Libu2f-emu Signed-off-by: César Belley --- docs/u2f.txt | 101 +++ 1 file changed, 101 insertions(+) create mode 100644 docs/u2f.txt

[PATCH 03/13] hw/usb: Add U2F key base class

This patch adds the specification for the U2F key base class. Used to group the common characteristics, this device class will be inherited by its two variants, corresponding to the two modes: passthrough and emulated This prepares the U2F devices hierarchy which is as follow: USB device -> u2f-ke

[PATCH 05/13] hw/usb: Add U2F key passthru mode

This patch adds the U2F key pass-through mode. The pass-through mode consists of passing all requests made from the guest to the physical security key connected to the host machine and vice versa. In addition, the dedicated pass-through allows to have a U2F security key shared on several guests w

[PATCH 01/13] hw/usb: Regroup USB HID protocol values

Group some HID values that are used pretty much everywhere when dealing with HID devices. Signed-off-by: César Belley --- hw/usb/dev-hid.c | 26 +++--- hw/usb/dev-wacom.c | 12 +++- include/hw/usb/hid.h | 17 + 3 files changed, 27 insertions(+),

Re: [PATCH 1/2] migration: unify the framework of socket-type channel

* Longpeng(Mike) (longpe...@huawei.com) wrote: > Currently, the only difference of tcp channel and unix channel in > migration/socket.c is the way to build SocketAddress, but socket_parse() > can handle these two types, so use it to instead of tcp_build_address() > and unix_build_address(). > > Th

[PATCH 08/13] configure: Add USB U2F key device

Signed-off-by: César Belley --- configure | 27 +++ 1 file changed, 27 insertions(+) diff --git a/configure b/configure index 2acc4d1465..3ea5e561ff 100755 --- a/configure +++ b/configure @@ -447,6 +447,7 @@ trace_file="trace" spice="" rbd="" smartcard="" +u2f="" libu

[PATCH 04/13] hw/usb: Add U2F key base class implementation

This patch adds the U2F key base class implementation. The U2F key base mainly takes care of the HID interfacing with guest. On the one hand, it retrieves the guest U2FHID packets and transmits them to the variant associated according to the mode: pass-through or emulated. On the other hand, it p

[PATCH 10/13] docs/qdev-device-use.txt: Add USB U2F key to the QDEV devices examples

Signed-off-by: César Belley --- docs/qdev-device-use.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/qdev-device-use.txt b/docs/qdev-device-use.txt index f8d0d2fe29..9889521e3c 100644 --- a/docs/qdev-device-use.txt +++ b/docs/qdev-device-use.txt @@ -325,6 +325,7 @@ The new way is -de

[PATCH 06/13] hw/usb: Add U2F key emulated mode

This patch adds the U2F key emulated mode. The emulated mode consists of completely emulating the behavior of a U2F device through software part. Libu2f-emu is used for that. The emulated mode is associated with a device inheriting from u2f-key base. To work, an emulated U2F device must have dif

[PATCH 07/13] hw/usb: Add U2F key build recipe

Signed-off-by: César Belley --- hw/usb/Kconfig | 5 + hw/usb/Makefile.objs | 7 +++ 2 files changed, 12 insertions(+) diff --git a/hw/usb/Kconfig b/hw/usb/Kconfig index 5e63dc75f8..3fc8fbe3c7 100644 --- a/hw/usb/Kconfig +++ b/hw/usb/Kconfig @@ -96,6 +96,11 @@ config USB_STORAGE_MTP

Re: [PATCH 06/11] tests/Makefile: Add $(EXESUF) to fp-test target

On 04/08/20 19:00, Thomas Huth wrote: > In case we ever want to compile this for Windows, we need the $(EXESUF) > here. > > Signed-off-by: Thomas Huth > --- > tests/Makefile.include | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tests/Makefile.include b/tests/Makefile.

[PATCH 09/13] docs/system: Add U2F key to the USB devices examples

Signed-off-by: César Belley --- docs/system/usb.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/system/usb.rst b/docs/system/usb.rst index ddfa828d74..9a2f1927c4 100644 --- a/docs/system/usb.rst +++ b/docs/system/usb.rst @@ -81,6 +81,9 @@ option or the ``device_add`` monitor comma

[PATCH 11/13] scripts: Add u2f-setup-gen script

This patch adds the script used to generate setup directories, needed for the device u2f-emulated configuration in directory mode: python u2f-setup-gen.py $DIR qemu -usb -device u2f-emulated,dir=$DIR Signed-off-by: César Belley --- scripts/u2f-setup-gen.py | 170

[PATCH 12/13] hw/usb: Add U2F device check to passthru mode

This patchs adds a check to verify that the device passed through the hidraw property is a U2F device. The check is done by ensuring that the first values of the report descriptor (USAGE PAGE and USAGE) correspond to those of a U2F device. Signed-off-by: César Belley --- hw/usb/Makefile.objs |

Re: [PATCH 2/2] target/arm: Implement an IMPDEF pauth algorithm

Richard Henderson writes: > Without hardware acceleration, a cryptographically strong > algorithm is too expensive for pauth_computepac. > > Even with hardware accel, we are not currently expecting > to link the linux-user binaries to any crypto libraries, > and doing so would generally make th

Re: [PATCH 08/11] stubs/notify-event: Mark qemu_notify_event() stub as "weak"

On 04/08/20 20:20, Thomas Huth wrote: > On 04/08/2020 19.50, Richard Henderson wrote: >> On 8/4/20 10:00 AM, Thomas Huth wrote: >>> Otherwise there is a linker error with MinGW while compiling the tests: >>> >>> LINKtests/test-timed-average.exe >>> libqemuutil.a(main-loop.o): In function `qe

Re: [PATCH 2/2] migration: add vsock as data channel support

* Longpeng(Mike) (longpe...@huawei.com) wrote: > The vsock channel is more widely use in some new features, for example, > the Nitro/Enclave. It can also be used as the migration channel. > > Signed-off-by: Longpeng(Mike) OK; it might be worth adding some tests for this. Can I ask what your use

[Bug 1890545] Re: (ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and can't load HTML

Hi,Peter. I have added the ioctl() patch for Radeon driver in Qemu. However, there are many ioctls that only give cmd, I don't know where it comes from. 12161 poll(275275025312,1,4294967295,1,0,67108865) 12161 futex(0x0042f898,FUTEX_PRIVATE_FLAG|FUTEX_WAKE,1,NULL,NULL,0) = 0 12161 memfd_c

Re: [PATCH v2 4/5] hw/arm/virt: Move kvm pmu setup to virt_cpu_post_init

Hi Drew, On 8/5/20 11:16 AM, Andrew Jones wrote: > Move the KVM PMU setup part of fdt_add_pmu_nodes() to > virt_cpu_post_init(), which is a more appropriate location. Now > fdt_add_pmu_nodes() is also named more appropriately, because it > no longer does anything but fdt node creation. > > No func

Re: [PATCH v2 2/5] target/arm/kvm: Make uncalled stubs explicitly unreachable

Hi Drew, On 8/5/20 11:16 AM, Andrew Jones wrote: > When we compile without KVM support !defined(CONFIG_KVM) we generate > stubs for functions that the linker will still encounter. Sometimes > these stubs can be executed safely and are placed in paths where they > get executed with or without KVM.

Re: [PATCH v2 3/5] hw/arm/virt: Move post cpu realize check into its own function

Hi Drew, On 8/5/20 11:16 AM, Andrew Jones wrote: > We'll add more to this new function in coming patches so we also > state the gic must be created and call it below create_gic(). > > No functional change intended. > > Signed-off-by: Andrew Jones > Reviewed-by: Peter Maydell Reviewed-by: Eric

Re: [PATCH v2 1/6] migration: improve error reporting of block driver state name

* Daniel P. Berrangé (berra...@redhat.com) wrote: > With blockdev, a BlockDriverState may not have a device name, > so using a node name is required as an alternative. > > Signed-off-by: Daniel P. Berrangé Reviewed-by: Dr. David Alan Gilbert > --- > migration/savevm.c | 12 ++---

Re: [PATCH v2 3/6] migration: stop returning errno from load_snapshot()

* Daniel P. Berrangé (berra...@redhat.com) wrote: > None of the callers care about the errno value since there is a full > Error object populated. This gives consistency with save_snapshot() > which already just returns -1. > > Signed-off-by: Daniel P. Berrangé Reviewed-by: Dr. David Alan Gilb

Re: [PATCH v2 2/5] target/arm/kvm: Make uncalled stubs explicitly unreachable

On Wed, Aug 12, 2020 at 12:16:43PM +0200, Auger Eric wrote: > Hi Drew, > > On 8/5/20 11:16 AM, Andrew Jones wrote: > > When we compile without KVM support !defined(CONFIG_KVM) we generate > > stubs for functions that the linker will still encounter. Sometimes > > these stubs can be executed safely

Re: Assertion failure through virtio_blk_req_complete

On Mon, May 11, 2020 at 5:07 AM Alexander Bulekov wrote: > While fuzzing, I found an input that triggers an assertion through > virtio-blk.c: This reproducer does not work anymore in 5.1 but the underlying bug is still there so I am sending a patch series. Stefan

Re: [PATCH v7 02/13] hw/misc: Add NPCM7xx Clock Controller device model

On 8/11/20 2:45 AM, Havard Skinnemoen wrote: > Enough functionality to boot the Linux kernel has been implemented. This > includes: > > - Correct power-on reset values so the various clock rates can be > accurately calculated. > - Clock enables stick around when written. > > In addition,

Re: [PATCH v2 4/5] hw/arm/virt: Move kvm pmu setup to virt_cpu_post_init

On Wed, Aug 12, 2020 at 12:16:31PM +0200, Auger Eric wrote: > Hi Drew, > On 8/5/20 11:16 AM, Andrew Jones wrote: > > Move the KVM PMU setup part of fdt_add_pmu_nodes() to > > virt_cpu_post_init(), which is a more appropriate location. Now > > fdt_add_pmu_nodes() is also named more appropriately, be

[PATCH 0/3] virtio: restore elem->in/out_sg after iov_discard_front/back()

Both virtio-blk and virtio-crypto use destructive iov_discard_front/back() operations on elem->in/out_sg. virtqueue_push() calls dma_memory_unmap() on t= he modified iovec arrays. The memory addresses may not match those originally mapped with dma_memory_map(). This raises several issues: 1. Memor

[PATCH 2/3] virtio-blk: undo destructive iov_discard_*() operations

Fuzzing discovered that virtqueue_unmap_sg() is being called on modified req->in/out_sg iovecs. This means dma_memory_map() and dma_memory_unmap() calls do not have matching memory addresses. Fuzzing discovered that non-RAM addresses trigger a bug: void address_space_unmap(AddressSpace *as, voi

[PATCH 3/3] virtio-crypto: don't modify elem->in/out_sg

A number of iov_discard_front/back() operations are made by virtio-crypto. The elem->in/out_sg iovec arrays are modified by these operations, resulting virtqueue_unmap_sg() calls on different addresses than were originally mapped. This is problematic because dirty memory may not be logged correctl

[PATCH 1/3] util/iov: add iov_discard_undo()

The iov_discard_front/back() operations are useful for parsing iovecs but they modify the array elements. If the original array is needed after parsing finishes there is currently no way to restore it. Although g_memdup() can be used before performing destructive iov_discard_front/back() operation

Re: [PATCH 1/2] target/arm: Add cpu property to control pauth

On Tue, Aug 11, 2020 at 11:53:38PM -0700, Richard Henderson wrote: > The crypto overhead of emulating pauth can be significant for > some workloads. Add an enumeration property that allows the > feature to be turned off, on with the architected algorithm, > or on with an implementation defined alg

[PATCH] target/arm: Clarify HCR_EL2 ARMCPRegInfo type

In commit ce4afed839 ("target/arm: Implement AArch32 HCR and HCR2") the HCR_EL2 register has been changed from type NO_RAW (no underlying state and does not support raw access for state saving/loading) to type CONST (TCG can assume the value to be constant), removing the read/write accessors. We fo

[Bug 1890360] Re: Assertion failure in address_space_unmap through virtio-blk

** Changed in: qemu Status: New => In Progress -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1890360 Title: Assertion failure in address_space_unmap through virtio-blk Status in QEMU: In

[Bug 1886602] Re: Windows 10 very slow with OVMF

Inactive for more than a month, significant amount of info was not provided. Closing. ** Changed in: qemu Status: New => Incomplete -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1886602 Title

[Bug 1888971] Re: SMI trigger causes hang with multiple cores

Inactive for ~two weeks, closing. ** Changed in: qemu Status: New => Incomplete ** Changed in: qemu Status: Incomplete => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1888971

[Bug 1858814] Re: 'make -C roms efi' does not update edk2 submodules

Symptom persists as of v5.1.0, but I don't think it really matters. We should close the ticket as wontfix. ** Changed in: qemu Status: New => Confirmed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net

[Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install

Can we close this ticket now? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1847793 Title: qemu 4.1.0 - Corrupt guest filesystem after new vm install Status in QEMU: New Bug description: When

[Bug 1846427] Re: 4.1.0: qcow2 corruption on savevm/quit/loadvm cycle

Commit 5e9785505210 was released in v4.2.0; closing this ticket. ** Changed in: qemu Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1846427 Title: 4.1.0

[Bug 1717708] Re: QEMU aarch64 can't run Windows ARM64 iso's

No need to keep this open any longer (no activity for 19 months). Please follow the links captured above to the past discussions. There's nothing new to add wrt. the situation. ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qem

[Bug 1826200] Re: RFE: populate "OEM Strings" (type 11) SMBIOS table strings from regular files

We'll probably never have resources for this -- nice to have feature, but has not become critical in ~1.5 years. LP doesn't allow me to close the ticket as "Won't Fix", so I'll have to go with "Invalid". (The report is not invalid at all, but the ticket status should *somehow* reflect that we have

[Bug 1658634] Re: Can't get correct display with latest QEMU and OVMF BIOS

Fixed in commit 3ef0c573d37b ("console: fix console resize", 2017-01-31), released in v2.9.0. ** Changed in: qemu Status: Confirmed => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bu

Re: [PATCH for-5.1 v2] acceptance: use stable URLs for the Debian and Ubuntu installer

On 8/10/20 11:29 AM, Paolo Bonzini wrote: > The kernel and initrd hashes seem to have changed for the Bionic > aarch64 installer, causing BootLinuxConsole.test_aarch64_xlnx_versal_virt > to fail. Correct the paths to use the previous binaries instead of > the latest. Do the same for the Lenny alp

Re: [PATCH v2 0/2] acceptance: update asset urls for the Bionic aarch64 installer

On 8/10/20 11:30 AM, Philippe Mathieu-Daudé wrote: > v2 of Paolo's patch: > https://www.mail-archive.com/qemu-devel@nongnu.org/msg728610.html > > Do not update the binaries (and their hash), update the path to > the current tested binaries. > > Supersedes: <20200809223741.56570-1-pbonz...@redhat.

[PATCH] plugins: new syscalls plugin

This commit adds a new syscalls plugin that displays the syscalls as they are executed and returned. This plugin outputs the number of the syscall as well as the syscall return value. Works in *-user only. Essentially, this commit restores: https://lists.gnu.org/archive/html/qemu-devel/2018-06

Re: Acceptance Test BootLinuxAarch64.test_virt_tcg execution times

On 8/6/20 9:35 PM, Cleber Rosa wrote: > TL;DR: This is a followup from an IRC chat about the > tests/acceptance/boot_linux.py:BootLinuxAarch64.test_virt_tcg test > taking many orders of magnitute longer than other acceptance (and even > similar boot) tests. I could not find an easy way for this sp

[Bug 1858814] Re: 'make -C roms efi' does not update edk2 submodules

There might be a big buildsys change in QEMU if we switch to Meson, so I'm waiting for that to happen first and then update this ticket. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1858814 Title:

[Bug 1886602] Re: Windows 10 very slow with OVMF

** Changed in: qemu Status: Incomplete => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1886602 Title: Windows 10 very slow with OVMF Status in QEMU: Invalid Bug description: D

[PULL 3/7] 9pfs: split out fs driver core of v9fs_co_readdir()

The implementation of v9fs_co_readdir() has two parts: the outer part is executed by main I/O thread, whereas the inner part is executed by fs driver on a background I/O thread. Move the inner part to its own new, private function do_readdir(), so it can be shared by another upcoming new function.

[PULL 1/7] tests/virtio-9p: added split readdir tests

The previous, already existing 'basic' readdir test simply used a 'count' parameter big enough to retrieve all directory entries with a single Treaddir request. In the 3 new 'split' readdir tests added by this patch, directory entries are retrieved, split over several Treaddir requests by picking

[PULL 4/7] 9pfs: add new function v9fs_co_readdir_many()

The newly added function v9fs_co_readdir_many() retrieves multiple directory entries with a single fs driver request. It is intended to replace uses of v9fs_co_readdir(), the latter only retrieves a single directory entry per fs driver request instead. The reason for this planned replacement is th

[PULL 2/7] 9pfs: make v9fs_readdir_response_size() public

Rename function v9fs_readdir_data_size() -> v9fs_readdir_response_size() and make it callable from other units. So far this function is only used by 9p.c, however subsequent patches require the function to be callable from another 9pfs unit. And as we're at it; also make it clear for what this func

Re: [PATCH v2 5/5] hw/arm/virt: Implement kvm-steal-time

Drew, On 8/5/20 11:16 AM, Andrew Jones wrote: > We add the kvm-steal-time CPU property and implement it for machvirt. > A tiny bit of refactoring was also done to allow pmu and pvtime to > use the same vcpu device helper functions. > > Signed-off-by: Andrew Jones > --- > docs/system/arm/cpu-fea

[PULL 7/7] 9pfs: clarify latency of v9fs_co_run_in_worker()

As we just fixed a severe performance issue with Treaddir request handling, clarify this overall issue as a comment on v9fs_co_run_in_worker() with the intention to hopefully prevent such performance mistakes in future (and fixing other yet outstanding ones). Signed-off-by: Christian Schoenebeck

[PULL 0/7] 9p performance fix for 5.2 2020-08-12

The following changes since commit d0ed6a69d399ae193959225cdeaa9382746c91cc: Update version for v5.1.0 release (2020-08-11 17:07:03 +0100) are available in the Git repository at: https://github.com/cschoenebeck/qemu.git tags/pull-9p-20200812 for you to fetch changes up to

[Bug 893208] Re: qemu on ARM hosts can't boot i386 image

The qemu-linaro project seems to have been discontinued; the wiki and git repo links at don't work, and the latest release seems to be "qemu-linaro-1.7.0-2014.01.tar.gz". Marking this ticket as "invalid" for the qemu-linaro project. ** Changed in: qemu-linaro

[PULL 6/7] 9pfs: differentiate readdir lock between 9P2000.u vs. 9P2000.L

Previous patch suggests that it might make sense to use a different mutex type now while handling readdir requests, depending on the precise protocol variant, as v9fs_do_readdir_with_stat() (used by 9P2000.u) uses a CoMutex to avoid deadlocks that might happen with QemuMutex otherwise, whereas do_r

[PULL 5/7] 9pfs: T_readdir latency optimization

Make top half really top half and bottom half really bottom half: Each T_readdir request handling is hopping between threads (main I/O thread and background I/O driver threads) several times for every individual directory entry, which sums up to huge latencies for handling just a single T_readdir

[Bug 1529449] Re: serial is required for -device nvme

No new developments for 4+ years, closing as invalid (I'd prefer "wontfix due to lack of resources", but I'm unable to pick that resolution). ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to

[Bug 1217339] Re: SIGQUIT to send ACPI-shutdown to Guest

The discussion noted in comment#4 petered out in March 2017. Closing this ticket as "Invalid" (only because LP does not let me use the "Won't Fix" resolution -- the report / feature request may very well have had merit, but apparently a good enough design could not be found). ** Changed in: qemu

[Bug 1778350] Re: Android-x86 4.4-r5 won't boot on QEMU since v2.11.0-rc2

No feedback for almost two years, closing. ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1778350 Title: Android-x86 4.4-r5 won't boot on QEMU sinc

[Bug 1723927] Re: Linux or windows guest boot failed by uefi on CPU of Intel Xeon X5675

Closing due to almost 3 years of inactivity. ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1723927 Title: Linux or windows guest boot failed by ue

[Bug 1813165] Re: KVM internal error. Suberror: 1 emulation failure

According to comment #12, the bug underlying this LP ticket was fixed in Linux kernel commit ad7dc69aeb23 ("x86/kvm/mmu: fix switch between root and guest MMUs", 2019-02-22), released in v5.0. ** Project changed: qemu => linux ** Changed in: linux Status: New => Fix Released -- You recei

Re: [PATCH 007/147] tests/vm: do not pollute configure with --efi-aarch64

Reviewed-by: Robert Foley On Mon, 10 Aug 2020 at 13:12, Paolo Bonzini wrote: > > Just make EFI_AARCH64 a variable in the makefile that defaults to the efi > firmware included with QEMU. It can be redefined on the "make" command > line. > > Signed-off-by: Paolo Bonzini > --- > configure

[PULL 0/2] Acceptance testing patches for 2020-08-12

The following changes since commit d0ed6a69d399ae193959225cdeaa9382746c91cc: Update version for v5.1.0 release (2020-08-11 17:07:03 +0100) are available in the Git repository at: https://gitlab.com/philmd/qemu.git tags/acceptance-testing-20200812 for you to fetch changes up to

[PULL 1/2] tests/acceptance/boot_linux: Extract common URL from xlnx-versal test

Both files refer to the same directory. Store the common part in a new variable. Signed-off-by: Philippe Mathieu-Daudé Message-Id: <20200810093050.28744-2-phi...@redhat.com> --- tests/acceptance/boot_linux_console.py | 11 +-- 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a

[PULL 2/2] acceptance: use stable URLs for the Debian and Ubuntu installer

From: Paolo Bonzini The kernel and initrd hashes seem to have changed for the Bionic aarch64 installer, causing BootLinuxConsole.test_aarch64_xlnx_versal_virt to fail. Correct the paths to use the previous binaries instead of the latest. Do the same for the Lenny alpha installer for consistency

Re: [PATCH 000/147] Meson integration for 5.2

Hi Howard, On 8/12/20 8:32 AM, Howard Spoelstra wrote: > Hi, > > I just compiled qemu-system-ppc using the the meson-poc-next branch with: > git clone -b meson-poc-next http://www.github.com/bonzini/qemu > qemu-mesonbuild-next I notice you refer to github while Paolo mentioned gitlab in the cove

[PATCH RFC 00/10] fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors, this series fixed this spelling errors. zhaolichang (10): qemu/: fix some comment spelling errors migration/: fix some comment spelling errors docs/: fix some com

[PATCH RFC 07/10] block/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the block folder. Signed-off-by: zhaolichang --- block/block-copy.c | 2 +- block/linux-aio.c | 2 +- block/mirror.c | 2

[PATCH RFC 06/10] linux-user/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the linux-user folder. Signed-off-by: zhaolichang --- linux-user/aarch64/signal.c | 2 +- linux-user/cris/target_

[PATCH RFC 08/10] disas/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the disas folder. Signed-off-by: zhaolichang --- disas/hppa.c | 2 +- disas/libvixl/vixl/a64/cons

[PATCH RFC 03/10] docs/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the docs folder. Signed-off-by: zhaolichang --- docs/COLO-FT.txt | 6 +++--- docs/devel/blkdebug.txt

[PATCH RFC 04/10] scripts/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the scripts folder. Signed-off-by: zhaolichang --- scripts/checkpatch.pl | 2 +- scripts/clean-header-guards.pl | 2 +

[PATCH RFC 05/10] util/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the util folder. Signed-off-by: zhaolichang --- util/osdep.c | 2 +- util/qemu-progress.c | 2 +- util/qemu-so

[PATCH RFC 01/10] qemu/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the folder. Signed-off-by: zhaolichang --- Changelog | 2 +- accel/tcg/user-exec.c | 2 +- audio/audio

[PATCH RFC 02/10] migration/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the migration folder. Signed-off-by: zhaolichang --- migration/colo-failover.c | 2 +- migration/colo.c | 2 +- mig

[PATCH RFC 09/10] qapi/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the qapi folder. Signed-off-by: zhaolichang --- qapi/block-core.json | 4 ++-- qapi/crypto.json | 4 ++-- 2 files changed,

[PATCH RFC 10/10] contrib/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the contrib folder. Signed-off-by: zhaolichang --- contrib/gitdm/filetypes.txt | 6 +++--- contrib/ivshmem-client/

Re: [PATCH v1 0/2] Add timeout mechanism to qmp actions

On Mon, Aug 10, 2020 at 10:52:44PM +0800, Zhenyu Ye wrote: > Before doing qmp actions, we need to lock the qemu_global_mutex, > so the qmp actions should not take too long time. > > Unfortunately, some qmp actions need to acquire aio context and > this may take a long time. The vm will soft locku

[PATCH 2/2] linux-user: Add support for 'utimensat_time64()' and 'semtimedop_time64()'

This patch introduces functionality for following time64 syscalls: *utimensat_time64() int utimensat(int dirfd, const char *pathname, const struct timespec times[2], int flags); -- change file timestamps with nanosecond precision -- man page: https://man7.org/linux/m

[PATCH 1/2] linux-user: Add support for 'ppoll_time64()' and 'pselect6_time64()'

This patch introduces functionality for following time64 syscalls: *ppoll_time64 This is a year 2038 safe variant of: int poll(struct pollfd *fds, nfds_t nfds, int timeout) -- wait for some event on a file descriptor -- man page: https://man7.org/linux/man-pages/man2/ppoll.2.html

Re: [PATCH v2 for 5.2 0/3] block: add logging facility for long standing IO requests

On Mon, Aug 10, 2020 at 01:14:44PM +0300, Denis V. Lunev wrote: > There are severe delays with IO requests processing if QEMU is running in > virtual machine or over software defined storage. Such delays potentially > results in unpredictable guest behavior. For example, guests over IDE or > SATA d

[PATCH] linux-user: Fix 'semop()' and 'semtimedop()' implementation

The implementations of syscalls 'semop()' and 'semtimedop()' in file 'syscall.c' use function 'target_to_host_sembuf()' to convert values of 'struct sembuf' from host to target. However, before this conversion it should be check whether the number of semaphore operations 'nsops' is not bigger than

[PATCH 0/2] linux-user: Adding support for a group of 4 time64 syscalls

This two patch series introduces functionality for following Year 2038 safe syscalls: --Introduced in first patch-- *ppoll_time64() *pselect6_time64() --Introduced in second patch-- *utimensat_time64() *semtimedop_time64() Testing notes: The implementations of these time64 syscalls was teste

Re: [PATCH RFC 01/10] qemu/: fix some comment spelling errors

zhaolichang writes: > I found that there are many spelling errors in the comments of qemu, > so I used the spellcheck tool to check the spelling errors > and finally found some spelling errors in the folder. > > Signed-off-by: zhaolichang > --- > diff --git a/gdbstub.c b/gdbstub.c > index f3

KVM call for agenda for 2020-08-25

Hi Please, send any topic that you are interested in covering. At the end of Monday I will send an email with the agenda or the cancellation of the call, so hurry up. After discussions on the QEMU Summit, we are going to have always open a KVM call where you can add topics. Call details: B

Re: [PATCH RFC 05/10] util/: fix some comment spelling errors

zhaolichang writes: > I found that there are many spelling errors in the comments of qemu, > so I used the spellcheck tool to check the spelling errors > and finally found some spelling errors in the util folder. > > Signed-off-by: zhaolichang Reviewed-by: Alex Bennée -- Alex Bennée

Re: [PATCH RFC 03/10] docs/: fix some comment spelling errors

zhaolichang writes: > I found that there are many spelling errors in the comments of qemu, > so I used the spellcheck tool to check the spelling errors > and finally found some spelling errors in the docs folder. > > Signed-off-by: zhaolichang Reviewed-by: Alex Bennée -- Alex Bennée

Re: [PATCH RFC 06/10] linux-user/: fix some comment spelling errors

zhaolichang writes: > I found that there are many spelling errors in the comments of qemu, > so I used the spellcheck tool to check the spelling errors > and finally found some spelling errors in the linux-user folder. > > Signed-off-by: zhaolichang Reviewed-by: Alex Bennée -- Alex Bennée

Re: [PATCH for-5.2 v3 0/3] migration: Add block-bitmap-mapping parameter

Ping – seems like everyone found v2 more or less acceptable bar the failing assertion in patch 1, and some aspects of the test. How about v3, are there any objections? On 22.07.20 10:05, Max Reitz wrote: > RFC v1: https://lists.nongnu.org/archive/html/qemu-block/2020-05/msg00912.html > RFC v2: ht

Re: [PATCH RFC 10/10] contrib/: fix some comment spelling errors

zhaolichang writes: > I found that there are many spelling errors in the comments of qemu, > so I used the spellcheck tool to check the spelling errors > and finally found some spelling errors in the contrib folder. > > Signed-off-by: zhaolichang Reviewed-by: Alex Bennée -- Alex Bennée

Re: [PATCH for-5.2 v3 1/3] migration: Add block-bitmap-mapping parameter

On 7/22/20 3:05 AM, Max Reitz wrote: This migration parameter allows mapping block node names and bitmap names to aliases for the purpose of block dirty bitmap migration. This way, management tools can use different node and bitmap names on the source and destination and pass the mapping of how

Re: [RFC v3 0/1] memory: Delete assertion in memory_region_unregister_iommu_notifier

On Tue, Aug 11, 2020 at 9:28 PM Peter Xu wrote: > > Hi, Eugenio, > > On Tue, Aug 11, 2020 at 08:10:44PM +0200, Eugenio Perez Martin wrote: > > Using this patch as a reference, I'm having problems to understand: > > > > - I'm not sure that the flag name expresses clearly the notifier capability. >

Re: [PATCH for-5.2 v3 0/3] migration: Add block-bitmap-mapping parameter

Now this doesn't apply, as code changed a lot after my series "[PATCH v4 for-5.1 00/21] Fix error handling during bitmap postcopy" merged first. I feel my responsibility for the mess with these series, so if you want I can try to rebase and post v4 of this one myself :) 12.08.2020 17:15, Max R

  1   2   3   >