From: Sunil Muthuswamy <sunilmut@microsoft.com>
To: "Marc Zyngier" <maz@kernel.org>,
"Michael Kelley" <mikelley@microsoft.com>,
"Boqun Feng" <Boqun.Feng@microsoft.com>,
"KY Srinivasan" <kys@microsoft.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
"Dexuan Cui" <decui@microsoft.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"\"Krzysztof Wilczyński\"" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Wei Liu" <wei.liu@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"\"H. Peter Anvin\"" <hpa@zytor.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/2] PCI: hv: Hyper-V vPCI for ARM64
Date: Fri, 8 Oct 2021 17:19:53 +0000 [thread overview]
Message-ID: <MW4PR21MB200217CCFBC351FD12D68DF0C0B29@MW4PR21MB2002.namprd21.prod.outlook.com> (raw)
Current Hyper-V vPCI code only compiles and works for x64. There are
some hardcoded assumptions about the architectural IRQ chip and other
arch defines.
This patch series adds support for Hyper-V vPCI for ARM64 by first
breaking the current hard coded dependency in the vPCI code and
making it arch neutral. That is in the first patch. The second
patch introduces a Hyper-V vPCI MSI IRQ chip for allocating SPI
vectors.
changes in v2:
- Moved the irqchip implementation to drivers/pci as suggested
by Marc Zyngier
- Addressed Multi-MSI handling issues identified by Marc Zyngier
- Addressed lock/synchronization primitive as suggested by Marc
Zyngier
- Addressed other code feedback from Marc Zyngier
Sunil Muthuswamy (2):
PCI: hv: Make the code arch neutral
PCI: hv: Support for Hyper-V vPCI for ARM64
MAINTAINERS | 2 +
arch/arm64/include/asm/hyperv-tlfs.h | 9 +
arch/x86/include/asm/hyperv-tlfs.h | 33 +++
arch/x86/include/asm/mshyperv.h | 7 -
drivers/pci/Kconfig | 2 +-
drivers/pci/controller/Kconfig | 2 +-
drivers/pci/controller/Makefile | 2 +-
drivers/pci/controller/pci-hyperv-irqchip.c | 256 ++++++++++++++++++++
drivers/pci/controller/pci-hyperv-irqchip.h | 21 ++
drivers/pci/controller/pci-hyperv.c | 58 +++--
include/asm-generic/hyperv-tlfs.h | 33 ---
11 files changed, 363 insertions(+), 62 deletions(-)
create mode 100644 drivers/pci/controller/pci-hyperv-irqchip.c
create mode 100644 drivers/pci/controller/pci-hyperv-irqchip.h
base-commit: e4e737bb5c170df6135a127739a9e6148ee3da82
--
2.25.1
next reply other threads:[~2021-10-08 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 17:19 Sunil Muthuswamy [this message]
2021-10-08 18:52 ` [PATCH v2 0/2] PCI: hv: Hyper-V vPCI for ARM64 Bjorn Helgaas
2021-10-08 19:11 ` [EXTERNAL] " Sunil Muthuswamy
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=MW4PR21MB200217CCFBC351FD12D68DF0C0B29@MW4PR21MB2002.namprd21.prod.outlook.com \
--to=sunilmut@microsoft.com \
--cc=Boqun.Feng@microsoft.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.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=lorenzo.pieralisi@arm.com \
--cc=maz@kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=robh@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--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).