From: Sairaj Kodilkar <sarunkod@amd.com>
To: Michael Tokarev <mjt@tls.msk.ru>, <qemu-devel@nongnu.org>
Cc: <mst@redhat.com>, <marcel.apfelbaum@gmail.com>,
<pbonzini@redhat.com>, <eduardo@habkost.net>,
<richard.henderson@linaro.org>, <alejandro.j.jimenez@oracle.com>,
<vasant.hegde@amd.com>, <philmd@linaro.org>,
<Suravee.Suthikulpanit@amd.com>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH v3 0/6] hw/i386/amd_iommu: Cleanups and fixes
Date: Thu, 7 Aug 2025 12:10:09 +0530 [thread overview]
Message-ID: <4cfda863-1c2d-4ecd-a81c-1cac8c26244d@amd.com> (raw)
In-Reply-To: <7b278bc0-4752-48fa-b8fa-8a76515069f6@tls.msk.ru>
On 8/6/2025 12:28 PM, Michael Tokarev wrote:
> On 04.08.2025 14:06, Sairaj Kodilkar wrote:
> ...
>>>> Sairaj Kodilkar (6):
>>>> hw/i386/amd_iommu: Fix MMIO register write tracing
>>>> hw/i386/amd_iommu: Remove unused and wrongly set ats_enabled field
>>>> hw/i386/amd_iommu: Move IOAPIC memory region initialization to
>>>> the end
>>>> hw/i386/amd_iommu: Fix amdvi_write*()
>>>> hw/i386/amd_iommu: Support MMIO writes to the status register
>>>> hw/i386/amd_iommu: Fix event log generation
>>>>
>>>> hw/i386/amd_iommu.c | 102 +++++++++++++++++++++++++++++++++
>>>> +----------
>>>> hw/i386/amd_iommu.h | 2 +-
>>>> 2 files changed, 80 insertions(+), 24 deletions(-)
>>>
>>> Hi!
>>>
>>> Is there anything there worth to pick up for qemu 10.0.x stable series?
>>> (the "Move IOAPIC memory init" does not apply to 10.0 already).
>>
>> Hi MJT,
>>
>> I will backport the patch manually and send it to qemu stable mailing
>> list
>
> Hi!
>
> There's no need to back-port it, -- there's just minor context fix
> required, here:
>
> +++ b/hw/i386/amd_iommu.c
> @@ -1693,19 +1693,16 @@ static void amdvi_sysbus_realize(DeviceState
> *dev, Error **errp)
> ...
>
> s->iotlb = g_hash_table_new_full(amdvi_uint64_hash,
> amdvi_uint64_equal, g_free, g_free);
>
> - /* Pseudo address space under root PCI bus. */
> - x86ms->ioapic_as = amdvi_host_dma_iommu(bus, s,
> AMDVI_IOAPIC_SB_DEVID);
> -
> /* set up MMIO */
> memory_region_init_io(&s->mr_mmio, OBJECT(s), &mmio_mem_ops, s,
> "amdvi-mmio", AMDVI_MMIO_SIZE);
>
> the "s->iotlb = g_hash_table_new_full" part were added by commit
> f864a3235ea1d1 "hw/i386/amd_iommu: Isolate AMDVI-PCI from amd-iommu
> device to allow full control over the PCI device creation". It should
> be okay to just remove the 3 marked lines from here (to be moved to
> the right place).
>
> My question was not about back-porting this commit, but more about
> the set of commits which needs to be picked up for the stable series.
>
> I picked up this commit. Please let me know if there are other changes
> needed to be picked up.
>
Hi MJT
I think this one is sufficient.
Thanks
Sairaj
prev parent reply other threads:[~2025-08-07 6:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 6:05 [PATCH v3 0/6] hw/i386/amd_iommu: Cleanups and fixes Sairaj Kodilkar
2025-08-01 6:05 ` [PATCH v3 1/6] hw/i386/amd_iommu: Fix MMIO register write tracing Sairaj Kodilkar
2025-09-30 9:36 ` vsntk18
2025-09-30 9:38 ` Sairaj Kodilkar
2025-08-01 6:05 ` [PATCH v3 2/6] hw/i386/amd_iommu: Remove unused and wrongly set ats_enabled field Sairaj Kodilkar
2025-08-01 14:08 ` Philippe Mathieu-Daudé
2025-08-01 6:05 ` [PATCH v3 3/6] hw/i386/amd_iommu: Move IOAPIC memory region initialization to the end Sairaj Kodilkar
2025-08-01 6:05 ` [PATCH v3 4/6] hw/i386/amd_iommu: Fix amdvi_write*() Sairaj Kodilkar
2025-08-01 6:05 ` [PATCH v3 5/6] hw/i386/amd_iommu: Support MMIO writes to the status register Sairaj Kodilkar
2025-08-01 6:05 ` [PATCH v3 6/6] hw/i386/amd_iommu: Fix event log generation Sairaj Kodilkar
2025-08-02 5:41 ` [PATCH v3 0/6] hw/i386/amd_iommu: Cleanups and fixes Michael Tokarev
2025-08-04 11:06 ` Sairaj Kodilkar
2025-08-06 6:58 ` Michael Tokarev
2025-08-07 6:40 ` Sairaj Kodilkar [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=4cfda863-1c2d-4ecd-a81c-1cac8c26244d@amd.com \
--to=sarunkod@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=richard.henderson@linaro.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).