... To early in the morning ...
It is on GitHub...
on Github:
https://github.com/intel/haxm/releases/tag/v7.5.6
others:
https://www.softpedia.com/get/Programming/Other-Programming-Files/Intel-Hardware-Accelerated-Execution-Manager.shtml
Hi Jerry,
have you read the instructtions on Intel:
https://github.com/intel/haxm/wiki/Installation-Instructions-on-Windows
May be this helps you
Best regards
Holger
Am 20.03.20 um 21:22 schrieb Jerry Geis:
So I tried --enable-whpx and I get Invalid option. Im on Windows 10
and QEMU 4.2.0
Loongson multimedia condition instructions were previously implemented as
write 0 to rd due to lack of documentation. So I just confirmed with Loongson
about their encoding and implemented them correctly.
Signed-off-by: Jiaxun Yang
---
target/mips/translate.c | 40
Add support for MinMem SPLPAR Characteristic on emulated
RTAS call ibm,get-system-parameter.
MinMem represents Minimum Memory, that is described in LOPAPR as:
The minimum amount of main store that is needed to power on the
partition. Minimum memory is expressed in MB of storage.
This provides a
On Fri, Mar 20, 2020 at 2:17 AM Alex Bennée wrote:
>
> Lirong Yuan writes:
>
> > On Fri, Mar 6, 2020 at 5:01 PM Lirong Yuan wrote:
> >
> >> This allows gdb to access the target’s auxiliary vector,
> >> which can be helpful for telling system libraries important details
> >> about the hardware,
Making use of ppc's Protected Execution Facility (PEF) feature, a
guest can become a secure guest (aka. secure VM - SVM) and have its
memory protected from access by the host. This feature is mediated by
a piece of firmware called the Ultravisor (UV).
The transition from a regular to a secure VM
On Wed, Mar 18, 2020 at 9:03 PM Leonardo Bras wrote:
>
> When dumping dtb to a file, qemu exits silently before starting the VM.
>
> Add info message so user can easily track why the proccess exits.
> Add error message if dtb dump failed.
>
> Signed-off-by: Leonardo Bras
Thanks for the patch
-20200320-1
for you to fetch changes up to 9f252c7c88eacbf21dadcfe117b0d08f2e88ceeb:
device_tree: Add info message when dumping dtb to file (2020-03-20 14:55:44
-0700)
DTC patches for 5.0
From: Leonardo Bras
When dumping dtb to a file, qemu exits silently before starting the VM.
Add info message so user can easily track why the proccess exits.
Add error message if dtb dump failed.
Signed-off-by: Leonardo Bras
Message-Id: <20200319040326.391090-1-leona...@linux.ibm.com>
This patch introduces support for PMR that has been defined as part of NVMe 1.4
spec. User can now specify a pmrdev option that should point to
HostMemoryBackend.
pmrdev memory region will subsequently be exposed as PCI BAR 2 in emulated NVMe
device. Guest OS can perform mmio read and writes to
On Thu, 2020-03-19 at 09:19 -0400, Janosch Frank wrote:
> The unpack facility provides the means to setup a protected guest. A
> protected guest cannot be introspected by the hypervisor or any
> user/administrator of the machine it is running on.
>
> Protected guests are encrypted at rest and
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On Mon, 17 Jul 2017 at 10:40, Gerd Hoffmann wrote:
> >
> > From: "Dr. David Alan Gilbert"
> >
> > The QMP query-vnc interfaces have gained a lot more information that
> > the HMP interfaces hasn't got yet. Update it.
> >
> > Note the output
So I tried --enable-whpx and I get Invalid option. Im on Windows 10 and
QEMU 4.2.0
I'm confused. Then I don't know where to download the HAXM. The place I
found is GIT and it wants the user to compile it. I was looking for just an
EXE.
Thanks
Jerry
On Thu, 19 Mar 2020 02:24:33 -0400
Yan Zhao wrote:
> On Thu, Mar 19, 2020 at 03:41:14AM +0800, Kirti Wankhede wrote:
> > diff --git a/drivers/vfio/vfio_iommu_type1.c
> > b/drivers/vfio/vfio_iommu_type1.c
> > index 912629320719..deec09f4b0f6 100644
> > --- a/drivers/vfio/vfio_iommu_type1.c
> >
On Fri 20 Mar 2020 08:35:44 PM CET, Eric Blake wrote:
>> This flag is however only supported when qcow_version >= 3. In older
>> images the cluster is simply deallocated, exposing any possible
>> previous data from the backing file.
>
> Discard is advisory, and has no requirements that discarded
On 3/20/20 1:58 PM, Alberto Garcia wrote:
Hi,
when full_discard is false in discard_in_l2_slice() then the selected
cluster should be deallocated and it should read back as zeroes. This
is done by clearing the cluster offset field and setting OFLAG_ZERO in
the L2 entry.
This flag is however
On Sat, 21 Mar 2020 00:44:32 +0530
Kirti Wankhede wrote:
> On 3/20/2020 9:17 PM, Alex Williamson wrote:
> > On Fri, 20 Mar 2020 09:40:39 -0600
> > Alex Williamson wrote:
> >
> >> On Fri, 20 Mar 2020 04:35:29 -0400
> >> Yan Zhao wrote:
> >>
> >>> On Thu, Mar 19, 2020 at 03:41:12AM +0800,
On Fri, Mar 20, 2020 at 5:48 PM Andrzej Jakowski
wrote:
>
> On 3/20/20 8:45 AM, Stefan Hajnoczi wrote:
> > Please use qemu_ram_writeback() so that pmem_persist() and qemu_msync()
> > are used as appropriate.
>
> Thx!
> qemu_ram_writeback() doesn't return any status. How can I know that actual
>
Am 20.03.20 um 18:20 schrieb Jerry Geis:
> Hi All,
>
> I have tried QEMU on Windows 10 host with and without HyperV active in
> the features list.
> Neither seemed to affect the "really slow" speed. Either option
> results in -enable-kvm giving "no acceleration found".
>
> How do I enable
On 3/20/2020 9:17 PM, Alex Williamson wrote:
On Fri, 20 Mar 2020 09:40:39 -0600
Alex Williamson wrote:
On Fri, 20 Mar 2020 04:35:29 -0400
Yan Zhao wrote:
On Thu, Mar 19, 2020 at 03:41:12AM +0800, Kirti Wankhede wrote:
DMA mapped pages, including those pinned by mdev vendor drivers,
The Python2 PyYAML is now pointless, switch to the Python3 version.
Fixes: bcbf27947 (docker: move tests from python2 to python3)
Signed-off-by: Philippe Mathieu-Daudé
---
tests/docker/dockerfiles/fedora.docker | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Install optional dependencies of QEMU to get better coverage.
Suggested-by: Peter Maydell
Signed-off-by: Philippe Mathieu-Daudé
---
tests/docker/dockerfiles/fedora.docker | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/docker/dockerfiles/fedora.docker
Easy fixes for our Docker images.
Philippe Mathieu-Daudé (4):
tests/docker: Keep package list sorted
tests/docker: Install gcrypt devel package in Debian image
tests/docker: Use Python3 PyYAML in the Fedora image
tests/docker: Add libepoxy and libudev packages to the Fedora image
Apparently Debian Stretch was listing gcrypt as a QEMU dependency,
but this is not the case anymore in Buster, so we need to install
it manually (it it not listed by 'apt-get -s build-dep qemu' in
the common debian10.docker anymore).
$ ../configure $QEMU_CONFIGURE_OPTS
ERROR: User requested
Keep package list sorted, this eases rebase/cherry-pick.
Fixes: 3a6784813
Signed-off-by: Philippe Mathieu-Daudé
---
tests/docker/dockerfiles/centos7.docker | 6 --
tests/docker/dockerfiles/fedora.docker | 6 --
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git
On Sat, 21 Mar 2020 00:12:04 +0530
Kirti Wankhede wrote:
> On 3/20/2020 11:31 PM, Alex Williamson wrote:
> > On Fri, 20 Mar 2020 23:19:14 +0530
> > Kirti Wankhede wrote:
> >
> >> On 3/20/2020 4:27 AM, Alex Williamson wrote:
> >>> On Fri, 20 Mar 2020 01:46:41 +0530
> >>> Kirti Wankhede
Hi,
when full_discard is false in discard_in_l2_slice() then the selected
cluster should be deallocated and it should read back as zeroes. This
is done by clearing the cluster offset field and setting OFLAG_ZERO in
the L2 entry.
This flag is however only supported when qcow_version >= 3. In
On Tue, Mar 17, 2020 at 8:45 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 33 +++
> target/riscv/insn32.decode | 8 +++
>
On Tue, Mar 17, 2020 at 8:41 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 33
> target/riscv/insn32.decode | 8 +++
>
On Tue, Mar 17, 2020 at 8:37 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 13
> target/riscv/insn32.decode | 6 ++
>
On Thu, 19 Mar 2020 18:31:11 +0100
David Hildenbrand wrote:
> [...]
>
> >>
> >> I asked this question already to Michael (cc) via a different
> >> channel, but hare is it again:
> >>
> >> Why does the balloon driver not support VIRTIO_F_IOMMU_PLATFORM? It
> >> is absolutely not clear to me. The
On Tue, Mar 17, 2020 at 8:33 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 25
> target/riscv/insn32.decode | 9 +
>
On 3/20/2020 11:31 PM, Alex Williamson wrote:
On Fri, 20 Mar 2020 23:19:14 +0530
Kirti Wankhede wrote:
On 3/20/2020 4:27 AM, Alex Williamson wrote:
On Fri, 20 Mar 2020 01:46:41 +0530
Kirti Wankhede wrote:
+static int vfio_iova_dirty_bitmap(struct vfio_iommu *iommu, dma_addr_t
On Tue, Mar 17, 2020 at 8:27 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 21 ++
> target/riscv/insn32.decode | 10 +
> target/riscv/insn_trans/trans_rvv.inc.c | 251
If we fail to get bitmap info, we must not leak the encryption info.
Fixes: b8968c875f403
Fixes: Coverity CID 1421894
Signed-off-by: Eric Blake
---
block/qcow2.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block/qcow2.c b/block/qcow2.c
index d44b45633dbb..e08917ed8462 100644
---
On 3/20/20 12:57 PM, Peter Maydell wrote:
On Mon, 11 Feb 2019 at 20:57, Eric Blake wrote:
From: Andrey Shinkevich
In the 'Format specific information' section of the 'qemu-img info'
command output, the supplemental information about existing QCOW2
bitmaps will be shown, such as a bitmap
Patchew URL:
https://patchew.org/QEMU/20200320155106.549514-1-marcandre.lur...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [PULL v2 0/1] Slirp patches
Message-id: 20200320155106.549514-1-marcandre.lur...@redhat.com
* Daniel P. Berrangé (berra...@redhat.com) wrote:
> On Fri, Mar 20, 2020 at 05:31:17PM +, Dr. David Alan Gilbert wrote:
> > (Rearranging the text a bit)
> >
> > * Markus Armbruster (arm...@redhat.com) wrote:
> >
> > > David (cc'ed) should be able to tell us which fix is right.
> > >
> > >
The QEMU 9pfs 'multidevs' option exists since QEMU 4.2, so just
set this capability based on that QEMU version.
Signed-off-by: Christian Schoenebeck
---
src/qemu/qemu_capabilities.c | 5 +
src/qemu/qemu_capabilities.h | 1 +
On Fri, 20 Mar 2020 23:19:14 +0530
Kirti Wankhede wrote:
> On 3/20/2020 4:27 AM, Alex Williamson wrote:
> > On Fri, 20 Mar 2020 01:46:41 +0530
> > Kirti Wankhede wrote:
> >
> >> VFIO_IOMMU_DIRTY_PAGES ioctl performs three operations:
> >> - Start dirty pages tracking while migration is
This option prevents misbehaviours on guest if a qemu 9pfs export
contains multiple devices, due to the potential file ID collisions
this otherwise may cause.
Signed-off-by: Christian Schoenebeck
---
src/qemu/qemu_command.c | 7 +++
src/qemu/qemu_domain.c | 12
2 files
Signed-off-by: Christian Schoenebeck
---
docs/formatdomain.html.in | 7 +++
1 file changed, 7 insertions(+)
diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
index 594146009d..cc2c671c14 100644
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -4084,13
QEMU 4.2 added a new option 'multidevs' for 9pfs. The following patch adds
support for this new option to libvirt.
In short, what is this about: to distinguish files uniquely from each other
in general, numeric file IDs are typically used for comparison, which in
practice is the combination of a
Introduce new 'multidevs' option for filesystem.
This option prevents misbehaviours on guest if a qemu 9pfs export
contains multiple devices, due to the potential file ID collisions
this otherwise may cause.
Signed-off-by: Christian Schoenebeck
---
docs/formatdomain.html.in
On 3/20/20 8:45 AM, Stefan Hajnoczi wrote:
> Please use qemu_ram_writeback() so that pmem_persist() and qemu_msync()
> are used as appropriate.
Thx!
qemu_ram_writeback() doesn't return any status. How can I know that actual
msync succeds?
Also qemu_ram_writeback() requires me to include
On Mon, 11 Feb 2019 at 20:57, Eric Blake wrote:
>
> From: Andrey Shinkevich
>
> In the 'Format specific information' section of the 'qemu-img info'
> command output, the supplemental information about existing QCOW2
> bitmaps will be shown, such as a bitmap name, flags and granularity:
Hi;
On 3/20/2020 4:27 AM, Alex Williamson wrote:
On Fri, 20 Mar 2020 01:46:41 +0530
Kirti Wankhede wrote:
VFIO_IOMMU_DIRTY_PAGES ioctl performs three operations:
- Start dirty pages tracking while migration is active
- Stop dirty pages tracking.
- Get dirty pages bitmap. Its user space
On Fri, Mar 20, 2020 at 05:31:17PM +, Dr. David Alan Gilbert wrote:
> (Rearranging the text a bit)
>
> * Markus Armbruster (arm...@redhat.com) wrote:
>
> > David (cc'ed) should be able to tell us which fix is right.
> >
> > @tls_creds and @tls_hostname look like they could have the same
On 19/03/20 20:33, Peter Maydell wrote:
> +# TODO: how do you get 'docker build' to print the output of the
> +# commands it is running to its stdout? This would be useful for debug.
> +DOCKER_BUILDKIT=1 docker build -t coverity-scanner \
> + --secret
On Mon, 3 Feb 2020 at 06:11, David Gibson wrote:
>
> From: Greg Kurz
>
> Most of the option vector helpers have assertions to check their
> arguments aren't null. The guest can provide an arbitrary address
> for the CAS structure that would result in such null arguments.
> Fail CAS with
(Rearranging the text a bit)
* Markus Armbruster (arm...@redhat.com) wrote:
> David (cc'ed) should be able to tell us which fix is right.
>
> @tls_creds and @tls_hostname look like they could have the same issue.
A certain Markus removed the Null checks in 8cc99dc because 4af245d
guaranteed
On Fri, Mar 20, 2020 at 4:20 PM Stefan Hajnoczi wrote:
>
> On Wed, Mar 18, 2020 at 02:48:49PM +0100, Julia Suvorova wrote:
> > ring->name is defined as 'char name[MAX_RING_NAME_SZ]'. Replace untruncated
> > strncpy with QEMU function.
> > This case prevented QEMU from compiling with
On 3/16/20 12:20 PM, Peter Maydell wrote:
Update the copyright date to 2020 for the copyright strings which are
user-facing and represent overall copyright info for all of QEMU.
Reported-by: John Arbuckle
Signed-off-by: Peter Maydell
---
include/qemu-common.h | 2 +-
docs/conf.py
On Fri, 20 Mar 2020 15:31:01 +0100
Halil Pasic wrote:
> In update_machine_ipl_properties() the array ascii_loadparm needs to
> hold the 8 char lodparm and a string terminating zero char.
s/lodparm/loadparm/
> Let's increase the size of ascii_loadparm accordingly.
>
> Signed-off-by: Halil
Aleksandar Markovic writes:
> пет, 20. мар 2020. у 12:45 Alex Bennée је написао/ла:
>>
>> While debugging check-acceptance failures I found an instability in
>> the mips64el test case. Briefly the test case:
>>
>> retry.py -n 100 -c -- ./mips64el-softmmu/qemu-system-mips64el \
>>
Hi All,
I have tried QEMU on Windows 10 host with and without HyperV active in the
features list.
Neither seemed to affect the "really slow" speed. Either option results in
-enable-kvm giving "no acceleration found".
How do I enable acceleration on QEMU for windows.
Jerry
On 3/19/20 12:33 PM, Peter Maydell wrote:
> The target_flat.h file is a QEMU header, so we should include it using
> quotes, not angle brackets.
>
> Coverity otherwise is unable to find the header:
>
> "../linux-user/flatload.c", line 40: error #1712: cannot open source file
>
On 3/19/20 12:33 PM, Peter Maydell wrote:
> For Coverity's benefit, we provide simpler versions of functions like
> qemu_mutex_lock(), qemu_cond_wait() and qemu_cond_timedwait(). When
> we added qemu_cond_timedwait() in commit 3dcc9c6ec4ea, a cut and
> paste error meant that the Coverity version
On 3/19/20 12:33 PM, Peter Maydell wrote:
> All the Coverity-specific definitions of qemu_mutex_lock() and friends
> have a trailing semicolon. This works fine almost everywhere because
> of QEMU's mandatory-braces coding style and because most callsites are
> simple, but target/s390x/sigp.c has a
On 3/19/20 12:33 PM, Peter Maydell wrote:
> In commit a1a98357e3fd in 2018 we added some workarounds for Coverity
> not being able to handle the _Float* types introduced by recent
> glibc. Newer versions of the Coverity scan tools have support for
> these types, and will fail with errors about
пет, 20. мар 2020. у 12:45 Alex Bennée је написао/ла:
>
> While debugging check-acceptance failures I found an instability in
> the mips64el test case. Briefly the test case:
>
> retry.py -n 100 -c -- ./mips64el-softmmu/qemu-system-mips64el \
> -display none -vga none -serial mon:stdio \
>
пет, 20. мар 2020. у 18:08 Aleksandar Markovic <
aleksandar.qemu.de...@gmail.com> је написао/ла:
>
> пет, 20. мар 2020. у 12:45 Alex Bennée је
написао/ла:
> >
> > While debugging check-acceptance failures I found an instability in
> > the mips64el test case. Briefly the test case:
> >
> >
We now have all bricks to support nested paging. This
uses MAP notifiers to map the MSIs. So let's allow MAP
notifiers to be registered.
Signed-off-by: Eric Auger
---
hw/arm/smmuv3.c | 8
1 file changed, 8 deletions(-)
diff --git a/hw/arm/smmuv3.c b/hw/arm/smmuv3.c
index
We convert iommu_fault structs received from the kernel
into the data struct used by the emulation code and record
the evnts into the virtual event queue.
Signed-off-by: Eric Auger
---
v3 -> v4:
- fix compil issue on mingw
Exhaustive mapping remains to be done
---
hw/arm/smmuv3.c | 71
In case PASID PciOps are set for the device we call
the set_pasid_table() callback on each STE update.
This allows to pass the guest stage 1 configuration
to the host and apply it at physical level.
Signed-off-by: Eric Auger
---
v4 -> v5:
- Use PciOps instead of config notifiers
v3 -> v4:
-
Let's propagate the leaf attribute throughout the invalidation path.
This hint is used to reduce the scope of the invalidations to the
last level of translation. Not enforcing it induces large performance
penalties in nested mode.
Signed-off-by: Eric Auger
---
hw/arm/smmuv3.c | 16
For VFIO integration we will need to pass the Context Descriptor (CD)
table GPA to the host. The CD table is also referred to as the PASID
table. Its GPA corresponds to the s1ctrptr field of the Stream Table
Entry. So let's decode and store it in the configuration structure.
Signed-off-by: Eric
The SMMUv3 has the peculiarity to translate MSI
transactionss. let's advertise the corresponding
attribute.
Signed-off-by: Eric Auger
---
---
hw/arm/smmuv3.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hw/arm/smmuv3.c b/hw/arm/smmuv3.c
index e33eabd028..9bea5f65ae 100644
---
On 3/19/20 4:34 PM, dnbrd...@gmail.com wrote:
> From: Daniel Brodsky
>
> - __COUNTER__ doesn't work with ## concat
> - replaced ## with glue() macro so __COUNTER__ is evaluated
>
> Fixes: 3284c3ddc4
>
> Signed-off-by: Daniel Brodsky
> ---
> include/qemu/lockable.h | 2 +-
>
Set up the fault region which is composed of the actual fault
queue (mmappable) and a header used to handle it. The fault
queue is mmapped.
Signed-off-by: Eric Auger
---
v4 -> v5:
- use a single DMA FAULT region. No version selection anymore
---
hw/vfio/pci.c | 64
When the guest invalidates one S1 entry, it passes the asid.
When propagating this invalidation downto the host, the asid
information also must be passed. So let's fill the arch_id field
introduced for that purpose.
Signed-off-by: Eric Auger
---
hw/arm/smmuv3.c | 1 +
1 file changed, 1
Let's introduce two helpers that allow to DMA map/unmap a RAM
section. Those helpers will be called for nested stage setup in
another call site. Also the vfio_listener_region_add/del()
structure may be clearer.
Signed-off-by: Eric Auger
---
v5 -> v6:
- add Error **
---
hw/vfio/common.c |
We register the stage1 MSI bindings when enabling the vectors
and we unregister them on container disconnection.
Signed-off-by: Eric Auger
---
v4 -> v5:
- use VFIO_IOMMU_SET_MSI_BINDING
v2 -> v3:
- only register the notifier if the IOMMU translates MSIs
- record the msi bindings in a
As done for vfio regions, add helpers to retrieve irq info
including their optional capabilities.
Signed-off-by: Eric Auger
---
hw/vfio/common.c | 97 +++
hw/vfio/trace-events | 1 +
include/hw/vfio/vfio-common.h | 7 +++
3 files changed,
Whenever the eventfd is triggered, we retrieve the DMA fault(s)
from the mmapped fault region and inject them in the iommu
memory region.
Signed-off-by: Eric Auger
---
hw/vfio/pci.c | 50 ++
hw/vfio/pci.h | 1 +
2 files changed, 51 insertions(+)
Let's introduce a hostwin_from_range() helper that returns the
hostwin encapsulating an IOVA range or NULL if none is found.
This improves the readibility of callers and removes the usage
of hostwin_found.
Signed-off-by: Eric Auger
---
hw/vfio/common.c | 36 +---
In nested mode, legacy vfio_iommu_map_notify cannot be used as
there is no "caching" mode and we do not trap on map.
On Intel, vfio_iommu_map_notify was used to DMA map the RAM
through the host single stage.
With nested mode, we need to setup the stage 2 and the stage 1
separately. This patch
From: Liu Yi L
This patch introduces PCIPASIDOps for IOMMU related operations.
https://lists.gnu.org/archive/html/qemu-devel/2018-03/msg00078.html
https://lists.gnu.org/archive/html/qemu-devel/2018-03/msg00940.html
So far, to setup virt-SVA for assigned SVA capable device, needs to
configure
We use the new extended IRQ VFIO_IRQ_TYPE_NESTED type and
VFIO_IRQ_SUBTYPE_DMA_FAULT subtype to set/unset
a notifier for physical DMA faults. The associated eventfd is
triggered, in nested mode, whenever a fault is detected at IOMMU
physical level.
The actual handler will be implemented in
This header is meant to exposes data types used by
several IOMMU devices such as struct for SVA and
nested stage configuration.
Signed-off-by: Eric Auger
---
include/hw/iommu/iommu.h | 28
1 file changed, 28 insertions(+)
create mode 100644 include/hw/iommu/iommu.h
In case we detect the address space is translated by
a virtual IOMMU which requires HW nested paging to
integrate with VFIO, let's set up the container with
the VFIO_TYPE1_NESTING_IOMMU iommu_type.
Signed-off-by: Eric Auger
---
v4 -> v5:
- fail immediatly if nested is wanted but not supported
We introduce a new IOMMU Memory Region attribute,
IOMMU_ATTR_VFIO_NESTED that tells whether the virtual IOMMU
requires HW nested paging for VFIO integration.
Current Intel virtual IOMMU device supports "Caching
Mode" and does not require 2 stages at physical level to be
integrated with VFIO.
This new API allows to inject @count iommu_faults into
the IOMMU memory region.
Signed-off-by: Eric Auger
---
include/exec/memory.h | 25 +
memory.c | 10 ++
2 files changed, 35 insertions(+)
diff --git a/include/exec/memory.h
We introduce a new IOMMU Memory Region attribute, IOMMU_ATTR_MSI_TRANSLATE
which tells whether the virtual IOMMU translates MSIs. ARM SMMU
will expose this attribute since, as opposed to Intel DMAR, MSIs
are translated as any other DMA requests.
Signed-off-by: Eric Auger
---
TLB entries are usually tagged with some ids such as the asid
or pasid. When propagating an invalidation command from the
guest to the host, we need to pass this id.
Also we add a leaf field which indicates, in case of invalidation
notification, whether only cache entries for the last level of
Update the script to import the new iommu.h uapi header.
Signed-off-by: Eric Auger
---
scripts/update-linux-headers.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/update-linux-headers.sh b/scripts/update-linux-headers.sh
index 29c27f4681..5b64ee3912 100755
---
This is an update against
https://github.com/eauger/linux/tree/will-arm-smmu-updates-2stage-v10
Signed-off-by: Eric Auger
---
linux-headers/COPYING | 2 +
linux-headers/asm-x86/kvm.h | 1 +
linux-headers/linux/iommu.h | 375
Up to now vSMMUv3 has not been integrated with VFIO. VFIO
integration requires to program the physical IOMMU consistently
with the guest mappings. However, as opposed to VTD, SMMUv3 has
no "Caching Mode" which allows easy trapping of guest mappings.
This means the vSMMUV3 cannot use the same VFIO
This bug was fixed in the package qemu - 1:4.2-3ubuntu3
---
qemu (1:4.2-3ubuntu3) focal; urgency=medium
* d/p/stable/lp-1867519-*: Stabilize qemu 4.2 with upstream
patches @qemu-stable (LP: #1867519)
-- Christian Ehrhardt Wed, 18 Mar
2020 13:57:57 +0100
** Changed in: qemu
On Fri, 20 Mar 2020 at 16:32, Philippe Mathieu-Daudé wrote:
> -fwrapv is here indeed.
>
> I use
>
On 3/20/20 5:21 PM, Peter Maydell wrote:
On Fri, 20 Mar 2020 at 16:19, Richard Henderson
wrote:
On 3/20/20 9:04 AM, Philippe Mathieu-Daudé wrote:
Not related to this patch, but this line generates a warning with Clang:
CC rx-softmmu/target/rx/cpu.o
target/rx/cpu.c:158:33: warning:
Hi Oksana,
On Fri, Mar 20, 2020 at 12:16 PM Oksana Vohchana wrote:
>
> Adds test for RDMA migration check
>
> Signed-off-by: Oksana Vohchana
> ---
> tests/acceptance/migration.py | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/tests/acceptance/migration.py
Vladimir Sementsov-Ogievskiy writes:
> 20.03.2020 16:58, Markus Armbruster wrote:
>> Vladimir Sementsov-Ogievskiy writes:
[...]
>>> I will not be surprised, if we missed some more interesting cases :)
>>> But we should proceed. What is our plan? Will you queue v10 for 5.1?
>>
>> v10's PATCH 1+2
Hi Oksana,
On Fri, Mar 20, 2020 at 12:15 PM Oksana Vohchana wrote:
>
> Provides new functions related to the rdma migration test
> Adds functions to check if service RDMA is enabled and gets
> the ip address on the interface where it was configured
>
> Signed-off-by: Oksana Vohchana
> ---
>
On Fri, 20 Mar 2020 at 16:19, Richard Henderson
wrote:
>
> On 3/20/20 9:04 AM, Philippe Mathieu-Daudé wrote:
> > Not related to this patch, but this line generates a warning with Clang:
> >
> > CC rx-softmmu/target/rx/cpu.o
> > target/rx/cpu.c:158:33: warning: The result of the left shift
On 3/20/20 5:14 PM, Peter Maydell wrote:
On Fri, 20 Mar 2020 at 16:11, Philippe Mathieu-Daudé wrote:
On 3/20/20 4:59 PM, Peter Maydell wrote:
On Wed, 18 Mar 2020 at 01:12, Eduardo Habkost wrote:
The following changes since commit d649689a8ecb2e276cc20d3af6d416e3c299cb17:
Merge
Vladimir Sementsov-Ogievskiy writes:
> Script adds ERRP_AUTO_PROPAGATE macro invocation where appropriate and
> does corresponding changes in code (look for details in
> include/qapi/error.h)
>
> Usage example:
> spatch --sp-file scripts/coccinelle/auto-propagated-errp.cocci \
> --macro-file
On 3/20/20 9:04 AM, Philippe Mathieu-Daudé wrote:
> Not related to this patch, but this line generates a warning with Clang:
>
> CC rx-softmmu/target/rx/cpu.o
> target/rx/cpu.c:158:33: warning: The result of the left shift is undefined
> because the left operand is negative
> address =
Philippe Mathieu-Daudé writes:
> This code is inside the "if (dinfo)" condition, so testing
> again here whether it is NULL is unnecessary.
>
> Fixes: dd59bcae7 (Don't size flash memory to match backing image)
> Reported-by: Coverity (CID 1421917)
> Suggested-by: Peter Maydell
> Signed-off-by:
On Fri, 20 Mar 2020 at 16:11, Philippe Mathieu-Daudé wrote:
>
> On 3/20/20 4:59 PM, Peter Maydell wrote:
> > On Wed, 18 Mar 2020 at 01:12, Eduardo Habkost wrote:
> >>
> >> The following changes since commit
> >> d649689a8ecb2e276cc20d3af6d416e3c299cb17:
> >>
> >>Merge remote-tracking branch
1 - 100 of 289 matches
Mail list logo
