mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Qihang <q.h.hack.winter@gmail.com>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
	Will Deacon <will@kernel.org>, Jason Gunthorpe <jgg@nvidia.com>,
	Robin Murphy <robin.murphy@arm.com>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	Vasant Hegde <vasant.hegde@amd.com>
Subject: Re: [PATCH 0/2] iommu/io-pgfault: reject partial faults after device removal
Date: Sun, 22 Nov 2026 15:39:19 +0800	[thread overview]
Message-ID: <4420a997-82e9-43e6-8ceb-5ede44594c51@linux.intel.com> (raw)
In-Reply-To: <CAH78Gvubo20uU4ntOxzd-+B6GHpUovL_wYQt9yahF-8=x3sEVA@mail.gmail.com>

On 11/21/2026 10:13 AM, Qihang wrote:
> Hi Baolu,
> 
> Thanks for confirming the VT-d ordering bug. I'll keep this series
> withdrawn and won't resend it.
> 
> I still have one question about AMD. detach_device() calls
> iopf_queue_flush_dev() just before amd_iommu_iopf_remove_device().
> That flush only waits on the iopf workqueue, while the PPR IRQ thread
> runs amd_iommu_poll_ppr_log() and reports the fault through
> iommu_report_device_fault() directly. What ensures that the thread has
> finished reporting faults for this device, and cannot report another
> one, before the device is removed from the IOPF queue?

+ Vasant

> Thanks,
> Qihang

Thanks,
baolu

      reply	other threads:[~2026-11-22  7:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  1:54 Qihang
2026-11-17  1:54 ` [PATCH 1/2] iommu/io-pgfault: unlink partial faults before freeing them Qihang
2026-11-17  1:54 ` [PATCH 2/2] iommu/io-pgfault: reject partial faults after the device is removed Qihang
2026-11-20  7:56 ` [PATCH 0/2] iommu/io-pgfault: reject partial faults after device removal Baolu Lu
2026-11-20  9:26   ` Qihang
2026-11-21  1:25     ` Baolu Lu
2026-11-21  2:13       ` Qihang
2026-11-22  7:39         ` Baolu Lu [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=4420a997-82e9-43e6-8ceb-5ede44594c51@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=q.h.hack.winter@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=vasant.hegde@amd.com \
    --cc=will@kernel.org \
    /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

all inboxes | Powered by JetHome®