RE: [RFC v2 00/22] intel_iommu: expose Shared Virtual Addressing to VM

> From: Jason Wang [mailto:jasow...@redhat.com] > Sent: Thursday, October 31, 2019 12:33 PM > > > On 2019/10/25 下午6:12, Tian, Kevin wrote: > >> From: Jason Wang [mailto:jasow...@redhat.com] > >> Sent: Friday, October 25, 2019 5:49 PM > >> > >> > >> On 2019/10/24 下午8:34, Liu Yi L wrote: > >>>

Re: [RFC v2 00/22] intel_iommu: expose Shared Virtual Addressing to VM

On 2019/10/25 下午6:12, Tian, Kevin wrote: From: Jason Wang [mailto:jasow...@redhat.com] Sent: Friday, October 25, 2019 5:49 PM On 2019/10/24 下午8:34, Liu Yi L wrote: Shared virtual address (SVA), a.k.a, Shared virtual memory (SVM) on Intel platforms allow address space sharing between device

[PATCH v1 1/1] hw/arm/boot: Rebuild hflags when modifying CPUState at boot

Rebuild hflags when modifying CPUState at boot. Fixes: e979972a6a Signed-off-by: Edgar E. Iglesias --- hw/arm/boot.c | 1 + 1 file changed, 1 insertion(+) diff --git a/hw/arm/boot.c b/hw/arm/boot.c index c264864c11..ef6724960c 100644 --- a/hw/arm/boot.c +++ b/hw/arm/boot.c @@ -786,6 +786,7 @@

[PATCH v1 0/1] hw/arm/boot: Rebuild hflags when modifying CPUState at boot

I'm seeing asserts with missmatching hflags when doing direct boots on versal. This patch fixes the problem for me, rebuilding hflags after boot code modifes the state. Cheers, Edgar Edgar E. Iglesias (1): hw/arm/boot: Rebuild hflags when modifying CPUState at boot hw/arm/boot.c | 1 + 1

Re: RFC: New device for zero-copy VM memory access

Hi Dave, On 2019-10-31 05:52, Dr. David Alan Gilbert wrote: * ge...@hostfission.com (ge...@hostfission.com) wrote: Hi All, Over the past week, I have been working to come up with a solution to the memory transfer performance issues that hinder the Looking Glass Project. Currently Looking

Re: [PATCH 00/30] virtiofs daemon (base)

On Wed, Oct 30, 2019 at 10:47:00AM +, Dr. David Alan Gilbert wrote: > * Michael S. Tsirkin (m...@redhat.com) wrote: > > On Mon, Oct 21, 2019 at 11:58:02AM +0100, Dr. David Alan Gilbert (git) > > wrote: > > > From: "Dr. David Alan Gilbert" > > > > > > Hi, > > > This is the 1st set for the

[Bug 1850000] Re: 4.1.0 bogus QCOW2 corruption reported after compress

Thank you Max. Can confirm your patch fixes my issue (qemu-img check ...) Not sure about those other code paths. I don't use internal snapshots and I'm not sure under which circumstances qcow2_free_any_clusters() gets exercised. Just for good measure, with patch applied I created another >4GB

Re: [RFC PATCH v2 05/26] qcow2: Document the Extended L2 Entries feature

On Wed 30 Oct 2019 05:23:30 PM CET, Max Reitz wrote: >> +Subcluster Allocation Bitmap (for standard clusters): >> + >> +Bit 0 - 31: Allocation status (one bit per subcluster) >> + >> +1: the subcluster is allocated. In this case the >> + host

Re: [PATCH] fw_cfg: Allow reboot-timeout=-1 again

However, another important question is: how can we avoid such undocumented incompatibility appears again? I can show another case caused by such incompatibile change: https://bugzilla.redhat.com/show_bug.cgi?id=1745868#c0 For the qemu devices, attributes, values, qmp cmds, qmp cmds arguments used

Re: [PULL for-4.2 0/1] softfp patch queue

Patchew URL: https://patchew.org/QEMU/20191030180953.24180-1-richard.hender...@linaro.org/ Hi, This series seems to have some coding style problems. See output below for more information: Subject: [PULL for-4.2 0/1] softfp patch queue Type: series Message-id:

Re: [PATCH] spapr/kvm: Set default cpu model for all machine classes

Patchew URL: https://patchew.org/QEMU/20191030163243.10644-1-da...@gibson.dropbear.id.au/ Hi, This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT

[PULL for-4.2 0/1] softfp patch queue

://github.com/rth7680/qemu.git tags/pull-sfp-20191030 for you to fetch changes up to 21381dcf0ca8fc822328e30570c8465ec4e52be9: softfp: Added hardfloat conversion from float32 to float64 (2019-10-30 19:03:37 +0100) Use hardfloat

[PULL for-4.2 1/1] softfp: Added hardfloat conversion from float32 to float64

From: Matus Kysel Reintroduce float32_to_float64 that was removed here: https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg00455.html - nbench test it not actually calling this function at all - SPECS 2006 significat number of tests impoved their runtime, just few of them showed

Re: [PATCH] spapr/kvm: Set default cpu model for all machine classes

Patchew URL: https://patchew.org/QEMU/20191030163243.10644-1-da...@gibson.dropbear.id.au/ Hi, This series seems to have some coding style problems. See output below for more information: Subject: [PATCH] spapr/kvm: Set default cpu model for all machine classes Type: series Message-id:

Re: [PATCH] spapr/kvm: Set default cpu model for all machine classes

On 30.10.19 17:32, David Gibson wrote: We have to set the default model of all machine classes, not just for the active one. Otherwise, "query-machines" will indicate the wrong CPU model ("qemu-s390x-cpu" instead of "host-s390x-cpu") as "default-cpu-type". Maybe use ppc CPU models here instead

Re: RFC: New device for zero-copy VM memory access

* ge...@hostfission.com (ge...@hostfission.com) wrote: > Hi All, > > Over the past week, I have been working to come up with a solution to the > memory transfer performance issues that hinder the Looking Glass Project. > > Currently Looking Glass works by using the IVSHMEM shared memory device >

Re: [PATCH 2/2] tests/fw_cfg: Test 'reboot-timeout=-1' special value

* Philippe Mathieu-Daudé (phi...@redhat.com) wrote: > The special value -1 means "don't reboot" for QEMU/libvirt. > Add a trivial test. > > Signed-off-by: Philippe Mathieu-Daudé Reviewed-by: Dr. David Alan Gilbert > --- > tests/fw_cfg-test.c | 21 + > 1 file changed, 21

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

There is a patch for the XFS kernel driver to fix the bug: https://www.spinics.net/lists/linux-xfs/msg33429.html On the qemu side, we’re still discussing on how to work around the bug in the 4.2 release. Max -- You received this bug notification because you are a member of qemu- devel-ml,

Re: [RFC PATCH v2 10/26] qcow2: Update get/set_l2_entry() and add get/set_l2_bitmap()

On 26.10.19 23:25, Alberto Garcia wrote: > Extended L2 entries are 128-bit wide: 64 bits for the entry itself and > 64 bits for the subcluster allocation bitmap. > > In order to support them correctly get/set_l2_entry() need to be > updated so they take the entry width into account in order to >

Re: [RFC PATCH v2 09/26] qcow2: Add l2_entry_size()

On 26.10.19 23:25, Alberto Garcia wrote: > qcow2 images with subclusters have 128-bit L2 entries. The first 64 > bits contain the same information as traditional images and the last > 64 bits form a bitmap with the status of each individual subcluster. > > Because of that we cannot assume that L2

[PATCH] spapr/kvm: Set default cpu model for all machine classes

We have to set the default model of all machine classes, not just for the active one. Otherwise, "query-machines" will indicate the wrong CPU model ("qemu-s390x-cpu" instead of "host-s390x-cpu") as "default-cpu-type". s390x already fixed this in de60a92e "s390x/kvm: Set default cpu model for all

Re: [PULL v4 for 4.2 00/57] TCG plugins

On Mon, 28 Oct 2019 at 15:15, Alex Bennée wrote: > > The following changes since commit 9bb73502321d46f4d320fa17aa38201445783fc4: > > Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging > (2019-10-28 13:32:40 +) > > are available in the Git repository at: > >

Re: [RFC PATCH v2 05/26] qcow2: Document the Extended L2 Entries feature

On 26.10.19 23:25, Alberto Garcia wrote: > Subcluster allocation in qcow2 is implemented by extending the > existing L2 table entries and adding additional information to > indicate the allocation status of each subcluster. > > This patch documents the changes to the qcow2 format and how they >

Re: [PATCH] tests: fix conditional for disabling XTS test

Patchew URL: https://patchew.org/QEMU/20191030151740.14326-1-berra...@redhat.com/ Hi, This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT BEGIN

Re: [RFC PATCH v2 01/26] qcow2: Add calculate_l2_meta()

On Wed 30 Oct 2019 01:04:02 PM CET, Max Reitz wrote: > (I intended not to comment on such things on an RFC, but here I am...) No problem with that :-) > I’d call it host_cluster_offset to make clear that it points to a > cluster and isn’t the host offset for @guest_offset. Sure, why not. We can

Re: [RFC PATCH v2 01/26] qcow2: Add calculate_l2_meta()

On Mon 28 Oct 2019 01:50:54 PM CET, Vladimir Sementsov-Ogievskiy wrote: >> -.cow_end = { >> -.offset = nb_bytes, > > hmm this logic is changed.. after the patch, it would be not nb_bytes, but > > offset_into_cluster(s, guest_offset) + MIN(*bytes, nb_bytes - >

Re: [PATCH v4 00/20] Add virtual device fuzzing support

Patchew URL: https://patchew.org/QEMU/20191030144926.11873-1-alx...@bu.edu/ Hi, This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT BEGIN ===

[PATCH] tests: fix conditional for disabling XTS test

The intent is to only enable the XTS test if both CONFIG_BLOCK and CONFIG_QEMU_PRIVATE_XTS are set to 'y'. Signed-off-by: Daniel P. Berrangé --- tests/Makefile.include | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/Makefile.include b/tests/Makefile.include index

[PATCH v4 19/20] fuzz: add virtio-net fuzz target

From: Alexander Oleinik The virtio-net fuzz target feeds inputs to all three virtio-net virtqueues, and uses forking to avoid leaking state between fuzz runs. Signed-off-by: Alexander Oleinik --- tests/fuzz/Makefile.include | 1 + tests/fuzz/virtio_net_fuzz.c | 123

[PATCH v4 17/20] fuzz: add support for qos-assisted fuzz targets

From: Alexander Oleinik Signed-off-by: Alexander Oleinik --- tests/fuzz/qos_fuzz.c | 232 ++ tests/fuzz/qos_fuzz.h | 33 ++ 2 files changed, 265 insertions(+) create mode 100644 tests/fuzz/qos_fuzz.c create mode 100644 tests/fuzz/qos_fuzz.h diff

[PATCH v4 16/20] fuzz: add support for fork-based fuzzing.

From: Alexander Oleinik fork() is a simple way to ensure that state does not leak in between fuzzing runs. Unfortunately, the fuzzer mutation engine relies on bitmaps which contain coverage information for each fuzzing run, and these bitmaps should be copied from the child to the parent(where

[PATCH v4 10/20] libqos: move useful qos-test funcs to qos_external

From: Alexander Oleinik The moved functions are not specific to qos-test and might be useful elsewhere. For example the virtual-device fuzzer makes use of them for qos-assisted fuzz-targets. Signed-off-by: Alexander Oleinik --- tests/Makefile.include | 1 + tests/libqos/qos_external.c

[PATCH v4 13/20] fuzz: add configure flag --enable-fuzzing

From: Alexander Oleinik Signed-off-by: Alexander Oleinik --- configure | 39 +++ 1 file changed, 39 insertions(+) diff --git a/configure b/configure index 3be9e92a24..aeca632dd9 100755 --- a/configure +++ b/configure @@ -501,6 +501,7 @@ libxml2=""

[PATCH v4 05/20] libqtest: Add a layer of abstraciton to send/recv

From: Alexander Oleinik This makes it simple to swap the transport functions for qtest commands to and from the qtest client. For example, now it is possible to directly pass qtest commands to a server handler that exists within the same process, without the standard way of writing to a file

[PATCH v4 11/20] libqtest: make qtest_bufwrite send "atomic"

From: Alexander Oleinik When using qtest "in-process" communication, qtest_sendf directly calls a function in the server (qtest.c). Combining the contents of the subsequent socket_sends into the qtest_sendf, makes it so the server can immediately handle the command, without building a local

[PATCH v4 08/20] tests: provide test variables to other targets

From: Alexander Oleinik Before, when tests/Makefile.include was included, the contents would be ignored if config-host.mak was defined. Moving the ifneq responsible for this allows a target to depend on both testing-related and host-related objects. For example the virtual-device fuzzer relies

[PATCH v4 20/20] fuzz: add documentation to docs/devel/

From: Alexander Oleinik Signed-off-by: Alexander Oleinik --- docs/devel/fuzzing.txt | 119 + 1 file changed, 119 insertions(+) create mode 100644 docs/devel/fuzzing.txt diff --git a/docs/devel/fuzzing.txt b/docs/devel/fuzzing.txt new file mode 100644

[PATCH v4 02/20] libqos: Rename i2c_send and i2c_recv

From: Alexander Oleinik The names i2c_send and i2c_recv collide with functions defined in hw/i2c/core.c. This causes an error when linking against libqos and softmmu simultaneously (for example when using qtest inproc). Rename the libqos functions to avoid this. Signed-off-by: Alexander Oleinik

[PATCH v4 14/20] fuzz: Add target/fuzz makefile rules

From: Alexander Oleinik Signed-off-by: Alexander Oleinik --- Makefile| 15 ++- Makefile.objs | 4 +++- Makefile.target | 18 +- tests/fuzz/Makefile.include | 4 4 files changed, 38 insertions(+), 3 deletions(-)

[PATCH v4 15/20] fuzz: add fuzzer skeleton

From: Alexander Oleinik tests/fuzz/fuzz.c serves as the entry point for the virtual-device fuzzer. Namely, libfuzzer invokes the LLVMFuzzerInitialize and LLVMFuzzerTestOneInput functions, both of which are defined in this file. This change adds a "FuzzTarget" struct, along with the

[PATCH v4 04/20] qtest: add qtest_server_send abstraction

From: Alexander Oleinik qtest_server_send is a function pointer specifying the handler used to transmit data to the qtest client. In the standard configuration, this calls the CharBackend handler, but now it is possible for other types of handlers, e.g direct-function calls if the qtest client

[PATCH v4 18/20] fuzz: add i440fx fuzz targets

From: Alexander Oleinik These three targets should simply fuzz reads/writes to a couple ioports, but they mostly serve as examples of different ways to write targets. They demonstrate using qtest and qos for fuzzing, as well as using rebooting and forking to reset state, or not resetting it at

[PATCH v4 06/20] module: check module wasn't already initialized

From: Alexander Oleinik The virtual-device fuzzer must initialize QOM, prior to running vl:qemu_init, so that it can use the qos_graph to identify the arguments required to initialize a guest for libqos-assisted fuzzing. This change prevents errors when vl:qemu_init tries to (re)initialize the

[PATCH v4 09/20] libqos: split qos-test and libqos makefile vars

From: Alexander Oleinik Most qos-related objects were specified in the qos-test-obj-y variable. qos-test-obj-y also included qos-test.o which defines a main(). This made it difficult to repurpose qos-test-obj-y to link anything beside tests/qos-test against libqos. This change separates objects

[PATCH v4 03/20] fuzz: Add FUZZ_TARGET module type

From: Alexander Oleinik Signed-off-by: Alexander Oleinik --- include/qemu/module.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/include/qemu/module.h b/include/qemu/module.h index 65ba596e46..684753d808 100644 --- a/include/qemu/module.h +++ b/include/qemu/module.h @@

[PATCH v4 12/20] libqtest: add in-process qtest.c tx/rx handlers

From: Alexander Oleinik Signed-off-by: Alexander Oleinik --- There's a particularily ugly line here: qtest_client_set_tx_handler(qts, (void (*)(QTestState *s, const char*, size_t)) send); Since qtest.c has no knowledge of the QTestState, I'm not sure how to avoid doing this, without

[PATCH v4 01/20] softmmu: split off vl.c:main() into main.c

From: Alexander Oleinik A program might rely on functions implemented in vl.c, but implement its own main(). By placing main into a separate source file, there are no complaints about duplicate main()s when linking against vl.o. For example, the virtual-device fuzzer uses a main() provided by

[PATCH v4 07/20] qtest: add in-process incoming command handler

From: Alexander Oleinik The handler allows a qtest client to send commands to the server by directly calling a function, rather than using a file/CharBackend Signed-off-by: Alexander Oleinik --- include/sysemu/qtest.h | 1 + qtest.c| 13 + 2 files changed, 14

[PATCH v4 00/20] Add virtual device fuzzing support

This series adds a framework for coverage-guided fuzzing of virtual-devices. Fuzzing targets are based on qtest and can make use of the libqos abstractions. V4: * add/transfer license headers to new files * restructure the added QTestClientTransportOps struct * restructure the FuzzTarget

Re: [RFC PATCH v2 03/26] qcow2: Process QCOW2_CLUSTER_ZERO_ALLOC clusters in handle_copied()

On 26.10.19 23:25, Alberto Garcia wrote: > When writing to a qcow2 file there are two functions that take a > virtual offset and return a host offset, possibly allocating new > clusters if necessary: > >- handle_copied() looks for normal data clusters that are already > allocated and

Re: [PULL 4/4] crypto: add support for nettle's native XTS impl

Daniel P. Berrangé writes: > Nettle 3.5.0 will add support for the XTS mode. Use this because long > term we wish to delete QEMU's XTS impl to avoid carrying private crypto > algorithm impls. > > Unfortunately this degrades nettle performance from 612 MB/s to 568 MB/s > as nettle's XTS impl

Re: [PATCH v11 14/15] hw/i386: Introduce the microvm machine type

On 30/10/19 10:25, Philippe Mathieu-Daudé wrote: >> diff --git a/default-configs/i386-softmmu.mak >> b/default-configs/i386-softmmu.mak >> index 4229900f57..4cc64dafa2 100644 >> --- a/default-configs/i386-softmmu.mak >> +++ b/default-configs/i386-softmmu.mak >> @@ -28,3 +28,4 @@ >>  

Re: [PULL 0/16] Python (acceptance tests) queue, 2019-10-28

On Tue, 29 Oct 2019 at 23:40, Cleber Rosa wrote: > > I'm now getting the updated key on every single server I've tried. > > Any further feedback/request is highly appreciated. Yep, I was able to pull the updated key. Applied, thanks. Please update the changelog at

Re: [PATCH v3 00/20] hw/i386/pc: Split PIIX3 southbridge from i440FX northbridge

> > In case you, for any reason, can't complete this by softfreeze, I advice >> you not to rush, and postpone the integration to 5.0. >> > > This series doesn't provide any useful feature, it is a simple cleanup, > posted and reviewed before soft freeze, so we still have 1 week (until > hard

Re: [Xen-devel] [PATCH v3 00/20] hw/i386/pc: Split PIIX3 southbridge from i440FX northbridge

Patchew URL: https://patchew.org/QEMU/20191026180143.7369-1-phi...@redhat.com/ Hi, This series seems to have some coding style problems. See output below for more information: Subject: [Xen-devel] [PATCH v3 00/20] hw/i386/pc: Split PIIX3 southbridge from i440FX northbridge Type: series

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

I have the same (related?) issue and wanted to add my experience with it. I had 3 qemu qcow2 VM running on ArchLinux. I never used snapshots or something like it. Just normal start 2 of these VMs were also ArchLinux running on ext4. Both of these VMs had a data corruption inside the quest. The

Re: [RFC PATCH v2 01/26] qcow2: Add calculate_l2_meta()

On 26.10.19 23:25, Alberto Garcia wrote: > handle_alloc() creates a QCowL2Meta structure in order to update the > image metadata and perform the necessary copy-on-write operations. > > This patch moves that code to a separate function so it can be used > from other places. > > Signed-off-by:

[PATCH v3] qcow2-bitmap: Fix uint64_t left-shift overflow

There are two issues in In check_constraints_on_bitmap(), 1) The sanity check on the granularity will cause uint64_t integer left-shift overflow when cluster_size is 2M and the granularity is BIGGER than 32K. 2) The way to calculate image size that the maximum bitmap supported can map to is a bit

[Bug 1850000] Re: 4.1.0 bogus QCOW2 corruption reported after compress

Forgot to say that I sent a patch: https://lists.nongnu.org/archive/html/qemu-block/2019-10/msg01764.html Thanks for reporting! Max -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/185 Title:

Re: [PATCH v3 4/6] iotests: Skip "make check-block" if QEMU does not support virtio-blk

On 22.10.19 09:21, Thomas Huth wrote: > The next patch is going to add some python-based tests to the "auto" > group, and these tests require virtio-blk to work properly. Running > iotests without virtio-blk likely does not make too much sense anyway, > so instead of adding a check for the

Re: [PULL 0/3] a few gitdm updates

On Sun, 27 Oct 2019 at 19:22, Alex Bennée wrote: > > The following changes since commit 856bd2c28e108ad0eb909bbbf3774f6f8bd7c2d4: > > Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' > into staging (2019-10-25 21:57:41 +0100) > > are available in the Git repository at: >

Re: [PULL 00/14] virtio: features, cleanups

On Tue, 29 Oct 2019 at 23:00, Michael S. Tsirkin wrote: > > The following changes since commit 16884391c750d0c5e863f55ad7146fc5181e: > > Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2019-10-29' > into staging (2019-10-29 20:06:08 +) > > are available in the Git

Re: [PATCH 00/30] virtiofs daemon (base)

* Michael S. Tsirkin (m...@redhat.com) wrote: > On Mon, Oct 21, 2019 at 11:58:02AM +0100, Dr. David Alan Gilbert (git) wrote: > > From: "Dr. David Alan Gilbert" > > > > Hi, > > This is the 1st set for the virtiofsd - a daemon > > that implements the user space side of virtiofs. > > > > The

Re: [PATCH v6 06/11] qapi: add failover negotiated event

On Tue, Oct 29, 2019 at 06:41:58PM -0400, Michael S. Tsirkin wrote: On Fri, Oct 25, 2019 at 07:39:21PM +0200, Jens Freimann wrote: On Fri, Oct 25, 2019 at 04:03:54PM +0200, Markus Armbruster wrote: > Bear with me, I know next to nothing about failover. > > Jens Freimann writes: > > > This

Re: [PATCH v3 00/20] hw/i386/pc: Split PIIX3 southbridge from i440FX northbridge

Hi Aleksandar, On 10/27/19 8:44 AM, Aleksandar Markovic wrote: On Saturday, October 26, 2019, Philippe Mathieu-Daudé > wrote: Changes since v2 [0]: - Use a #define - Reword one description - Added review tags (thanks all for reviewing!) Changes

[Bug 1850378] Re: RISC-V unreliable IPIs

** Description changed: I am working on a project with custom inter processor interrupts (IPIs) on the RISC-V virt machine. After upgrading from version 3.1.0 to 4.1.0 which fixes a related issue (https://github.com/riscv/riscv-qemu/issues/132) I am able to use the CPU hotplug feature.

Re: [PULL 00/20] hw/i386/pc: Split PIIX3 southbridge from i440FX northbridge

Hi Peter, Paolo, On 10/30/19 7:15 AM, Peter Maydell wrote: On Mon, 28 Oct 2019 at 17:48, Philippe Mathieu-Daudé wrote: The i440FX northbridge is only used by the PC machine, while the PIIX southbridge is also used by the Malta

Re: [PATCH v11 14/15] hw/i386: Introduce the microvm machine type

Hi Sergio, Paolo, On 10/18/19 12:53 PM, Sergio Lopez wrote: microvm is a machine type inspired by Firecracker and constructed after its machine model. It's a minimalist machine type without PCI nor ACPI support, designed for short-lived guests. microvm also establishes a baseline for

Re: [PATCH] block/block-copy: fix s->copy_size for compressed cluster

On 29.10.19 16:09, Vladimir Sementsov-Ogievskiy wrote: > 0e2402452f1f20429 allowed writes larger than cluster, but that's > unsupported for compressed write. Fix it. > > Fixes: 0e2402452f1f20429 > Signed-off-by: Vladimir Sementsov-Ogievskiy > --- > block/block-copy.c | 4 ++-- > 1 file changed,

Re: [PATCH v2] Added hardfloat conversion from float32 to float64

On 10/17/19 4:21 PM, Matus Kysel wrote: > Reintroduce float32_to_float64 that was removed here: > https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg00455.html > > - nbench test it not actually calling this function at all > - SPECS 2006 significat number of tests impoved their runtime,

RE: [PATCH v7 4/4] colo: Update Documentation for continuous replication

> -Original Message- > From: Lukas Straub > Sent: Thursday, October 24, 2019 10:26 PM > To: qemu-devel > Cc: Zhang, Chen ; Jason Wang > ; Wen Congyang ; > Wen Congyang ; Xie Changlong > ; Kevin Wolf ; Max Reitz > ; qemu-block > Subject: [PATCH v7 4/4] colo: Update Documentation for

Re: [PATCH v20 3/5] ACPI: Add APEI GHES table generation support

On 2019/10/27 18:14, Michael S. Tsirkin wrote: > On Sat, Oct 26, 2019 at 11:24:45AM +0800, Xiang Zheng wrote: >> From: Dongjiu Geng >> >> This patch implements APEI GHES Table generation via fw_cfg blobs. Now >> it only supports ARMv8 SEA, a type of GHESv2 error source. Afterwards, >> we can

RE: [PATCH] Added hardfloat conversion from float32 to float64

Hi, I have send patch v2 with proposed changes, please have a look https://lists.nongnu.org/archive/html/qemu-devel/2019-10/msg04264.html Matus -Original Message- From: Richard Henderson Sent: streda 16. októbra 2019 17:38 To: Matus Kysel ; qemu-devel@nongnu.org Cc: Peter Maydell ;

[PATCH v2] fdc/i8257: implement verify transfer mode

While working on the Tulip driver i tried to write some Teledisk images to a floppy image which didn't work. Turned out that Teledisk checks the written data by issuing a READ command to the FDC but running the DMA controller in VERIFY mode. As we ignored the DMA request in that case, the DMA

[PATCH] virtio: add check for inconsistent VQ in virtio_save()

From: Cheng Lin In a case, we have an not enabled VQ (virtio-net) which desc is NULL and get a last_avail_idx is not 0 from dpdk. As a result, it is successed to create a snapshot, but failed to revert it. Because in virtio_load(), there is an inconsistent check for VQ. (call virtio_load() in

Re: RFC: New device for zero-copy VM memory access

The windows driver source is now available also. https://github.com/gnif/Porthole-Guest-Driver I have also opted to rename the device to 'porthole', hopefully this name is acceptable. On 2019-10-30 09:53, ge...@hostfission.com wrote: Just to follow this up, here is a sample client

[PATCH v1 Resend] target/i386: set the CPUID level to 0x14 on old machine-type

The CPUID level need to be set to 0x14 manually on old machine-type if Intel PT is enabled in guest. e.g. in Qemu 3.1 -machine pc-i440fx-3.1 -cpu qemu64,+intel-pt will be CPUID[0].EAX(level)=7 and CPUID[7].EBX[25](intel-pt)=1. Some Intel PT capabilities are exposed by leaf 0x14 and the missing

Re: [PATCH v1] target/i386: set the CPUID level to 0x14 on old machine-type

Patchew URL: https://patchew.org/QEMU/1572413233-27015-1-git-send-email-luwei.k...@intel.com/ Hi, This series seems to have some coding style problems. See output below for more information: Subject: [PATCH v1] target/i386: set the CPUID level to 0x14 on old machine-type Type: series

Re: [PATCH v1 1/1] target/riscv: Remove atomic accesses to MIP CSR

On Tue, Oct 29, 2019 at 4:14 PM Palmer Dabbelt wrote: > > On Tue, 29 Oct 2019 03:49:23 PDT (-0700), alistai...@gmail.com wrote: > > On Fri, Oct 18, 2019 at 7:44 PM Alistair Francis > > wrote: > >> > >> On Fri, Oct 18, 2019 at 9:51 AM Palmer Dabbelt wrote: > >> > > >> > On Tue, 08 Oct 2019

Re: [PATCH] MAINTAINERS: Change to my personal email address

On Wed, Oct 30, 2019 at 5:57 AM Palmer Dabbelt wrote: > > I'm leaving SiFive in a bit less than two weeks, which means I'll be > losing my @sifive email address. I don't have my new email address yet, > so I'm switching over to my personal address instead. > > Signed-off-by: Palmer Dabbelt >

[PATCH v1] target/i386: set the CPUID level to 0x14 on old machine-type

The CPUID level need to be set to 0x14 manually on old machine-type if Intel PT is enabled in guest. e.g. in Qemu 3.1 -machine pc-i440fx-3.1 -cpu qemu64,+intel-pt will be CPUID[0].EAX(level)=7 and CPUID[7].EBX[25](intel-pt)=1. Some Intel PT capabilities are exposed by leaf 0x14 and the missing

Re: [PULL 00/20] hw/i386/pc: Split PIIX3 southbridge from i440FX northbridge

On Mon, 28 Oct 2019 at 17:48, Philippe Mathieu-Daudé wrote: > > Hi Peter, > > This is a X86/MIPS pull, Paolo and Aleksandar are OK I send it: > > https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg04959.html > > Regards, > > Phil. > > The following changes since commit