qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yi Liu <yi.l.liu@intel.com>
To: CLEMENT MATHIEU--DRIF <clement.mathieu--drif@eviden.com>,
	"Konstantin Belousov" <kib@kib.kiev.ua>,
	David Woodhouse <dwmw2@infradead.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>, Le Tan <tamlokveer@gmail.com>,
	"jhb@freebsd.org" <jhb@freebsd.org>,
	"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	 Richard Henderson <richard.henderson@linaro.org>,
	Eduardo Habkost <eduardo@habkost.net>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2] intel_iommu: Allow both Status Write and Interrupt Flag in QI wait
Date: Tue, 15 Jul 2025 20:35:55 +0800	[thread overview]
Message-ID: <8fe80210-7cf0-4fec-94d4-79b41216a620@intel.com> (raw)
In-Reply-To: <afe3881b-1193-4d89-b0d0-6c316e54684f@eviden.com>

On 2025/7/15 14:11, CLEMENT MATHIEU--DRIF wrote:
> 
> 
> On 14/07/2025 11:22 pm, Konstantin Belousov wrote:
>> Caution: External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe.
>>
>>
>> On Mon, Jul 14, 2025 at 05:41:22PM +0100, David Woodhouse wrote:
>>> On 14 July 2025 15:28:09 GMT+01:00, Yi Liu <yi.l.liu@intel.com> wrote:
>>>> Hi David,
>>>>
>>>> On 2025/7/14 16:00, David Woodhouse wrote:
>>>>> From: David Woodhouse <dwmw@amazon.co.uk>
>>>>>
>>>>> FreeBSD does both, and this appears to be perfectly valid. The VT-d
>>>>> spec even talks about the ordering (the status write should be done
>>>>> first, unsurprisingly).
> 
> Are you talking about the ordering constraint mentioned in bullet
> "Page-request Drain (PD)"?

David is talking about the IF and SW flags. And he is correct. Spec has 
below sentence. It means a wait descriptor can have both IF and SW set
and indeed completion interrupt happens later than status write.  Let's
go on refine the patch. :)

"The invalidation completion event interrupt must push any in-flight 
invalidation completion status
writes, including status writes that may have originated from the same 
inv_wait_dsc for which the interrupt was generated."


Regards,
Yi Liu


  parent reply	other threads:[~2025-07-15 13:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14  8:00 [PATCH v2] intel_iommu: Allow both Status Write and Interrupt Flag in QI wait David Woodhouse
2025-07-14 14:28 ` Yi Liu
2025-07-14 16:41   ` David Woodhouse
2025-07-14 21:22     ` Konstantin Belousov via
2025-07-15  6:11       ` CLEMENT MATHIEU--DRIF
2025-07-15  8:27         ` David Woodhouse
2025-07-15 12:27           ` CLEMENT MATHIEU--DRIF
2025-07-16  4:01             ` Yi Liu
2025-07-16  4:05               ` Konstantin Belousov
2025-07-16  9:23                 ` Yi Liu
2025-07-16  9:36                   ` Konstantin Belousov via
2025-07-15 12:35         ` Yi Liu [this message]
2025-07-15 13:59           ` CLEMENT MATHIEU--DRIF
2025-07-22 12:04           ` David Woodhouse
2025-08-01 15:09             ` Liu, Yi L
2025-08-02  5:38 ` Michael Tokarev

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=8fe80210-7cf0-4fec-94d4-79b41216a620@intel.com \
    --to=yi.l.liu@intel.com \
    --cc=clement.mathieu--drif@eviden.com \
    --cc=dwmw2@infradead.org \
    --cc=eduardo@habkost.net \
    --cc=jasowang@redhat.com \
    --cc=jhb@freebsd.org \
    --cc=kib@kib.kiev.ua \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=tamlokveer@gmail.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).