On 200921 0743, Philippe Mathieu-Daudé wrote:
> Hi Alexander,
>
> On 9/21/20 4:24 AM, Alexander Bulekov wrote:
> > This is a generic fuzzer designed to fuzz a virtual device's
> > MemoryRegions, as long as they exist within the Memory or Port IO (if it
> > exists) AddressSpaces. The fuzzer's
I had to rebase the series due to conflicting changes on master. There
are no other differences.
Berto
v4:
- Fix rebase conflicts after cb8503159a
v3: https://lists.gnu.org/archive/html/qemu-block/2020-09/msg00912.html
- Add a new patch to improve the reporting of BDRV_BLOCK_ZERO [Vladimir]
-
If a BlockDriverState supports backing files but has none then any
unallocated area reads back as zeroes.
bdrv_co_block_status() is only reporting this is if want_zero is true,
but this is an inexpensive test and there is no reason not to do it in
all cases.
Suggested-by: Vladimir
On 9/21/20 1:34 PM, Stefan Hajnoczi wrote:
> vu_panic() is not guaranteed to exit the program. Return early when
> errors are encountered.
>
> Note that libvhost-user does not have an "unmap" operation for mapped
> descriptors. Therefore it is correct to return without explicit cleanup.
>
>
On 9/21/20 1:34 PM, Stefan Hajnoczi wrote:
> vu_panic() is not guaranteed to exit the program. Return early when
> errors are encountered.
>
> Signed-off-by: Stefan Hajnoczi
> ---
> contrib/libvhost-user/libvhost-user.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
Michael S. Tsirkin 于2020年9月21日周一 下午8:31写道：
>
> On Mon, Sep 21, 2020 at 07:44:42PM +0800, Li Qiang wrote:
> > Michael S. Tsirkin 于2020年9月21日周一 下午7:30写道：
> > >
> > > The following changes since commit
> > > 053a4177817db307ec854356e95b5b350800a216:
> > >
> > > Merge remote-tracking branch
> >
If error occurs while processing the virtio request we should call
'virtqueue_detach_element' to detach the element from the virtqueue
before free the elem.
Fixes: 5f503cd9f3 ("virtio-pmem: add virtio device")
Reviewed-by: Pankaj Gupta
Signed-off-by: Li Qiang
---
hw/virtio/virtio-pmem.c | 1 +
On 9/21/20 6:48 AM, Dr. David Alan Gilbert wrote:
> * Tom Lendacky (thomas.lenda...@amd.com) wrote:
>> On 9/18/20 5:00 AM, Dr. David Alan Gilbert wrote:
>>> * Tom Lendacky (thomas.lenda...@amd.com) wrote:
On 9/17/20 12:28 PM, Dr. David Alan Gilbert wrote:
> * Tom Lendacky
On 9/21/20 2:24 PM, Dr. David Alan Gilbert wrote:
> * Markus Armbruster (arm...@redhat.com) wrote:
>> Philippe Mathieu-Daudé writes:
>>
>>> +Paolo & Kevin.
>>>
>>> On 9/21/20 10:40 AM, Markus Armbruster wrote:
Philippe Mathieu-Daudé writes:
> As it is legal to WRITE/ERASE the
On 21/09/20 15:44, Stefan Hajnoczi wrote:
> On Mon, Sep 21, 2020 at 01:15:30PM +0200, Paolo Bonzini wrote:
>> On 21/09/20 12:41, Stefan Hajnoczi wrote:
>>> The upshot is that all atomic variables in QEMU need to use C11 Atomic
>>> atomic_* types. This is a big change!
>>
>> The main issue with
On 9/21/20 1:45 AM, Dov Murik wrote:
> On 16/09/2020 0:29, Tom Lendacky wrote:
>> From: Tom Lendacky
>>
>> Provide initial support for SEV-ES. This includes creating a function to
>> indicate the guest is an SEV-ES guest (which will return false until all
>> support is in place), performing the
Patchew URL: https://patchew.org/QEMU/20200921112913.555392-1-...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20200921112913.555392-1-...@redhat.com
Subject: [PULL v3 00/15] virtio,pc,acpi: fixes, tests
On Mon, Sep 21, 2020 at 09:35:16AM -0400, Vivek Goyal wrote:
> On Mon, Sep 21, 2020 at 09:50:19AM +0100, Dr. David Alan Gilbert wrote:
> > * Vivek Goyal (vgo...@redhat.com) wrote:
> > > Hi All,
> > >
> > > virtiofsd default thread pool size is 64. To me it feels that in most of
> > > the cases
On Mon, Sep 21, 2020 at 03:47:56PM +0200, Peter Lieven wrote:
> Am 21.09.20 um 10:29 schrieb Daniel P. Berrangé:
> > On Sun, Sep 20, 2020 at 10:24:41PM +0200, Peter Lieven wrote:
> > > Hi Qemu folks,
> > >
> > >
> > > is there a BCP to limit just the maximum usage of a virtual (KVM) cpu?
> > >
On 21/09/20 15:38, Alexander Bulekov wrote:
> Hi Paolo,
> These are the builds with clang coverage enabled.
> The normal fuzzing builds are succeeding now (log from this morning:
> https://oss-fuzz-build-logs.storage.googleapis.com/log-a426424c-cae4-407a-ae7b-205a9ae59286.txt
> )
>
> I already
On Fri, Sep 04, 2020 at 05:08:36PM +0100, Daniel P. Berrangé wrote:
> On Fri, Sep 04, 2020 at 04:35:34PM +0100, Alex Bennée wrote:
> >
> > Hi,
> >
> > Given our growing reliance on GitLab and the recent announcement about
> > free tier minutes:
> >
> >
I've reproduced the problem with HEAD of master, qemu-4.2.0 and
qemu-4.0.0.
I think the problem comes from the the kernel.
Host CPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
Host kernel: 5.8.4-200.fc32.x86_64
--
You received this bug notification because you are a member of qemu-
devel-ml,
23.07.2020 12:47, Max Reitz wrote:
On 01.06.20 20:11, Vladimir Sementsov-Ogievskiy wrote:
This brings async request handling and block-status driven chunk sizes
to backup out of the box, which improves backup performance.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
Am 21.09.20 um 10:29 schrieb Daniel P. Berrangé:
On Sun, Sep 20, 2020 at 10:24:41PM +0200, Peter Lieven wrote:
Hi Qemu folks,
is there a BCP to limit just the maximum usage of a virtual (KVM) cpu?
I know that there are many approaches, but as far as I know they all limit the
complete qemu
Dear Stefan,
Am 21.09.20 um 15:10 schrieb Stefan Reiter:
since SeaBIOS 1.14.0 (QEMU 5.1) VMs with LVM root disks spanning more
than one PV fail to boot, if only the first is set as bootable. I
believe this is due to the changes in SeaBIOS only initializing drives
marked as 'bootable' by
On Mon, Sep 21, 2020 at 01:15:30PM +0200, Paolo Bonzini wrote:
> On 21/09/20 12:41, Stefan Hajnoczi wrote:
> > The upshot is that all atomic variables in QEMU need to use C11 Atomic
> > atomic_* types. This is a big change!
>
> The main issue with this is that C11 atomic types do too much magic,
On 200921 1410, Paolo Bonzini wrote:
> On 21/09/20 12:10, ClusterFuzz-External via monorail wrote:
> >
> > Comment #2 on issue 25514 by ClusterFuzz-External: qemu: Coverage build
> > failure
> > https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25514#c2
> >
> > Friendly reminder that the the
On Mon, Sep 21, 2020 at 09:39:23AM +0100, Stefan Hajnoczi wrote:
> On Fri, Sep 18, 2020 at 05:34:36PM -0400, Vivek Goyal wrote:
> > And here are the comparision results. To me it seems that by default
> > we should switch to 1 thread (Till we can figure out how to make
> > multi thread performance
On Mon, Sep 21, 2020 at 09:50:19AM +0100, Dr. David Alan Gilbert wrote:
> * Vivek Goyal (vgo...@redhat.com) wrote:
> > Hi All,
> >
> > virtiofsd default thread pool size is 64. To me it feels that in most of
> > the cases thread pool size 1 performs better than thread pool size 64.
> >
> > I ran
On 9/21/20 8:09 PM, Paolo Bonzini wrote:
On 21/09/20 04:22, zhenwei pi wrote:
Hi,
A patchset about handling 'MCE' might have been ignored, can anyone tell
me whether the purpose is reasonable?
https://patchwork.kernel.org/cover/11773795/
Yes, it's very useful. Just one thing,
On 21/09/20 12:54, Alex Bennée wrote:
> Something is breaking when switching to a branch with this on from
> current master:
>
> Linking target qemu-hppa
> /usr/bin/ld: libcommon.fa.p/disas_alpha.c.o: in function `print_insn_alpha':
>
On 9/21/20 8:48 PM, Peter Maydell wrote:
On Mon, 14 Sep 2020 at 14:53, zhenwei pi wrote:
Introduce 4 memory failure events for a guest. Then uplayer could
know when/why/what happened to a guest during hitting a hardware
memory failure.
Signed-off-by: zhenwei pi
---
+##
+#
Hi list,
since SeaBIOS 1.14.0 (QEMU 5.1) VMs with LVM root disks spanning more
than one PV fail to boot, if only the first is set as bootable. I
believe this is due to the changes in SeaBIOS only initializing drives
marked as 'bootable' by QEMU.
One fix is to mark all disks containing root
Mailing list discussion about how to fix this:
https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg07392.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1895471
Title:
compilation error
On Fri, 18 Sep 2020 10:51:22 +0200
David Hildenbrand wrote:
> Recent upstream Linux uses the MONITOR CALL instruction for things like
> BUG_ON() and WARN_ON(). We currently inject an operation exception when
> we hit a MONITOR CALL instruction - which is wrong, as the instruction
> is not glued
Add trace functionis in vhost-vdpa.c.
All traces from this file can be enabled with '-trace vhost_vdpa*'.
Acked-by: Stefan Hajnoczi
Signed-off-by: Laurent Vivier
---
hw/virtio/trace-events | 29 ++
hw/virtio/vhost-vdpa.c | 86 +++---
2 files
Add trace events functions in vdpa functions.
Modify qemu_hexdump() to be able to dump the vdpa config
in trace logs in hexadecimal form.
v2: fix problems reported by checkpatch (TAB, missing 0x and 80+ line)
added Stefan Acked-by
Laurent Vivier (2):
util/hexdump: introduce
Dumping one line of hexadecimal/ASCII from a buffer is often needed.
Move this part from qemu_hexdump() and use it
Acked-by: Stefan Hajnoczi
Signed-off-by: Laurent Vivier
---
include/qemu-common.h | 8 +++
util/hexdump.c| 54 +++
2 files
Philippe Mathieu-Daudé writes:
> On 9/21/20 10:19 AM, Markus Armbruster wrote:
>> Philippe Mathieu-Daudé writes:
>>
>>> Commit 9940b2cfbc0 introduced qdev_realize() and qbus_realize()
>>> with the ability to return a boolean value if an error occured,
>>> thus the caller does not need to check
On Mon, Sep 21, 2020 at 02:54:15PM +0200, Peter Krempa wrote:
> On Mon, Sep 21, 2020 at 13:45:14 +0100, Richard W.M. Jones wrote:
> > Some general comments on using the patch:
> >
> > * For libguestfs I chose to add
> >
> > -compat deprecated-input=reject,deprecated-output=hide
> >
> > This
On Mon, 14 Sep 2020 at 09:55, Markus Armbruster wrote:
>
> New option -compat lets you configure what to do when deprecated
> interfaces get used. This is intended for testing users of the
> management interfaces. It is experimental.
>
> -compat deprecated-input= configures what to do when
>
On Mon, Sep 21, 2020 at 13:45:14 +0100, Richard W.M. Jones wrote:
> Some general comments on using the patch:
>
> * For libguestfs I chose to add
>
> -compat deprecated-input=reject,deprecated-output=hide
>
> This is only enabled in developer builds of libguestfs when we
> are running
On Mon, Sep 21, 2020 at 7:06 PM Alex Bennée wrote:
>
>
> Alex Bennée writes:
>
> > Richard Henderson writes:
> >
> >> There are better ways to do this, e.g. meson cmake subproject,
> >> but that requires cmake 3.7 and some of our CI environments
> >> only provide cmake 3.5.
> >>
> >> Nor can we
On Mon, 14 Sep 2020 at 14:53, zhenwei pi wrote:
>
> Introduce 4 memory failure events for a guest. Then uplayer could
> know when/why/what happened to a guest during hitting a hardware
> memory failure.
>
> Signed-off-by: zhenwei pi
> ---
> +##
> +# @MemoryFailureAction:
> +#
> +# Host memory
Some general comments on using the patch:
* For libguestfs I chose to add
-compat deprecated-input=reject,deprecated-output=hide
This is only enabled in developer builds of libguestfs when we
are running qemu directly (not via libvirt). The patch for
this is attached.
* What's the
On 21/09/2020 14:32, Michael S. Tsirkin wrote:
> On Mon, Sep 21, 2020 at 09:41:36AM +0100, Stefan Hajnoczi wrote:
>> On Sun, Sep 20, 2020 at 06:24:32PM +0200, Laurent Vivier wrote:
>>> Add trace events functions in vdpa functions.
>>>
>>> Modify qemu_hexdump() to be able to dump the vdpa config
On Mon, Sep 21, 2020 at 01:33:47PM +0200, Gerd Hoffmann wrote:
> On Fri, Sep 18, 2020 at 08:36:14AM -0400, Michael S. Tsirkin wrote:
> > On Fri, Sep 18, 2020 at 02:19:11PM +0200, Gerd Hoffmann wrote:
> > > Uses the existing gpex device which is also used as pcie host bridge on
> > > arm/aarch64.
On Mon, Sep 21, 2020 at 07:44:42PM +0800, Li Qiang wrote:
> Michael S. Tsirkin 于2020年9月21日周一 下午7:30写道：
> >
> > The following changes since commit 053a4177817db307ec854356e95b5b350800a216:
> >
> > Merge remote-tracking branch 'remotes/philmd-gitlab/tags/fw_cfg-20200918'
> > into staging
On 21/09/2020 14:17, Dr. David Alan Gilbert wrote:
* Dov Murik (dovmu...@linux.vnet.ibm.com) wrote:
When running the xen-save-devices-state QMP command, if the filename
already exists it will be truncated before dumping the devices' state
into it.
Signed-off-by: Dov Murik
---
OK, that
On Mon, Sep 21, 2020 at 09:41:36AM +0100, Stefan Hajnoczi wrote:
> On Sun, Sep 20, 2020 at 06:24:32PM +0200, Laurent Vivier wrote:
> > Add trace events functions in vdpa functions.
> >
> > Modify qemu_hexdump() to be able to dump the vdpa config
> > in trace logs in hexadecimal form.
> >
> >
On Mon, Sep 21, 2020 at 01:46:01PM +0200, Igor Mammedov wrote:
> On Mon, 7 Sep 2020 07:23:38 -0400
> Igor Mammedov wrote:
>
> > v5:
> > - fix hotplug on Windows when there is more than 256 possible CPUs
> > (Windows isn't able to handle VarPackage over 255 elements
> > so process
Commit 9b3a35ec82 ("virtio: verify that legacy support is not
accidentally on") added a safety check that requires to set
'disable-legacy=on' on vhost-user-vsock-pci device:
$ ./qemu-system-x86_64 ... \
-chardev socket,id=char0,reconnect=0,path=/tmp/vhost4.socket \
-device
virtio-vsock was introduced after the release of VIRTIO 1.0
specifications, so it should be 'modern-only'.
This patch forces virtio version 1 as done for vhost-vsock-pci.
To avoid migration issues, we force virtio version 1 only when
legacy check is enabled in the new machine types (>= 5.1).
On 20/09/2020 20:03, no-re...@patchew.org wrote:
> Patchew URL:
> https://patchew.org/QEMU/20200920162434.868041-1-lviv...@redhat.com/
>
>
>
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> Type: series
> Message-id:
Commit 9b3a35ec82 ("virtio: verify that legacy support is not accidentally
on") added a check that returns an error if legacy support is on, but the
device does not support legacy.
Unfortunately some devices were wrongly declared legacy capable even if
they were not (e.g vhost-vsock).
To avoid
Commit 9b3a35ec82 ("virtio: verify that legacy support is not
accidentally on") added a safety check that requires to set
'disable-legacy=on' on vhost-vsock-pci device:
$ ./qemu-system-x86_64 ... -device vhost-vsock-pci,guest-cid=5
qemu-system-x86_64: -device
v5:
- Patch 2: added a phrase about transitional device in the commit
message [Cornelia]
- All patches reviewed by Cornelia
v4: https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg07353.html
v3: https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06549.html
v2:
On Fri, 18 Sep 2020 at 19:04, Eduardo Habkost wrote:
>
> Leftovers from pre-5.1.0 days.
>
> The following changes since commit 053a4177817db307ec854356e95b5b350800a216:
>
> Merge remote-tracking branch 'remotes/philmd-gitlab/tags/fw_cfg-20200918'
> into staging (2020-09-18 16:34:26 +0100)
>
>
* Markus Armbruster (arm...@redhat.com) wrote:
> Philippe Mathieu-Daudé writes:
>
> > +Paolo & Kevin.
> >
> > On 9/21/20 10:40 AM, Markus Armbruster wrote:
> >> Philippe Mathieu-Daudé writes:
> >>
> >>> As it is legal to WRITE/ERASE the address/block 0,
> >>> change the value of this
Philippe Mathieu-Daudé writes:
> +Paolo & Kevin.
>
> On 9/21/20 10:40 AM, Markus Armbruster wrote:
>> Philippe Mathieu-Daudé writes:
>>
>>> As it is legal to WRITE/ERASE the address/block 0,
>>> change the value of this definition to an illegal
>>> address: UINT32_MAX.
>>>
>>> Signed-off-by:
On 21/09/20 04:22, zhenwei pi wrote:
> Hi,
>
> A patchset about handling 'MCE' might have been ignored, can anyone tell
> me whether the purpose is reasonable?
>
> https://patchwork.kernel.org/cover/11773795/
Yes, it's very useful. Just one thing, "guest-mce" can be reported for
both AR and AO
On 21/09/20 12:10, ClusterFuzz-External via monorail wrote:
>
> Comment #2 on issue 25514 by ClusterFuzz-External: qemu: Coverage build
> failure
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25514#c2
>
> Friendly reminder that the the build is still failing.
> Please try to fix this
On Mon, Sep 14, 2020 at 10:08:50AM -0500, Eric Blake wrote:
> On 9/14/20 3:47 AM, Markus Armbruster wrote:
> >Policy is separate for input and output.
> >
> >Input policy can be "accept" (accept silently), or "reject" (reject
> >the request with an error).
> >
> >Output policy can be "accept"
Wire up "usb=on" machine option. When enabled add a sysbus xhci
controller with 8 ports. Declare it in the ACPI DSDT table so the
guest OS finds it.
Signed-off-by: Gerd Hoffmann
---
include/hw/i386/microvm.h | 5 -
hw/i386/acpi-microvm.c| 20
hw/i386/microvm.c
Add a comment with a table listing the IRQs,
both legacy pc and microvm side-by-side.
Signed-off-by: Gerd Hoffmann
---
include/hw/i386/microvm.h | 22 ++
1 file changed, 22 insertions(+)
diff --git a/include/hw/i386/microvm.h b/include/hw/i386/microvm.h
index
Hi,
interesting bug report - thanks lee, Kashyap and Sean - as well as Danil for
taking a look already.
If this would always fail no unplugs would work ever which I knew can't
be right as I test that. So we need to find what is different...
@Openstack people - is that reliably triggering at
vu_panic() is not guaranteed to exit the program. Return early when
errors are encountered.
Note that libvhost-user does not have an "unmap" operation for mapped
descriptors. Therefore it is correct to return without explicit cleanup.
Signed-off-by: Stefan Hajnoczi
---
vu_panic() is not guaranteed to exit the program. Return errors instead.
Most of the code already does this but I spotted some cases that weren't
handled yet.
Stefan Hajnoczi (2):
libvhost-user: return early on virtqueue errors
libvhost-user: return on error in vu_log_queue_fill()
This depends on the xhci sysfs patch series by
Sai Pavan Boddu
Gerd Hoffmann (2):
microvm: add irq table
microvm: add usb support
include/hw/i386/microvm.h | 25 +
hw/i386/acpi-microvm.c| 20
hw/i386/microvm.c | 12
3
* Tom Lendacky (thomas.lenda...@amd.com) wrote:
> On 9/18/20 5:00 AM, Dr. David Alan Gilbert wrote:
> > * Tom Lendacky (thomas.lenda...@amd.com) wrote:
> > > On 9/17/20 12:28 PM, Dr. David Alan Gilbert wrote:
> > > > * Tom Lendacky (thomas.lenda...@amd.com) wrote:
> > > > > From: Tom Lendacky
> >
From: Igor Mammedov
These were deprecated since 4.0, remove both HMP and QMP variants.
Users should use device_add command instead. To get list of
possible CPUs and options, use 'info hotpluggable-cpus' HMP
or query-hotpluggable-cpus QMP command.
Signed-off-by: Igor Mammedov
Reviewed-by:
Michael S. Tsirkin 于2020年9月21日周一 下午7:30写道：
>
> The following changes since commit 053a4177817db307ec854356e95b5b350800a216:
>
> Merge remote-tracking branch 'remotes/philmd-gitlab/tags/fw_cfg-20200918'
> into staging (2020-09-18 16:34:26 +0100)
>
> are available in the Git repository at:
>
>
On Fri, Sep 18, 2020 at 08:36:14AM -0400, Michael S. Tsirkin wrote:
> On Fri, Sep 18, 2020 at 02:19:11PM +0200, Gerd Hoffmann wrote:
> > Uses the existing gpex device which is also used as pcie host bridge on
> > arm/aarch64. For now only a 32bit mmio window and no ioport support.
> >
> > It is
On Mon, 7 Sep 2020 07:23:38 -0400
Igor Mammedov wrote:
> v5:
> - fix hotplug on Windows when there is more than 256 possible CPUs
> (Windows isn't able to handle VarPackage over 255 elements
> so process CPUs in batches)
> - fix off-by-one in package length (Laszlo)
> - fix not
From: Dima Stepanov
For now a QTEST_VHOST_USER_FIXME environment variable is used to
separate reconnect tests for the vhost-user-net device. Looks like the
reconnect functionality is pretty stable, so this separation is
deprecated.
Remove it and enable these tests for the default run.
On Fri, Sep 18, 2020 at 6:18 PM Apteryx <1896...@bugs.launchpad.net> wrote:
> Host CPU: AMD Ryzen 3900X
I also hit this test failure.
Host CPU: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
Host kernel: Linux 5.8.6-201.fc32.x86_64
qemu-system-x86_64: error: failed to set MSR 0x4b564d02 to 0x0
From: Dima Stepanov
Add support for the vhost-user-blk-pci device. This node can be used by
the vhost-user-blk tests. Tests for the vhost-user-blk device are added
in the following patches.
Signed-off-by: Dima Stepanov
Message-Id:
vu_panic() is not guaranteed to exit the program. Return early when
errors are encountered.
Signed-off-by: Stefan Hajnoczi
---
contrib/libvhost-user/libvhost-user.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/contrib/libvhost-user/libvhost-user.c
b/contrib/libvhost-user/libvhost-user.c
From: Dima Stepanov
Add vhost_user_ops structure for the vhost-user-blk device class. Add
the test_reconnect and test_migrate tests for this device.
Signed-off-by: Dima Stepanov
Reviewed-by: Raphael Norwitz
Message-Id:
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin
---
From: Dima Stepanov
For now only vhost-user-net device is supported by the test. Other
vhost-user devices are not tested. As a first step make source code
refactoring so new devices can reuse the same test routines. To make
this provide a new vhost_user_ops structure with the methods to
From: Li Qiang
If error occurs while processing the virtio request we should call
'virtqueue_detach_element' to detach the element from the virtqueue
before free the elem.
Signed-off-by: Li Qiang
Message-Id: <20200816142245.17556-1-liq...@163.com>
Fixes: 910b25766b ("virtio-mem:
From: Dima Stepanov
If the vhost-user-blk daemon provides only one virtqueue, but device was
added with several queues, then QEMU will send more VHOST-USER command
than expected by daemon side. The vhost_virtqueue_start() routine
handles such case by checking the return value from the
From: Dima Stepanov
Add new migrate_reconnect test for the vhost-user-blk device. Perform a
disconnect after sending response for the VHOST_USER_SET_LOG_BASE
command.
Signed-off-by: Dima Stepanov
Reviewed-by: Raphael Norwitz
Message-Id:
From: Dima Stepanov
vhost-user devices can get a disconnect in the middle of the VHOST-USER
handshake on the migration start. If disconnect event happened right
before sending next VHOST-USER command, then the vhost_dev_set_log()
call in the vhost_migration_log() function will return error. This
From: Eric Auger
Commit 9b3a35ec82 ("virtio: verify that legacy support is not
accidentally on") added a safety check that requires to set
'disable-legacy=on' on virtio-iommu-pci:
qemu-system-aarch64: -device virtio-iommu-pci: device is modern-only,
use disable-legacy=on
virtio-iommu was
From: Jason Wang
This patch tries to switch to use new kernel IOTLB format V2. Previous
version may have inconsistent ABI between 32bit and 64bit machines
because of the hole after type field. Refer kernel commit
("429711aec282 vhost: switch to use new message format") for more
information.
To
From: Jason Wang
To speed up the memory mapping updating between vhost-vDPA and vDPA
device driver, this patch passes the IOTLB batching flags via IOTLB
API. Two new flags was introduced, VHOST_IOTLB_BATCH_BEGIN is a hint
that a bathced IOTLB updating may be initiated from the
userspace.
From: David Hildenbrand
Unfortunately, a typo sneeked in: we want to set
auto_enable_numa_with_memdev to false, not auto_enable_numa_with_memhp.
Cc: qemu-sta...@nongnu.org # v5.1
Fixes: 195784a0cfad (numa: Auto-enable NUMA when any memory devices are
possible)
Reported-by: Dr. David Alan
From: Eric Auger
If realize fails, domains and endpoints trees may be NULL. On
unrealize(), this produces assertions:
"GLib: g_tree_destroy: assertion 'tree != NULL' failed"
Check that the trees are non NULL before destroying them.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Eric Auger
The following changes since commit 053a4177817db307ec854356e95b5b350800a216:
Merge remote-tracking branch 'remotes/philmd-gitlab/tags/fw_cfg-20200918'
into staging (2020-09-18 16:34:26 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git
From: Jason Wang
Update against Linux 5.9-rc4.
Cc: Cornelia Huck
Cc: Paolo Bonzini
Signed-off-by: Jason Wang
Message-Id: <20200907104903.31551-2-jasow...@redhat.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin
---
include/standard-headers/drm/drm_fourcc.h | 140
* Dov Murik (dovmu...@linux.vnet.ibm.com) wrote:
> When running the xen-save-devices-state QMP command, if the filename
> already exists it will be truncated before dumping the devices' state
> into it.
>
> Signed-off-by: Dov Murik
> ---
OK, that looks fine to me, so:
Reviewed-by: Dr. David
On 21/09/20 12:41, Stefan Hajnoczi wrote:
> The upshot is that all atomic variables in QEMU need to use C11 Atomic
> atomic_* types. This is a big change!
The main issue with this is that C11 atomic types do too much magic,
including defaulting to seq-cst operations for loads and stores. As
On 2020-09-19 10:22, Zhenyu Ye wrote:
> On 2020/9/18 22:06, Fam Zheng wrote:
> >
> > I can see how blocking in a slow io_submit can cause trouble for main
> > thread. I think one way to fix it (until it's made truly async in new
> > kernels) is moving the io_submit call to thread pool, and
From: Philippe Mathieu-Daudé
Commit a5d7eb6534a ("Add TSC2301 touchscreen & keypad controller")
added the MouseTransformInfo declaration in "ui/console.h",
however it is only used in "hw/input/tsc2xxx.h".
Reduce the structure exposure by moving it to the single include
where it is used.
This
The following changes since commit 053a4177817db307ec854356e95b5b350800a216:
Merge remote-tracking branch 'remotes/philmd-gitlab/tags/fw_cfg-20200918' i=
nto staging (2020-09-18 16:34:26 +0100)
are available in the Git repository at:
git://git.kraxel.org/qemu tags/input-20200921-pull
On Mon 21 Sep 2020 01:01:45 PM CEST, Philippe Mathieu-Daudé wrote:
> Use self-explicit NANOSECONDS_PER_SECOND definition instead
> of magic value.
>
> Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Alberto Garcia
Berto
Alex Bennée writes:
> Richard Henderson writes:
>
>> There are better ways to do this, e.g. meson cmake subproject,
>> but that requires cmake 3.7 and some of our CI environments
>> only provide cmake 3.5.
>>
>> Nor can we add a meson.build file to capstone/, because the git
>> submodule
Use self-explicit NANOSECONDS_PER_SECOND definition instead
of magic value.
Signed-off-by: Philippe Mathieu-Daudé
---
block/sheepdog.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/sheepdog.c b/block/sheepdog.c
index cbbebc1aaf2..cbc655a1a05 100644
---
Richard Henderson writes:
> There are better ways to do this, e.g. meson cmake subproject,
> but that requires cmake 3.7 and some of our CI environments
> only provide cmake 3.5.
>
> Nor can we add a meson.build file to capstone/, because the git
> submodule would then always report "untracked
This patch is incomplete but I am looking for feedback on the approach
before fully implementing it (which will involve lots of changes).
QEMU's atomic.h provides atomic operations and is intended to work with
or without . Some of the atomic.h APIs are from C11 Atomics
while others are
Hi Gerd,
Thanks, I will update this in V8.
Regards,
Sai Pavan
> -Original Message-
> From: Gerd Hoffmann
> Sent: Thursday, September 17, 2020 5:14 PM
> To: Sai Pavan Boddu
> Cc: Peter Maydell ; Markus Armbruster
> ; 'Marc-André Lureau'
> ; Paolo Bonzini ;
> Edgar Iglesias ; Francisco
+Paolo & Kevin.
On 9/21/20 10:40 AM, Markus Armbruster wrote:
> Philippe Mathieu-Daudé writes:
>
>> As it is legal to WRITE/ERASE the address/block 0,
>> change the value of this definition to an illegal
>> address: UINT32_MAX.
>>
>> Signed-off-by: Philippe Mathieu-Daudé
>> ---
>> Cc: Dr.
Hi Joel,
> -Original Message-
> From: Joel Stanley
> Sent: Thursday, September 17, 2020 6:25 AM
> To: Sai Pavan Boddu ; Cédric Le Goater
>
> Cc: Philippe Mathieu-Daudé ; Edgar Iglesias
> ; qemu-devel@nongnu.org
> Subject: Re: eMMC support
>
> On Wed, 16 Sep 2020 at 18:35, Sai Pavan
Hi Cedric,
> -Original Message-
> From: Cédric Le Goater
> Sent: Thursday, September 17, 2020 11:55 AM
> To: Joel Stanley ; Sai Pavan Boddu
> Cc: Philippe Mathieu-Daudé ; Edgar Iglesias
> ; qemu-devel@nongnu.org
> Subject: Re: eMMC support
>
> On 9/17/20 2:55 AM, Joel Stanley wrote:
>
201 - 300 of 366 matches
Mail list logo
