qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Santosh Shukla <santosh.shukla@amd.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
	joao.m.martins@oracle.com, Suravee.Suthikulpanit@amd.com,
	vasant.hegde@amd.com, mtosatti@redhat.com,
	marcel.apfelbaum@gmail.com
Subject: Re: [PATCH 0/5] Interrupt Remap support for emulated amd viommu
Date: Tue, 10 Sep 2024 16:14:36 -0400	[thread overview]
Message-ID: <20240910161403-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240904100257.184851-1-santosh.shukla@amd.com>

On Wed, Sep 04, 2024 at 05:02:52AM -0500, Santosh Shukla wrote:
> Series adds following feature support for emulated amd vIOMMU
> 1) Pass Through(PT) mode
> 2) Interrupt Remapping(IR) mode
> 
> 1) PT mode
> Introducing the shared 'nodma' memory region that can be aliased
> by all the devices in the PT mode. Shared memory with aliasing
> approach will help run VM faster when lot of devices attached to
> VM.
> 
> 2) IR mode
> Shared IR memory region with aliasing approach proposed for the
> reason mentioned in 1). Also add support to invalidate Interrupt
> remaping table(IRT).
> 
> Series based on f259e4cb8a8b4ef5463326fc214a7d8d7703d5de.


Fails build on non-kvm:

https://gitlab.com/mstredhat/qemu/-/jobs/7791357916

/usr/lib/gcc-cross/i686-linux-gnu/10/../../../../i686-linux-gnu/bin/ld: libqemu-x86_64-softmmu.a.p/hw_i386_amd_iommu.c.o: in function `amdvi_sysbus_realize':
/builds/mstredhat/qemu/build/../hw/i386/amd_iommu.c:1660: undefined reference to `kvm_enable_x2apic'
collect2: error: ld returned 1 exit status


> Testing:
> 1. nvme/fio testing for VM with > 255 vCPU with xtsup=on and x2apic
> enabled
> 2. Windows Server 2022 VM testing for > 255 vCPU.
> 
> Suravee Suthikulpanit (5):
>   amd_iommu: Rename variable mmio to mr_mmio
>   amd_iommu: Add support for pass though mode
>   amd_iommu: Use shared memory region for Interrupt Remapping
>   amd_iommu: Send notification when invaldate interrupt entry cache
>   amd_iommu: Check APIC ID > 255 for XTSup
> 
>  hw/i386/acpi-build.c |  4 +-
>  hw/i386/amd_iommu.c  | 98 +++++++++++++++++++++++++++++++++++---------
>  hw/i386/amd_iommu.h  |  5 ++-
>  3 files changed, 85 insertions(+), 22 deletions(-)
> 
> -- 
> 2.43.5



  parent reply	other threads:[~2024-09-10 20:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 10:02 [PATCH 0/5] Interrupt Remap support for emulated amd viommu Santosh Shukla
2024-09-04 10:02 ` [PATCH 1/5] amd_iommu: Rename variable mmio to mr_mmio Santosh Shukla
2024-09-04 10:02 ` [PATCH 2/5] amd_iommu: Add support for pass though mode Santosh Shukla
2024-09-04 10:02 ` [PATCH 3/5] amd_iommu: Use shared memory region for Interrupt Remapping Santosh Shukla
2024-09-04 10:02 ` [PATCH 4/5] amd_iommu: Send notification when invaldate interrupt entry cache Santosh Shukla
2024-09-04 10:02 ` [PATCH 5/5] amd_iommu: Check APIC ID > 255 for XTSup Santosh Shukla
2024-09-10 20:14 ` Michael S. Tsirkin [this message]
2024-09-12  5:40   ` [PATCH 0/5] Interrupt Remap support for emulated amd viommu Shukla, Santosh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240910161403-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=joao.m.martins@oracle.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=santosh.shukla@amd.com \
    --cc=vasant.hegde@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).