From: "Shukla, Santosh" <santosh.shukla@amd.com>
To: qemu-devel@nongnu.org, pbonzini@redhat.com
Cc: joao.m.martins@oracle.com, Suravee.Suthikulpanit@amd.com,
vasant.hegde@amd.com, mtosatti@redhat.com, mst@redhat.com,
marcel.apfelbaum@gmail.com, alejandro.j.jimenez@oracle.com
Subject: Re: [PATCH v3 0/5] Interrupt Remap support for emulated amd viommu
Date: Mon, 28 Oct 2024 15:56:53 +0530 [thread overview]
Message-ID: <d6a1489a-83a6-a7d5-060c-02e82c28759a@amd.com> (raw)
In-Reply-To: <42e3067c-1e87-9e17-2e89-4a0b910d9f61@amd.com>
Hi there,
Ping? Appreciate any further review comment or series is OK to pull, Please let me know.
Thank you!
Santosh
On 10/9/2024 11:35 AM, Shukla, Santosh wrote:
>
> Ping?
> Gentle reminder.
>
> Thanks,
> Santosh
>
> On 9/27/2024 10:59 PM, 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 e10cd93872c31332b002c933a798ab0bc51705a4
>>
>> 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.
>>
>> Change History:
>>
>> v3:
>> - Incorporated Alejandro's v2 nits comment.
>>
>> V2:
>> - https://lore.kernel.org/qemu-devel/20240916143116.169693-1-santosh.shukla@amd.com/
>>
>> V1:
>> - https://lore.kernel.org/all/20240904100257.184851-3-santosh.shukla@amd.com/T/
>>
>> 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 invalidate 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(-)
>>
prev parent reply other threads:[~2024-10-28 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 17:29 [PATCH v3 0/5] Interrupt Remap support for emulated amd viommu Santosh Shukla
2024-09-27 17:29 ` [PATCH v3 1/5] amd_iommu: Rename variable mmio to mr_mmio Santosh Shukla
2024-09-27 17:29 ` [PATCH v3 2/5] amd_iommu: Add support for pass though mode Santosh Shukla
2024-09-27 17:29 ` [PATCH v3 3/5] amd_iommu: Use shared memory region for Interrupt Remapping Santosh Shukla
2024-09-27 17:29 ` [PATCH v3 4/5] amd_iommu: Send notification when invalidate interrupt entry cache Santosh Shukla
2024-09-27 17:29 ` [PATCH v3 5/5] amd_iommu: Check APIC ID > 255 for XTSup Santosh Shukla
2024-10-09 6:05 ` [PATCH v3 0/5] Interrupt Remap support for emulated amd viommu Shukla, Santosh
2024-10-28 10:26 ` Shukla, Santosh [this message]
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=d6a1489a-83a6-a7d5-060c-02e82c28759a@amd.com \
--to=santosh.shukla@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=joao.m.martins@oracle.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).