From: David Woodhouse <dwmw2@infradead.org>
To: Yi Liu <yi.l.liu@intel.com>,
CLEMENT MATHIEU--DRIF <clement.mathieu--drif@eviden.com>,
Konstantin Belousov <kib@kib.kiev.ua>
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, 22 Jul 2025 14:04:20 +0200 [thread overview]
Message-ID: <60537d9a2f87c36160b26a5154a1839df3e90b58.camel@infradead.org> (raw)
In-Reply-To: <8fe80210-7cf0-4fec-94d4-79b41216a620@intel.com>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
On Tue, 2025-07-15 at 20:35 +0800, Yi Liu wrote:
>
> 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. :)
Are there any refinements you believe are necessary?
https://gitlab.com/dwmw2/qemu/-/pipelines/1941324674 looks like it's
going to be clean, and I think we resolved everything we talked about.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]
next prev parent reply other threads:[~2025-07-22 12: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
2025-07-15 13:59 ` CLEMENT MATHIEU--DRIF
2025-07-22 12:04 ` David Woodhouse [this message]
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=60537d9a2f87c36160b26a5154a1839df3e90b58.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=clement.mathieu--drif@eviden.com \
--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 \
--cc=yi.l.liu@intel.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).