linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
	Arnd Bergmann <arnd@arndb.de>, Marc Zyngier <maz@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
	Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Rob Herring <robh@kernel.org>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Mike Rapoport <rppt@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jon Derrick <jonathan.derrick@intel.com>,
	Sunil Muthuswamy <sunilmut@microsoft.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-hyperv@vger.kernel.org
Subject: [RFC v2 0/7] PCI: hv: Support host bridge probing on ARM64
Date: Mon,  3 May 2021 22:46:28 +0800	[thread overview]
Message-ID: <20210503144635.2297386-1-boqun.feng@gmail.com> (raw)

Hi Bjorn, Arnd and Marc,

This is the updated version of my first try to prepare for virtual PCI
support on Hyper-V ARM64:

	https://lore.kernel.org/lkml/20210319161956.2838291-1-boqun.feng@gmail.com/

, thanks a lot for your suggestions in the previous one.

This is still more an RFC, and trying to see what I'm on the correct
direction.

The basic problem we need to resolve is that ARM64 is an arch with
PCI_DOMAINS_GENERIC=y, so the bus sysdata is pci_config_window. However,
Hyper-V PCI provides a paravirtualized PCI interface, so there is no
actual pci_config_window for a PCI host bridge, so no information can be
retrieve from the pci_config_window of a Hyper-V virtual PCI bus.

This patchset mainly handle three things:

1)	PCI domain number. As suggested by Bjorn and Arnd, I introduce
	a member in pci_host_bridge, and Hyper-V can use it to set up
	the correct PCI domain number for the bus, while others remain
	the same behavior.

2)	MSI irq_domain. As suggested by Arnd, I use the
	GENERIC_MSI_IRQ_DOMAIN's dev_{set,get}_msi_domain() to allow
	Hyper-V set up the msi domain using generic code.

3)	pcibios_root_bridge_prepare(). This one is new, PCI core will
	call this during host bridge register, and it will access the
	pci_config_window, luckily the only field it accesses it the
	parent field, and I change the ARM64's behavior to treat the
	acpi device as NULL if pci_config_window::parent is NULL, so
	that Hyper-V can provide a all-zeroed pci_config_window.

With the above, we could enable the virtual PCI on Hyper-V ARM64 guest
with other code under development.

Comments and suggestions are welcome.

Regards,
Boqun

Arnd Bergmann (1):
  PCI: hv: Generify PCI probing

Boqun Feng (6):
  PCI: Introduce pci_host_bridge::domain_nr
  PCI: Allow msi domain set-up at host probing time
  PCI: hv: Use pci_host_bridge::domain_nr for PCI domain
  PCI: hv: Set up msi domain at bridge probing time
  PCI: arm64: Allow pci_config_window::parent to be NULL
  PCI: hv: Turn on the host bridge probing on ARM64

 arch/arm/kernel/bios32.c              |  2 +
 arch/arm/mach-dove/pcie.c             |  2 +
 arch/arm/mach-mv78xx0/pcie.c          |  2 +
 arch/arm/mach-orion5x/pci.c           |  2 +
 arch/arm64/kernel/pci.c               |  5 +-
 arch/mips/pci/pci-legacy.c            |  2 +
 arch/mips/pci/pci-xtalk-bridge.c      |  2 +
 drivers/pci/controller/pci-ftpci100.c |  2 +
 drivers/pci/controller/pci-hyperv.c   | 90 +++++++++++++++------------
 drivers/pci/controller/pci-mvebu.c    |  2 +
 drivers/pci/pci.c                     |  4 +-
 drivers/pci/probe.c                   | 12 +++-
 include/linux/pci.h                   | 11 +++-
 13 files changed, 89 insertions(+), 49 deletions(-)

-- 
2.30.2


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-05-03 14:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 14:46 Boqun Feng [this message]
2021-05-03 14:46 ` [RFC v2 1/7] PCI: Introduce pci_host_bridge::domain_nr Boqun Feng
2021-05-04  5:16   ` Mike Rapoport
2021-05-04 14:34     ` Rob Herring
2021-05-06 10:52     ` Lorenzo Pieralisi
2021-05-10 13:44       ` Boqun Feng
2021-05-14  9:19         ` Lorenzo Pieralisi
2021-05-03 14:46 ` [RFC v2 2/7] PCI: Allow msi domain set-up at host probing time Boqun Feng
2021-05-03 14:46 ` [RFC v2 3/7] PCI: hv: Generify PCI probing Boqun Feng
2021-05-03 14:46 ` [RFC v2 4/7] PCI: hv: Use pci_host_bridge::domain_nr for PCI domain Boqun Feng
2021-05-03 14:46 ` [RFC v2 5/7] PCI: hv: Set up msi domain at bridge probing time Boqun Feng
2021-05-03 14:46 ` [RFC v2 6/7] PCI: arm64: Allow pci_config_window::parent to be NULL Boqun Feng
2021-05-06 22:25   ` Bjorn Helgaas
2021-05-10  7:04     ` Boqun Feng
2021-05-03 14:46 ` [RFC v2 7/7] PCI: hv: Turn on the host bridge probing on ARM64 Boqun Feng

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=20210503144635.2297386-1-boqun.feng@gmail.com \
    --to=boqun.feng@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=gregory.clement@bootlin.com \
    --cc=haiyangz@microsoft.com \
    --cc=jonathan.derrick@intel.com \
    --cc=kys@microsoft.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=maz@kernel.org \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=rppt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=sthemmin@microsoft.com \
    --cc=sunilmut@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tsbogend@alpha.franken.de \
    --cc=wei.liu@kernel.org \
    --cc=will@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).