[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MWHPR21MB1593A265118977A57FF3B329D7369@MWHPR21MB1593.namprd21.prod.outlook.com>
Date: Thu, 17 Feb 2022 16:31:06 +0000
From: "Michael Kelley (LINUX)" <mikelley@...rosoft.com>
To: Boqun Feng <boqun.feng@...il.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Wei Liu <wei.liu@...nel.org>
CC: Sunil Muthuswamy <sunilmut@...ux.microsoft.com>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Dexuan Cui <decui@...rosoft.com>,
Rob Herring <robh@...nel.org>,
Krzysztof WilczyĆski <kw@...ux.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [RFC PATCH v2] PCI: hv: Avoid the retarget interrupt hypercall in
irq_unmask() on ARM64
From: Boqun Feng <boqun.feng@...il.com> Sent: Wednesday, February 16, 2022 7:45 PM
>
> 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.
>
> Signed-off-by: Boqun Feng <boqun.feng@...il.com>
> ---
> v1 -> v2:
>
> * Introduce arch-specific interface hv_arch_irq_unmask() as
> suggested by Bjorn
>
> drivers/pci/controller/pci-hyperv.c | 233 +++++++++++++++-------------
> 1 file changed, 122 insertions(+), 111 deletions(-)
Reviewed-by: Michael Kelley <mikelley@...rosoft.com>
Powered by blists - more mailing lists