linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sunil Muthuswamy <sunilmut@microsoft.com>
To: "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: "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 0/2] PCI: hv: Hyper-V vPCI for ARM64
Date: Mon, 13 Sep 2021 17:35:45 +0000	[thread overview]
Message-ID: <MW4PR21MB20022E3A433CFA1558C71485C0D99@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.

This patch depends on two other independent patch sets. First one
is the patch series from Michael Kelley titled:
"Enable Linux guests on Hyper-V on ARM64"
and the second one is from Boqun Feng titled:
"PCI: hv: Support host bridge probing on ARM64". Neither of these
patches are merged into one branch at the moment. I think its best
to carry this patch with the 'hyperv-next' tree after merging Boqun's
patch series.

Sunil Muthuswamy (2):
  PCI: hv: Make the code arch neutral
  PCI: hv: Support for Hyper-V vPCI for ARM64

 arch/arm64/hyperv/Makefile           |   2 +-
 arch/arm64/hyperv/hv_pci.c           | 275 +++++++++++++++++++++++++++
 arch/arm64/include/asm/hyperv-tlfs.h |   9 +
 arch/arm64/include/asm/mshyperv.h    |  26 +++
 arch/x86/include/asm/hyperv-tlfs.h   |  33 ++++
 arch/x86/include/asm/mshyperv.h      |  25 +++
 drivers/pci/Kconfig                  |   2 +-
 drivers/pci/controller/Kconfig       |   2 +-
 drivers/pci/controller/pci-hyperv.c  |  49 +++--
 include/asm-generic/hyperv-tlfs.h    |  33 ----
 10 files changed, 405 insertions(+), 51 deletions(-)
 create mode 100644 arch/arm64/hyperv/hv_pci.c

-- 
2.25.1

                 reply	other threads:[~2021-09-13 17:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=MW4PR21MB20022E3A433CFA1558C71485C0D99@MW4PR21MB2002.namprd21.prod.outlook.com \
    --to=sunilmut@microsoft.com \
    --cc=Boqun.Feng@microsoft.com \
    --cc=bhelgaas@google.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=lorenzo.pieralisi@arm.com \
    --cc=mikelley@microsoft.com \
    --cc=robh@kernel.org \
    --cc=sthemmin@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).