[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87fsqnwniv.wl-maz@kernel.org>
Date: Mon, 20 Dec 2021 10:58:48 +0000
From: Marc Zyngier <maz@...nel.org>
To: Sunil Muthuswamy <sunilmut@...ux.microsoft.com>
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
wei.liu@...nel.org, decui@...rosoft.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, hpa@...or.com,
lorenzo.pieralisi@....com, robh@...nel.org, kw@...ux.com,
bhelgaas@...gle.com, arnd@...db.de, x86@...nel.org,
linux-kernel@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-pci@...r.kernel.org, linux-arch@...r.kernel.org,
Sunil Muthuswamy <sunilmut@...rosoft.com>
Subject: Re: [PATCH v7 0/2] PCI: hv: Hyper-V vPCI for arm64
On Fri, 17 Dec 2021 18:51:59 +0000,
Sunil Muthuswamy <sunilmut@...ux.microsoft.com> wrote:
>
> From: Sunil Muthuswamy <sunilmut@...rosoft.com>
>
> Current Hyper-V vPCI code only compiles and works for x86. There are some
> hardcoded assumptions about the architectural IRQ chip and other arch
> defines.
>
> Add support for Hyper-V vPCI for arm64 by first breaking the current hard
> coded dependency using a set of new interfaces and implementing those for
> x86 first. That is in the first patch. The second patch adds support for
> Hyper-V vPCI for arm64 by implementing the above mentioned interfaces. That
> is done by introducing a Hyper-V vPCI specific MSI IRQ domain & chip for
> allocating SPI vectors.
For the series,
Reviewed-by: Marc Zyngier <maz@...nel.org>
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists