> -Original Message-
> From: Philippe Mathieu-Daudé On Behalf Of
> Philippe Mathieu-Daudé
> Sent: 20 September 2020 12:44
> To: Markus Armbruster ; qemu-devel@nongnu.org
> Cc: Laurent Vivier ; Paolo Bonzini ;
> Anthony Perard
> ; Stefano Stabellini ;
> Daniel P. Berrangé
> ; Eduardo Hab
On 9/21/20 8:48 AM, Pavel Dovgalyuk wrote:
> On 20.09.2020 10:58, Paolo Bonzini wrote:
>> On 14/09/20 08:06, Pavel Dovgalyuk wrote:
>>> GDB remote protocol supports reverse debugging of the targets.
>>> It includes 'reverse step' and 'reverse continue' operations.
>>> The first one finds the previo
John Snow writes:
> On 9/18/20 6:33 AM, Markus Armbruster wrote:
>> John Snow writes:
[...]
>>> Embedded templates are always gonna look kinda nasty, I think, because
>>> you're trying to fight style guidelines in two languages
>>> simultaneously and it's never gonna quite work out exactly how y
On Fri, 2020-09-18 at 00:20 -0400, Eduardo Habkost wrote:
> On Fri, Sep 18, 2020 at 10:18:56AM +0800, Robert Hoo wrote:
> > On Thu, 2020-09-17 at 14:01 -0400, Eduardo Habkost wrote:
> > > On Wed, Sep 16, 2020 at 04:37:14PM +0800, Robert Hoo wrote:
> > > > Going to obsolete Icelake-Client CPU models
John Snow writes:
> On 9/18/20 6:55 AM, Markus Armbruster wrote:
>> John Snow writes:
>
>>> We'll get to them in due time. For now, please admire the lipstick.
>> If I take off my glasses and step six feet back, I just might be
>> able to
>> overlook it.
>>
>
> I consider writing a nice __repr_
Hi Eduardo,
This patch set will remove some limitations of Intel PT CPUID information.
1. The "IP payloads" feature will disable the Intel PT in guests and it
will be coming soon.
2. To make the live migration safe, we set the Intel PT CPUID as a constant
value(Icelake server CPUID).
Il lun 21 set 2020, 02:29 Richard Henderson
ha scritto:
> On 9/20/20 6:07 AM, Paolo Bonzini wrote:
> > Some lines are only meaningful for user-mode targets, remove them.
> >
> > Signed-off-by: Paolo Bonzini
> > ---
>
> This seems like it could be folded with the previous.
>
The previous patch w
On Tue, Sep 15, 2020 at 11:52:57PM +0530, P J P wrote:
> From: Prasad J Pandit
>
> Hello,
>
> * While servicing transfer descriptors(TD) in ohci_service[_iso]_td
> routines, it may lead to out-of-bounds access and/or infinite loop
> issues, as the OHCI controller driver may supply malicious
> -Original Message-
> From: Anthony PERARD
> Sent: 18 September 2020 15:53
> To: qemu-devel@nongnu.org
> Cc: Paul Durrant ; Stefano Stabellini ;
> Anthony PERARD
> ; John Snow ;
> qemu-bl...@nongnu.org
> Subject: [PATCH] xen: rework pci_piix3_xen_ide_unplug
>
> This is to allow IDE dis
Machine-specific patches extracted from v2 [*] and rebased.
Housekeeping the QOM model to easily add more machines.
Patches missing review: 1-3,7.
[*] https://www.mail-archive.com/qemu-devel@nongnu.org/msg680135.html
Based-on: <20200921035257.434532-1-f4...@amsat.org>
Philippe Mathieu-Daudé (8
The 'first_cpu' is more a QEMU accelerator-related concept
than a variable the machine requires to use.
Since the machine is aware of its CPUs, directly use the
first one to load the firmware.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/arm/raspi.c | 3 ++-
1 file changed, 2 insertions(+), 1 de
Display the board revision in the machine description.
Before:
$ qemu-system-aarch64 -M help | fgrep raspi
raspi2 Raspberry Pi 2B
raspi3 Raspberry Pi 3B
After:
raspi2 Raspberry Pi 2B (revision 1.1)
raspi3 Raspberry Pi 3B (revisio
As we only support a reduced set of the REV_CODE_PROCESSOR id
encoded in the board revision, define the PROCESSOR_ID values
as an enum. We can simplify the board_soc_type and cores_count
methods.
Reviewed-by: Luc Michel
Signed-off-by: Philippe Mathieu-Daudé
---
hw/arm/raspi.c | 45 +
The arm_boot_info structure belong to the machine,
move it to RaspiMachineState.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/arm/raspi.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/hw/arm/raspi.c b/hw/arm/raspi.c
index 8716a80a75e..16e6c8
Now that we can instantiate different machines based on their
board_rev register value, we can have various raspi2 and raspi3.
In commit fc78a990ec103 we corrected the machine description.
Correct the machine names too. For backward compatibility, add
an alias to the previous generic name.
Review
We expected the 'version' ID to match the board processor ID,
but this is not always true (for example boards with revision
id 0xa02042/0xa22042 are Raspberry Pi 2 with a BCM2837 SoC).
This was not important because we were not modelling them, but
since the recent refactor now allow to model these
Using class_data pointer to create a MachineClass is not
the recommended way anymore. The correct way is to open-code
the MachineClass::fields in the class_init() method.
We can not use TYPE_RASPI_MACHINE::class_base_init() because
it is called *before* each machine class_init(), therefore the
boa
Hi,
> Fix compiler deprecation warnings with Spice > 0.14.3 (not released
> yet). We may want to wait until newer version is actually released to
> apply the patch.
Probably makes sense, just in case. It's not like this is an urgent
fix.
> +#if SPICE_SERVER_VERSION < 0x000e04 /* release 0.14.
John Snow writes:
> On 9/18/20 7:55 AM, Markus Armbruster wrote:
>> Ignorant question: why does this come after PATCH 13 "qapi/common.py:
>> add notational type hints", but before all the other patches adding type
>> hints?
>> John Snow writes:
>>
>>> Fix two very minor issues, and then establi
The firmware load address depends of the SoC ("processor id") used,
not of the version of the board.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/arm/raspi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/arm/raspi.c b/hw/arm/raspi.c
index 0d8e5a34c78..ae98a2fbfca 10064
John Snow writes:
> On 9/18/20 7:55 AM, Markus Armbruster wrote:
>> Ignorant question: why does this come after PATCH 13 "qapi/common.py:
>> add notational type hints", but before all the other patches adding type
>> hints?
>> John Snow writes:
>>
>>> Fix two very minor issues, and then establi
On Thu, Sep 17, 2020 at 10:22:41AM +0400, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Note that for consistency, we use the same logic as MonitorsConfig to
> figure out the associated monitor. However, I can't find traces of the
> discussion/patches about the "new spice-serv
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 if the Error* pointer is
> set.
> Provide the same ability to the BusRealize type.
>
> Signed
On Sat, Sep 19, 2020 at 09:11:39PM +0530, Ani Sinha wrote:
> Object property insertion code iterates over an integer to get an unused
> index that can be used as an unique name for an object property. This loop
> increments the integer value indefinitely. Although very unlikely, this can
> still ca
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 process which is far more
>
> than just
v4:
- Patch 1: fixed commit message and warning message [Cornelia]
- Patch 3: added comment in the code [Cornelia]
- Added Cornelia's R-b tags
v3: https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06549.html
v2: https://lists.gnu.org/archive/html/qemu-devel/2020-08/msg04437.html
v1
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 vhost-vsock-pci,guest-cid=
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 vhost-user-v
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. David Alan Gilbert
> Cc: Markus Armbruster
>
> Same problem I had with the pf
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 mi
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).
Cc:
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 better even when single process is doing
> I/O in client).
Let's underst
On Fri, Sep 18, 2020 at 10:59 AM Denis V. Lunev wrote:
> On 9/17/20 3:41 PM, Stefan Hajnoczi wrote:
> > On Wed, Sep 16, 2020 at 5:43 PM Denis V. Lunev wrote:
> >> On 9/16/20 5:07 PM, Denis V. Lunev wrote:
> >>> I will make a check today.
> >>>
> >>> Talking about our performance measurements, we
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.
>
> Laurent Vivier (2):
> util/hexdump: introduce qemu_hexdump_line()
> vhost-vdpa:
* 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 virtiofs-tests.
>
> https://github.com/rhvgoyal/virtiofs-tests
>
> And here are the
On Fri, Aug 21, 2020 at 9:38 PM Stefano Garzarella wrote:
> On Fri, Aug 21, 2020 at 07:55:02PM +0200, Philippe Mathieu-Daudé wrote:
> > On 8/21/20 6:54 PM, Stefano Garzarella wrote:
> > > Install liburing-devel dependencies to get better coverage on
> > > io-uring stuff (block/io_uring.c and util/
On 18.09.20 22:11, Vladimir Sementsov-Ogievskiy wrote:
> 17.07.2020 16:45, Max Reitz wrote:
>> On 01.06.20 20:11, Vladimir Sementsov-Ogievskiy wrote:
>>> Refactor common path to use BlockCopyCallState pointer as parameter, to
>>> prepare it for use in asynchronous block-copy (at least, we'll need t
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.kraxel.org/qemu tags/usb-20200921-pu
Just use qemu_open_old() for a quick fix, switch
to better error handling left for another day.
Fixes: 448058aa99aa ("util: rename qemu_open() to qemu_open_old()")
Cc: César Belley
Signed-off-by: Gerd Hoffmann
Reviewed-by: Daniel P. Berrangé
Message-id: 20200918110122.9121-1-kra...@redhat.com
-
On Sun, 20 Sep 2020 15:25:19 +0200
"Maciej S. Szmigiero" wrote:
> From: "Maciej S. Szmigiero"
>From description it sounds like an alternative of virtio-mem,
CCing David.
> This series adds a Hyper-V Dynamic Memory Protocol driver (hv-balloon)
> and its protocol definitions.
> Also included is
From: Prasad J Pandit
While servicing OHCI transfer descriptors(TD), ohci_service_iso_td
retires a TD if it has passed its time frame. It does not check if
the TD was already processed once and holds an error code in TD_CC.
It may happen if the TD list has a loop. Add check to avoid an
infinite l
From: Prasad J Pandit
While servicing the OHCI transfer descriptors(TD), OHCI host
controller derives variables 'start_addr', 'end_addr', 'len'
etc. from values supplied by the host controller driver.
Host controller driver may supply values such that using
above variables leads to out-of-bounds
Object property insertion code iterates over an integer to get an unused
index that can be used as an unique name for an object property. This loop
increments the integer value indefinitely. Although very unlikely, this can
still cause an integer overflow.
In this change, we fix the above code by c
* Stefan Hajnoczi (stefa...@redhat.com) wrote:
> From: "Harry G. Coin"
>
> The virtiofsd --help output documents the cache=auto default value but
> the man page does not. Fix this.
>
> Signed-off-by: Harry G. Coin
> Signed-off-by: Stefan Hajnoczi
Reviewed-by: Dr. David Alan Gilbert
Thanks,
On 20.09.20 15:25, Maciej S. Szmigiero wrote:
> From: "Maciej S. Szmigiero"
>
> This series adds a Hyper-V Dynamic Memory Protocol driver (hv-balloon)
> and its protocol definitions.
> Also included is a driver providing backing devices for memory hot-add
> protocols ("haprots").
>
> A haprot de
On Mon, Sep 21, 2020 at 02:37:04PM +0530, Ani Sinha wrote:
> Object property insertion code iterates over an integer to get an unused
> index that can be used as an unique name for an object property. This loop
> increments the integer value indefinitely. Although very unlikely, this can
> still ca
marcandre.lur...@redhat.com writes:
> From: Marc-André Lureau
>
> Hi,
>
> Among the QEMU developers, there is a desire to use Rust. (see previous
> thread from Stefan "Why QEMU should move from C to Rust", the rust-vmm
> related projects and other experiments).
>
> Thanks to our QAPI type system
Mark Cave-Ayland writes:
> Instead use qdev_set_nic_properties() to configure the on-board NIC at the
> sun4m machine level.
>
> Signed-off-by: Mark Cave-Ayland
> ---
> hw/dma/sparc32_dma.c | 5 -
> hw/sparc/sun4m.c | 21 +
> 2 files changed, 13 insertions(+), 13 de
On 21/09/20 11:16, Markus Armbruster wrote:
> QMP is an *external* interface.
>
> It supports compatible evolution: we can make certain kinds of changes
> without affecting clients. These include:
>
> * Adding optional arguments
>
> * Adding results
>
> * Adding values to an enumeration type,
On 21.09.20 11:00, Igor Mammedov wrote:
> On Sun, 20 Sep 2020 15:25:19 +0200
> "Maciej S. Szmigiero" wrote:
>
>> From: "Maciej S. Szmigiero"
>
> From description it sounds like an alternative of virtio-mem,
> CCing David.
Hah! Was already replying when your cc came in (thanks anyway!).
Not qu
Object property insertion code iterates over an integer to get an unused
index that can be used as an unique name for an object property. This loop
increments the integer value indefinitely. Although very unlikely, this can
still cause an integer overflow.
In this change, we fix the above code by c
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 if the Error* pointer is
>> set.
>> Prov
On Mon, 21 Sep 2020 10:38:04 +0200
Stefano Garzarella wrote:
> 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 decl
On Mon, Sep 21, 2020 at 11:40:54AM +0200, Cornelia Huck wrote:
> On Mon, 21 Sep 2020 10:38:04 +0200
> Stefano Garzarella wrote:
>
> > 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
On Mon, 21 Sep 2020 10:38:05 +0200
Stefano Garzarella wrote:
> 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,g
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
---
Note that I found the above issue while trying to debug
xen-load-devices-state which simply fails (prints "Configuratio
Hi Mark,
On 9/20/20 10:20 AM, Mark Cave-Ayland wrote:
> Instead use qdev_set_nic_properties() to configure the on-board NIC at the
> sun4m machine level.
>
> Signed-off-by: Mark Cave-Ayland
> ---
> hw/dma/sparc32_dma.c | 5 -
> hw/sparc/sun4m.c | 21 +
> 2 files cha
On Mon, Sep 21, 2020 at 11:46:02AM +0200, Cornelia Huck wrote:
> On Mon, 21 Sep 2020 10:38:05 +0200
> Stefano Garzarella wrote:
>
> > Commit 9b3a35ec82 ("virtio: verify that legacy support is not
> > accidentally on") added a safety check that requires to set
> > 'disable-legacy=on' on vhost-vsoc
Hi
On Mon, Sep 21, 2020 at 1:16 PM Markus Armbruster wrote:
>
> marcandre.lur...@redhat.com writes:
>
> > From: Marc-André Lureau
> >
> > Hi,
> >
> > Among the QEMU developers, there is a desire to use Rust. (see previous
> > thread from Stefan "Why QEMU should move from C to Rust", the rust-vmm
Hi
On Mon, Sep 21, 2020 at 1:16 PM Markus Armbruster wrote:
>
> marcandre.lur...@redhat.com writes:
>
> > From: Marc-André Lureau
> >
> > Hi,
> >
> > Among the QEMU developers, there is a desire to use Rust. (see previous
> > thread from Stefan "Why QEMU should move from C to Rust", the rust-vmm
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:
> >
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 Bodd
+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. David
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 Ed
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 Linux-inspi
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
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
--- a/block/sheepdo
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 would
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
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-202
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 sho
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 wrapped
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
docume
* 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 Ala
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 tags/for
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 ++
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
Reviewed
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. VHOST_IO
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 Gilber
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 e
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 introd
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: 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:
<6f38139d24a1be703a6f1c7d983faccdf21d2a9a.1599813294.git
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
virtio_queu
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: Paravirtualized
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
initializ
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
---
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 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:
<4d3e683a87557bcef520826c54aa3e5ab7c64111.1599813294.git.dimas.
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
qemu-sy
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.
Signed-off
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 se
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 d
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:
>
>
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: Thoma
* 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
> >
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 fil
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()
contrib/l
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
---
contrib/libvhost-user/lib
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 th
1 - 100 of 377 matches
Mail list logo
