From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Boqun Feng <boqun.feng@gmail.com>, Wei Liu <wei.liu@kernel.org>
Cc: "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Sunil Muthuswamy" <sunilmut@linux.microsoft.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
linux-kernel@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
"Dexuan Cui" <decui@microsoft.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
linux-hyperv@vger.kernel.org,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, "K. Y. Srinivasan" <kys@microsoft.com>
Subject: Re: [RFC PATCH v2] PCI: hv: Avoid the retarget interrupt hypercall in irq_unmask() on ARM64
Date: Wed, 2 Mar 2022 10:16:25 +0000 [thread overview]
Message-ID: <164621616889.27346.10460850825594773169.b4-ty@arm.com> (raw)
In-Reply-To: <20220217034525.1687678-1-boqun.feng@gmail.com>
On Thu, 17 Feb 2022 11:45:19 +0800, Boqun Feng wrote:
> On ARM64 Hyper-V guests, SPIs are used for the interrupts of virtual PCI
> devices, and SPIs can be managed directly via GICD registers. Therefore
> the retarget interrupt hypercall is not needed on ARM64.
>
> An arch-specific interface hv_arch_irq_unmask() is introduced to handle
> the architecture level differences on this. For x86, the behavior
> remains unchanged, while for ARM64 no hypercall is invoked when
> unmasking an irq for virtual PCI devices.
>
> [...]
Applied to pci/hv, thanks!
[1/1] PCI: hv: Avoid the retarget interrupt hypercall in irq_unmask() on ARM64
https://git.kernel.org/lpieralisi/pci/c/d06957d7a6
Thanks,
Lorenzo
prev parent reply other threads:[~2022-03-02 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 3:45 [RFC PATCH v2] PCI: hv: Avoid the retarget interrupt hypercall in irq_unmask() on ARM64 Boqun Feng
2022-02-17 16:31 ` Michael Kelley (LINUX)
2022-02-21 17:56 ` Wei Liu
2022-03-02 3:13 ` Boqun Feng
2022-03-02 9:50 ` Lorenzo Pieralisi
2022-03-02 10:16 ` Lorenzo Pieralisi [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=164621616889.27346.10460850825594773169.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=boqun.feng@gmail.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kw@linux.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=sunilmut@linux.microsoft.com \
--cc=wei.liu@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;
as well as URLs for NNTP newsgroup(s).