Hi
On Wed, Oct 18, 2023 at 5:38 PM Edmund Raile wrote:
>
> Previous implementation of both functions was blocking and caused guest
> freezes / crashes on host clipboard owner change.
> * use callbacks instead of waiting for GTK to deliver
>clipboard content type evaluation and contents
> *
Steve Sistare writes:
> Coverity diagnoses a possible out-of-range array index here ...
>
> static GSList *migration_blockers[MIG_MODE__MAX];
>
> fill_source_migration_info() {
> GSList *cur_blocker = migration_blockers[migrate_mode()];
>
> ... because it does not know that
On 13/11/23 20:52, David Woodhouse wrote:
On Mon, 2023-11-13 at 16:21 +0100, Philippe Mathieu-Daudé wrote:
"sysemu/xen.h" defines CONFIG_XEN_IS_POSSIBLE as a target-agnostic
version of CONFIG_XEN. Use it in order to use "sysemu/xen-mapcache.h"
in target-agnostic files.
Signed-off-by: Philippe
On Tue, 14 Nov 2023, Marc-André Lureau wrote:
Hi
On Wed, Nov 8, 2023 at 7:56 PM Kamay Xutax wrote:
Signed-off-by: Kamay Xutax
---
include/ui/sdl2.h | 5 ++
meson.build | 1 +
ui/meson.build | 1 +
ui/sdl2-clipboard.c | 147
The extensions zicntr and zihpm were officially added in the privilege
instruction set specification 1.12. However, QEMU has been implemented
them long before it and thus they are forced to be on during the cpu
initialization to ensure compatibility (see riscv_cpu_init).
Tested-by: Clément Chigot
On Fri, Nov 10, 2023 at 6:08 PM Richard Henderson
wrote:
>
> In cpu_exec_step_atomic, we did not set CF_LAST_IO, which can
> lead to a loop with cpu_io_recompile.
>
> But since 18a536f1f8 ("Always require can_do_io") we no longer need
> a flag to indicate when the last
QOM names currently don't have any enforced naming rules. This
can be problematic, e.g. when they are used on the command line
for the "-device" option (where the comma is used to separate
properties). To avoid that such problematic type names come in
again, let's restrict the set of acceptable
On 11/14/23 04:36, Marc-André Lureau wrote:
Hi
On Tue, Nov 14, 2023 at 6:12 AM Joelle van Dyne wrote:
Signed-off-by: Joelle van Dyne
Reviewed-by: Stefan Berger
nit: you also added tests for x86, could be a different patch?
For arm, the test fails until next patch with:
# starting
On 11/13/23 06:56, Christoph Muellner wrote:
From: Palmer Dabbelt
The Ztso extension is already ratified, this adds it as a CPU property
and adds various fences throughout the port in order to allow TSO
targets to function on weaker hosts. We need no fences for AMOs as
they're already SC,
Thomas Huth writes:
> Forgot to CC: qemu-devel (sorry) - thanks to Markus for the hint.
> So let's repeat it here:
>
> On 14/11/2023 10.31, Daniel P. Berrangé wrote:
>> On Tue, Nov 14, 2023 at 10:05:37AM +0100, Thomas Huth wrote:
>>> QOM names currently don't have any enforced naming rules. This
On 11/14/23 11:09, Zhenzhong Duan wrote:
From: Yi Liu
/dev/vfio/devices/vfioX may not exist. In that case it is still possible
to open /dev/char/$major:$minor instead. Add helper function to abstract
the cdev open.
Suggested-by: Jason Gunthorpe
Signed-off-by: Yi Liu
Signed-off-by: Zhenzhong
On 11/14/23 11:09, Zhenzhong Duan wrote:
This is a trivial optimization. If there is active container in space,
vfio_reset_handler will never be unregistered. So revert the check of
space->containers and return early.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Cédric Le Goater
Thanks,
C.
Reviewed-by: Claudio Fontana
On 11/10/23 18:08, Richard Henderson wrote:
> In cpu_exec_step_atomic, we did not set CF_LAST_IO, which can
> lead to a loop with cpu_io_recompile.
>
> But since 18a536f1f8 ("Always require can_do_io") we no longer need
> a flag to indicate when the last insn should
On 11/14/23 11:09, Zhenzhong Duan wrote:
Legacy vfio pci and iommufd cdev have different process to hot reset
vfio device, expand current code to abstract out pci_hot_reset callback
for legacy vfio, this same interface will also be used by iommufd
cdev vfio device.
Rename vfio_pci_hot_reset to
On 11/14/23 11:09, Zhenzhong Duan wrote:
This gives management tools like libvirt a chance to open the vfio
cdev with privilege and pass FD to qemu. This way qemu never needs
to have privilege to open a VFIO or iommu cdev node.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Matthew Rosato
On 11/14/23 11:09, Zhenzhong Duan wrote:
Now we support two types of iommu backends, let's add the capability
to select one of them. This depends on whether an iommufd object has
been linked with the vfio-ap device:
if the user wants to use the legacy backend, it shall not
link the vfio-ap
The intel_iommu test is currently succeeding with annoying warnings.
Add the proper asset hashes to avoid those.
Signed-off-by: Thomas Huth
---
tests/avocado/intel_iommu.py | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tests/avocado/intel_iommu.py
Previous commits re-organized the target-specific bits
from Xen files. We can now build the common files once
instead of per-target.
Only 4 files call libxen API (thus its CPPFLAGS):
- xen-hvm-common.c,
- xen_pt.c, xen_pt_graphics.c, xen_pt_msi.c
Signed-off-by: Philippe Mathieu-Daudé
---
xen-hvm.c calls xc_set_hvm_param() from ,
so better compile it with Xen CPPFLAGS.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/i386/xen/meson.build | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/hw/i386/xen/meson.build b/hw/i386/xen/meson.build
index
We don't need a target-specific header for common target-specific
prototypes. Declare xen_arch_handle_ioreq() and xen_arch_set_memory()
in "hw/xen/xen-hvm-common.h".
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: David Woodhouse
Reviewed-by: Richard Henderson
---
On Tue, 2023-11-14 at 13:25 +0100, Philippe Mathieu-Daudé wrote:
>
> As is CONFIG_XEN.
>
> Maybe be worth renaming CONFIG_ACCEL_XEN if you think we need
> guest hw specific CONFIG_foo_XEN variables.
I don't think so. We have CONFIG_XEN_BUS and CONFIG_XEN_EMU (from
commit 820c1aba519b) which I
On 11/14/23 11:09, Zhenzhong Duan wrote:
From: Yi Liu
Add the iommufd backend. The IOMMUFD container class is implemented
based on the new /dev/iommu user API. This backend obviously depends
on CONFIG_IOMMUFD.
So far, the iommufd backend doesn't support dirty page sync yet due
to missing
assertEquals() has been removed in Python 3.12 and should be replaced by
assertEqual(). See: https://docs.python.org/3.12/whatsnew/3.12.html#id3
Signed-off-by: Thomas Huth
---
docs/devel/testing.rst | 2 +-
tests/avocado/cpu_queries.py| 2 +-
On 11/14/23 11:09, Zhenzhong Duan wrote:
Some vIOMMU such as virtio-iommu use IOVA ranges from host side to
setup reserved ranges for passthrough device, so that guest will not
use an IOVA range beyond host support.
Use an uAPI of IOMMUFD to get IOVA ranges of host side and pass to
vIOMMU just
Cc'ing Paolo
On 14/11/23 13:25, Philippe Mathieu-Daudé wrote:
On 13/11/23 20:52, David Woodhouse wrote:
On Mon, 2023-11-13 at 16:21 +0100, Philippe Mathieu-Daudé wrote:
"sysemu/xen.h" defines CONFIG_XEN_IS_POSSIBLE as a target-agnostic
version of CONFIG_XEN. Use it in order to use
On 11/14/23 11:09, Zhenzhong Duan wrote:
Now we support two types of iommu backends, let's add the capability
to select one of them. This depends on whether an iommufd object has
been linked with the vfio-platform device:
If the user wants to use the legacy backend, it shall not
link the
Since commit 04b0de0ee8 ("xen: factor out common functions")
xen_hvm_inject_msi() stub is not required.
Signed-off-by: Philippe Mathieu-Daudé
---
stubs/xen-hw-stub.c | 4
1 file changed, 4 deletions(-)
diff --git a/stubs/xen-hw-stub.c b/stubs/xen-hw-stub.c
index 7d7ffe83a9..6cf0e9a4c1
Xen is a system specific accelerator, it makes no sense
to include its headers in user emulation.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Richard Henderson
Reviewed-by: David Woodhouse
---
include/sysemu/xen.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff
Use a common 'xen_arch_' prefix for architecture-specific functions.
Rename xen_arch_set_memory() and xen_arch_handle_ioreq().
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: David Woodhouse
Reviewed-by: Richard Henderson
---
include/hw/arm/xen_arch_hvm.h | 4 ++--
Per commit f17068c1c7 ("xen-hvm: reorganize xen-hvm and move common
function to xen-hvm-common"), handle_ioreq() is expected to be
target-agnostic. However it uses 'target_ulong', which is a target
specific definition.
Per xen/include/public/hvm/ioreq.h header:
struct ioreq {
uint64_t
Add a tag to run all Xen-specific tests using:
$ make check-avocado AVOCADO_TAGS='guest:xen'
Signed-off-by: Philippe Mathieu-Daudé
---
tests/avocado/boot_xen.py | 3 +++
tests/avocado/kvm_xen_guest.py | 1 +
2 files changed, 4 insertions(+)
diff --git a/tests/avocado/boot_xen.py
Missing review: 4-10,13,16,18-19
Since v1:
- Rework handle_ioreq() patch (Richard)
- Call xen_enabled() and remove various stubs
- Use QEMU_ALIGNED() in xen_blkif header
- Rename ram_memory -> xen_memory
- Have files using Xen API also use its CPPFLAGS
- Add missing license
- Added Avocado tag
-
From: Janosch Frank
PV dumps block vcpu runs until dump end is reached. If there's an
error between PV dump init and PV dump end the vm will never be able
to run again. One example of such an error is insufficient disk space
for the dump file.
Let's add a cleanup function that tries to do a
The following changes since commit f78ea7ddb0e18766ece9fdfe02061744a7afc41b:
Merge tag 'pull-request-2023-11-13' of https://gitlab.com/thuth/qemu into
staging (2023-11-13 07:15:43 -0500)
are available in the Git repository at:
https://gitlab.com/thuth/qemu.git tags/pull-request-2023-11-14
From: Janosch Frank
dump_state_prepare() now sets the function pointers to NULL so we only
need to touch them if we're going to use them.
Signed-off-by: Janosch Frank
Reviewed-by: Marc-André Lureau
Reviewed-by: Thomas Huth
Message-ID: <20231109120443.185979-2-fran...@linux.ibm.com>
From: Janosch Frank
Some architectures (s390x) need to cleanup after a failed dump to be
able to continue to run the vm. Add a cleanup function pointer and
call it if it's set.
Signed-off-by: Janosch Frank
Reviewed-by: Thomas Huth
Reviewed-by: Marc-André Lureau
Message-ID:
Hi
On Tue, Nov 14, 2023 at 4:27 PM BALATON Zoltan wrote:
>
> On Tue, 14 Nov 2023, Marc-André Lureau wrote:
> > Hi
> >
> > On Wed, Nov 8, 2023 at 7:56 PM Kamay Xutax wrote:
> >>
> >> Signed-off-by: Kamay Xutax
> >> ---
> >> include/ui/sdl2.h | 5 ++
> >> meson.build | 1 +
> >>
On Tue, 14 Nov 2023 at 13:05, Thomas Huth wrote:
>
> QOM names currently don't have any enforced naming rules. This
> can be problematic, e.g. when they are used on the command line
> for the "-device" option (where the comma is used to separate
> properties). To avoid that such problematic type
On Tue, 2023-11-14 at 08:58 +0100, Philippe Mathieu-Daudé wrote:
> > > Reviewing quickly hw/block/dataplane/xen-block.c, this code doesn't
> > > seem target specific at all IMHO. Otherwise I'd really expect it to
> > > fail compiling. But I don't know much about Xen, so I'll let block &
> > > xen
On 14/11/2023 15.10, Philippe Mathieu-Daudé wrote:
Hi Thomas,
On 14/11/23 14:43, Thomas Huth wrote:
assertEquals() has been removed in Python 3.12 and should be replaced by
assertEqual(). See: https://docs.python.org/3.12/whatsnew/3.12.html#id3
From this list I see assertEquals() has been
All these stubs are protected by a 'if (xen_enabled())' check.
Signed-off-by: Philippe Mathieu-Daudé
---
stubs/xen-hw-stub.c | 24
1 file changed, 24 deletions(-)
diff --git a/stubs/xen-hw-stub.c b/stubs/xen-hw-stub.c
index 6cf0e9a4c1..53c6a6f2a0 100644
---
assertRegexpMatches() has been removed in Python 3.12 and should be replaced by
assertRegex(). See: https://docs.python.org/3.12/whatsnew/3.12.html#id3
Inspired-by: Thomas Huth
Signed-off-by: Philippe Mathieu-Daudé
---
docs/devel/testing.rst | 2 +-
tests/avocado/version.py | 2 +-
2 files
From: Shiju Jose
CXL spec 3.1 section 8.2.9.9.11.2 describes the DDR5 Error Check Scrub (ECS)
control feature.
The Error Check Scrub (ECS) is a feature defined in JEDEC DDR5 SDRAM
Specification (JESD79-5) and allows the DRAM to internally read, correct
single-bit errors, and write back
From: Shiju Jose
CXL spec 3.0 section 8.2.9.6 describes optional device specific features.
CXL devices supports features with changeable attributes.
Get Supported Features retrieves the list of supported device specific
features. The settings of a feature can be retrieved using Get Feature and
From: Shiju Jose
Add support for the feature commands, device patrol scrub control and
DDR5 ECS control features.
CXL spec 3.0 section 8.2.9.6 describes optional device specific features.
CXL spec 3.1 section 8.2.9.9.11.1 describes the device patrol scrub control
feature.
CXL spec 3.1 section
From: Shiju Jose
CXL spec 3.1 section 8.2.9.9.11.1 describes the device patrol scrub control
feature. The device patrol scrub proactively locates and makes corrections
to errors in regular cycle. The patrol scrub control allows the request to
configure patrol scrub input configurations.
The
On 11/13/23 06:56, Christoph Muellner wrote:
From: Christoph Müllner
The Ssdtso extension introduces a DTSO field to the {m,s,h}envcfg
register to enable TSO at run-time. Building on top of Ztso support,
this patch treates Ssdtso just like Ztso (always execute in TSO mode),
On 11/14/23 11:09, Zhenzhong Duan wrote:
From: Eric Auger
Now we support two types of iommu backends, let's add the capability
to select one of them. This depends on whether an iommufd object has
been linked with the vfio-pci device:
If the user wants to use the legacy backend, it shall not
On 11/14/23 11:09, Zhenzhong Duan wrote:
Some of the callbacks in VFIOIOMMUOps pass VFIOContainerBase poiner,
those callbacks only need read access to the sub object of VFIOContainerBase.
So make VFIOContainerBase, VFIOContainer and VFIOIOMMUFDContainer as const
in these callbacks.
Local
On 11/14/23 11:09, Zhenzhong Duan wrote:
Now we support two types of iommu backends, let's add the capability
to select one of them. This depends on whether an iommufd object has
been linked with the vfio-ccw device:
If the user wants to use the legacy backend, it shall not
link the vfio-ccw
On 11/14/23 11:09, Zhenzhong Duan wrote:
This gives management tools like libvirt a chance to open the vfio
cdev with privilege and pass FD to qemu. This way qemu never needs
to have privilege to open a VFIO or iommu cdev node.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Matthew Rosato
Hi Thomas,
On 14/11/23 14:43, Thomas Huth wrote:
assertEquals() has been removed in Python 3.12 and should be replaced by
assertEqual(). See: https://docs.python.org/3.12/whatsnew/3.12.html#id3
From this list I see assertEquals() has been deprecated in 3.2, along
with assertRegexpMatches().
On 11/14/23 11:09, Zhenzhong Duan wrote:
This gives management tools like libvirt a chance to open the vfio
cdev with privilege and pass FD to qemu. This way qemu never needs
to have privilege to open a VFIO or iommu cdev node.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Cédric Le Goater
Hi Marc-André,
+ Mathieu for vhost RNG stuff.
On Tue, Nov 14, 2023 at 01:54:50PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Mon, Nov 13, 2023 at 11:04 PM Leo Yan wrote:
[...]
> > @@ -2233,6 +2233,7 @@ L: virtio...@redhat.com
> > virtio-input
> > M: Gerd Hoffmann
> > S: Odd Fixes
> > +F:
Commit eaab4d60d3 ("Introduce Xen PCI Passthrough, qdevice")
introduced both xen_pt.[ch], but only added the license to
xen_pt.c. Use the same license for xen_pt.h.
Suggested-by: David Woodhouse
Signed-off-by: Philippe Mathieu-Daudé
---
hw/xen/xen_pt.h | 10 ++
1 file changed, 10
On 14/11/23 15:21, Thomas Huth wrote:
On 14/11/2023 15.10, Philippe Mathieu-Daudé wrote:
Hi Thomas,
On 14/11/23 14:43, Thomas Huth wrote:
assertEquals() has been removed in Python 3.12 and should be replaced by
assertEqual(). See: https://docs.python.org/3.12/whatsnew/3.12.html#id3
From
"hw/xen/xen_pt.h" requires "hw/xen/xen_native.h" which is target
specific. It also declares IGD methods, which are not target
specific.
Target-agnostic code can use IGD methods. To allow that, extract
these methos into a new "hw/xen/xen_igd.h" header.
Signed-off-by: Philippe Mathieu-Daudé
We rarely need to include "cpu.h" in headers. Including it
'taint' headers to be target-specific. Here only the i386/arm
implementations requires "cpu.h", so include it there and
remove from the "hw/xen/xen-hvm-common.h" *common* header.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Richard
(adding maintainers in the CC)
On 11/14/23 06:44, Clément Chigot wrote:
The extensions zicntr and zihpm were officially added in the privilege
instruction set specification 1.12. However, QEMU has been implemented
them long before it and thus they are forced to be on during the cpu
Hi
On Wed, Nov 8, 2023 at 7:56 PM Kamay Xutax wrote:
>
> Signed-off-by: Kamay Xutax
> ---
> include/ui/sdl2.h | 5 ++
> meson.build | 1 +
> ui/meson.build | 1 +
> ui/sdl2-clipboard.c | 147
> ui/sdl2.c | 8 +++
> 5
On 11/14/23 11:09, Zhenzhong Duan wrote:
From: Eric Auger
Introduce an iommufd object which allows the interaction
with the host /dev/iommu device.
The /dev/iommu can have been already pre-opened outside of qemu,
in which case the fd can be passed directly along with the
iommufd object:
This
Il dom 12 nov 2023, 13:06 Stefan Hajnoczi ha scritto:
> On Sat, 11 Nov 2023 at 23:30, Paolo Bonzini wrote:
> >
> > The following changes since commit
> ad6ef0a42e314a8c6ac6c96d5f6e607a1e5644b5:
> >
> > Merge tag 'for-upstream' of https://repo.or.cz/qemu/kevin into
> staging (2023-11-09
On 11/14/23 11:09, Zhenzhong Duan wrote:
This gives management tools like libvirt a chance to open the vfio
cdev with privilege and pass FD to qemu. This way qemu never needs
to have privilege to open a VFIO or iommu cdev node.
Together with the earlier support of pre-opening /dev/iommu device,
"sysemu/xen.h" defines CONFIG_XEN_IS_POSSIBLE as a target-agnostic
version of CONFIG_XEN accelerator.
Use it in order to use "sysemu/xen-mapcache.h" in target-agnostic files.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: David Woodhouse
---
include/sysemu/xen-mapcache.h | 3 ++-
1 file
Similarly to the restriction in hw/pci/msix.c (see commit
e1e4bf2252 "msix: fix msix_vector_masked"), restrict the
xen_is_pirq_msi() call in msi_is_masked() to Xen.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/pci/msi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
physmem.c doesn't use any declaration from "hw/xen/xen.h",
it only requires "sysemu/xen.h" and "system/xen-mapcache.h".
Suggested-by: David Woodhouse
Signed-off-by: Philippe Mathieu-Daudé
---
system/physmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/system/physmem.c
To avoid a potential global variable shadow in
hw/i386/pc_piix.c::pc_init1(), rename Xen's
"ram_memory" as "xen_memory".
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/xen/xen-hvm-common.h | 2 +-
hw/arm/xen_arm.c| 6 +++---
hw/i386/xen/xen-hvm.c | 10
Except imported source files, QEMU code base uses
the QEMU_ALIGNED() macro to align its structures.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/block/xen_blkif.h | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/hw/block/xen_blkif.h b/hw/block/xen_blkif.h
index
Only call xen_register_framebuffer() when Xen is enabled.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/display/vga.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/hw/display/vga.c b/hw/display/vga.c
index 37557c3442..f9cf3d6f77 100644
--- a/hw/display/vga.c
+++
Instead of the target-specific TARGET_PAGE_BITS definition,
use qemu_target_page_bits() which is target agnostic.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Richard Henderson
Reviewed-by: David Woodhouse
---
hw/xen/xen-hvm-common.c | 6 --
1 file changed, 4 insertions(+), 2
-Original Message-
From: Nabih Estefan
Sent: Saturday, October 28, 2023 1:55 AM
To: peter.mayd...@linaro.org
Cc: qemu-...@nongnu.org; qemu-devel@nongnu.org; CS20 KFTing
; wuhao...@google.com; jasonw...@redhat.com; IS20 Avi
Fishman ; nabiheste...@google.com; CS20 KWLiu
; IS20 Tomer
Hi
On Tue, Nov 14, 2023 at 6:10 AM Joelle van Dyne wrote:
>
> The impetus for this patch set is to get TPM 2.0 working on Windows 11 ARM64.
> Windows' tpm.sys does not seem to work on a TPM TIS device (as verified with
> VMWare's implementation). However, the current TPM CRB device uses a fixed
The only tool we have for configuring the schema is the 'if'
conditional. 'if': 'CONFIG_IOMMUFD' compiles to #if
defined(CONFIG_IOMMUFD) ... #endif. Your use of #ifdef CONFIG_IOMMUFD
above suggests this is fine here.
Symbols that are only defined in target-dependent compiles (see
Support specification Version 1.0.0-draft4 rapid-k model.
Signed-off-by: Ethan Chen
---
hw/misc/Kconfig | 4 +
hw/misc/meson.build | 1 +
hw/misc/riscv_iopmp.c | 967 ++
Signed-off-by: Ethan Chen
---
hw/dma/Kconfig | 4 +
hw/dma/atcdmac300.c | 566
hw/dma/meson.build | 1 +
include/hw/dma/atcdmac300.h | 180
4 files changed, 751 insertions(+)
create mode 100644
Make other device can use /hw/core/stream.c by select this config.
Signed-off-by: Ethan Chen
---
hw/core/Kconfig | 3 +++
hw/core/meson.build | 1 +
2 files changed, 4 insertions(+)
diff --git a/hw/core/Kconfig b/hw/core/Kconfig
index 9397503656..628dc3d883 100644
--- a/hw/core/Kconfig
+++
- Add 'iopmp=on' option to enable a iopmp device and a dma device
connect to the iopmp device
- Add 'iopmp_cascade=on' option to enable iopmp cascading.
Signed-off-by: Ethan Chen
---
hw/riscv/Kconfig| 2 ++
hw/riscv/virt.c | 72 +++--
This series implements IOPMP specification v1.0.0-draft4 rapid-k model.
When IOPMP is enabled, a DMA device ATCDMAC300 is added to RISC-V virt
platform. This DMA devce is connected to the IOPMP and has the functionalities
required by IOPMP, including:
- Support specify source-id (SID)
- Support
Markus Armbruster wrote:
D> Cc: Paolo for QOM expertise.
>
> Peter Xu writes:
>
>> On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote:
>
> [...]
>
>>> Migration has its own idiosyncratic configuration interface, even though
>>> its configuration needs are not special at all. This
On Tue, Nov 14, 2023 at 11:28:28AM +0100, Juan Quintela wrote:
> Daniel P. Berrangé wrote:
> > On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote:
> >> Now let's try to apply this to migration.
> >>
> >> As long as we can have just one migration, we need just one QAPI object
> >>
Daniel P. Berrangé wrote:
> On Tue, Nov 14, 2023 at 11:28:28AM +0100, Juan Quintela wrote:
>> Daniel P. Berrangé wrote:
>> > On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote:
>> >> Now let's try to apply this to migration.
>> >>
>> >> As long as we can have just one migration,
Mikhail Tyutin writes:
>> > What is the right way to get virtual address of either translation block
>> > or instruction inside of TCG plugin? Does
>> > plugin API allow that or it needs some extension?
>> >
>> > So far I use qemu_plugin_tb_vaddr() inside of my block translation
>> > callback
On 14/11/2023 08.41, Markus Armbruster wrote:
Cc: the other QOM maintainers
Daniel P. Berrangé writes:
On Mon, Nov 13, 2023 at 02:43:42PM +0100, Markus Armbruster wrote:
We got rid of QOM type names containing ',' in 6.0, but some have
crept back in. Replace them just like we did in 6.0.
> > What is the right way to get virtual address of either translation block or
> > instruction inside of TCG plugin? Does
> > plugin API allow that or it needs some extension?
> >
> > So far I use qemu_plugin_tb_vaddr() inside of my block translation callback
> > to get block virtual address
On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote:
> Now let's try to apply this to migration.
>
> As long as we can have just one migration, we need just one QAPI object
> to configure it.
>
> We could create the object with -object / object_add. For convenience,
> we'd probably
The extensions zicntr and zihpm were officially added in the privilege
instruction set specification 1.12. However, QEMU has been implemented
them long before it and thus they are forced to be on during the cpu
initialization to ensure compatibility (see riscv_cpu_init).
On Mon, Nov 13, 2023 at 11:04 PM Leo Yan wrote:
>
> The Virtio input device invokes set_config() callback for retrieving
> the event configuration info, but the callback is not supported in
> vhost-user-base.
>
> This patch adds support set_config() callback in vhost-user-base.
>
> Signed-off-by:
Thomas Huth writes:
> On 14/11/2023 08.41, Markus Armbruster wrote:
>> Cc: the other QOM maintainers
>> Daniel P. Berrangé writes:
>>
>>> On Mon, Nov 13, 2023 at 02:43:42PM +0100, Markus Armbruster wrote:
We got rid of QOM type names containing ',' in 6.0, but some have
crept back
Daniel P. Berrangé writes:
> On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote:
>> Now let's try to apply this to migration.
>>
>> As long as we can have just one migration, we need just one QAPI object
>> to configure it.
>>
>> We could create the object with -object /
This gives management tools like libvirt a chance to open the vfio
cdev with privilege and pass FD to qemu. This way qemu never needs
to have privilege to open a VFIO or iommu cdev node.
Together with the earlier support of pre-opening /dev/iommu device,
now we have full support of passing a vfio
From: Cédric Le Goater
Signed-off-by: Cédric Le Goater
Signed-off-by: Zhenzhong Duan
---
hw/i386/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/i386/Kconfig b/hw/i386/Kconfig
index 55850791df..a1846be6f7 100644
--- a/hw/i386/Kconfig
+++ b/hw/i386/Kconfig
@@ -95,6 +95,7 @@
This gives management tools like libvirt a chance to open the vfio
cdev with privilege and pass FD to qemu. This way qemu never needs
to have privilege to open a VFIO or iommu cdev node.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Matthew Rosato
---
hw/vfio/ccw.c | 25 ++---
This helper will be used by both legacy and iommufd backends.
No functional changes intended.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Cédric Le Goater
Signed-off-by: Cédric Le Goater
---
hw/vfio/pci.h | 3 +++
hw/vfio/pci.c | 54 +++
2
Some of the callbacks in VFIOIOMMUOps pass VFIOContainerBase poiner,
those callbacks only need read access to the sub object of VFIOContainerBase.
So make VFIOContainerBase, VFIOContainer and VFIOIOMMUFDContainer as const
in these callbacks.
Local functions called by those callbacks also need
From: Eric Auger
Now we support two types of iommu backends, let's add the capability
to select one of them. This depends on whether an iommufd object has
been linked with the vfio-pci device:
If the user wants to use the legacy backend, it shall not
link the vfio-pci device with any iommufd
This gives management tools like libvirt a chance to open the vfio
cdev with privilege and pass FD to qemu. This way qemu never needs
to have privilege to open a VFIO or iommu cdev node.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Matthew Rosato
---
hw/vfio/ap.c | 23 ++-
1
Add a new callback iommufd_cdev_pci_hot_reset to do iommufd specific
check and reset operation.
Signed-off-by: Zhenzhong Duan
---
v6: pci_hot_reset return -errno if fails
hw/vfio/iommufd.c| 145 +++
hw/vfio/trace-events | 1 +
2 files changed, 146
Now we support two types of iommu backends, let's add the capability
to select one of them. This depends on whether an iommufd object has
been linked with the vfio-platform device:
If the user wants to use the legacy backend, it shall not
link the vfio-platform device with any iommufd object:
From: Cédric Le Goater
Signed-off-by: Cédric Le Goater
Signed-off-by: Zhenzhong Duan
Reviewed-by: Matthew Rosato
---
hw/s390x/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/s390x/Kconfig b/hw/s390x/Kconfig
index 4c068d7960..26ad104485 100644
--- a/hw/s390x/Kconfig
+++
I noticed that Neoverse-V1 has FEAT_RNG enabled so let enable it also on
Neoverse-N2.
Signed-off-by: Marcin Juszkiewicz
---
target/arm/tcg/cpu64.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/arm/tcg/cpu64.c b/target/arm/tcg/cpu64.c
index 08db1dbcc7..fcda99e158
1 - 100 of 409 matches
Mail list logo
