From: Peter Xu <peterx@redhat.com>
To: Bui Quang Minh <minhquangbui99@gmail.com>
Cc: qemu-devel@nongnu.org, "David Woodhouse" <dwmw2@infradead.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Joao Martins" <joao.m.martins@oracle.com>,
"Jason Wang" <jasowang@redhat.com>
Subject: Re: [PATCH v7 4/5] intel_iommu: allow Extended Interrupt Mode when using userspace APIC
Date: Fri, 28 Jul 2023 17:25:17 -0400 [thread overview]
Message-ID: <ZMQyPbbnyZZ0Foc/@x1n> (raw)
In-Reply-To: <20230728144229.49860-5-minhquangbui99@gmail.com>
On Fri, Jul 28, 2023 at 09:42:28PM +0700, Bui Quang Minh wrote:
> As userspace APIC now supports x2APIC, intel interrupt remapping
> hardware can be set to EIM mode when userspace local APIC is used.
>
> Suggested-by: Joao Martins <joao.m.martins@oracle.com>
> Signed-off-by: Bui Quang Minh <minhquangbui99@gmail.com>
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2023-07-28 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 14:42 [PATCH v7 0/5] Support x2APIC mode with TCG accelerator Bui Quang Minh
2023-07-28 14:42 ` [PATCH v7 1/5] i386/tcg: implement x2APIC registers MSR access Bui Quang Minh
2023-07-28 14:42 ` [PATCH v7 2/5] apic: add support for x2APIC mode Bui Quang Minh
2023-07-28 14:42 ` [PATCH v7 3/5] apic, i386/tcg: add x2apic transitions Bui Quang Minh
2023-07-28 14:42 ` [PATCH v7 4/5] intel_iommu: allow Extended Interrupt Mode when using userspace APIC Bui Quang Minh
2023-07-28 21:25 ` Peter Xu [this message]
2023-07-28 14:42 ` [PATCH v7 5/5] amd_iommu: report x2APIC support to the operating system Bui Quang Minh
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=ZMQyPbbnyZZ0Foc/@x1n \
--to=peterx@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=dwmw2@infradead.org \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=jasowang@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=minhquangbui99@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).