qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 4 Aug 2025 16:36:40 +0530	[thread overview]
Message-ID: <d29ccd29-d4c6-41fa-8158-93f9a21ab3ba@amd.com> (raw)
In-Reply-To: <703d1159-7bdc-47b7-be08-64d7b000e45b@tls.msk.ru>



On 8/2/2025 11:11 AM, Michael Tokarev wrote:
> On 01.08.2025 09:05, Sairaj Kodilkar wrote:
>> This series provides few cleanups and fixes for the amd iommu
>>
>> Changes since v2:
>> - Used VMSTATE_UNUSED() to maintain migration compatibility when 
>> ats_enabled
>>    flag is removed [Phil].
>> - Simplified the amdvi_writew [Phil].
>> v2: https://lore.kernel.org/qemu- 
>> devel/2e8f2b72-8fb5-474f-9844-61f306efeb2b@amd.com/
>>
>> Changes since v1:
>> - Dropped top two patches which depend on the Alejandro's changes and 
>> rebased
>>    remaining patches on top of v10.1.0-rc0 [Phil].
>> - Added a patch to fix amdvi_write*() [Ethon].
>> - Reset event log head and tail when guest writes to event log base 
>> register
>>    [Ethon].
>> - Considered "evtlog_intr" flag while generating event log interrupt 
>> [Ethon].
>> - Fixed comment [Ethon].
>> v1: https://lore.kernel.org/qemu-devel/20250716073145.915-1- 
>> sarunkod@amd.com/
>>
>> Base commit: 9e601684dc24a521bb1d23215a63e5c6e79ea0bb (v10.1.0-rc0)
>>
>> 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

Thanks
Sairaj




  reply	other threads:[~2025-08-04 11:25 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 [this message]
2025-08-06  6:58     ` Michael Tokarev
2025-08-07  6:40       ` Sairaj Kodilkar

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=d29ccd29-d4c6-41fa-8158-93f9a21ab3ba@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).