Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1292390 > unrolled thread

RE: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V VMs

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  RE: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V  VMs KY Srinivasan <kys@microsoft.com> - 2015-12-15 18:40 +0100
    RE: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V  VMs Thomas Gleixner <tglx@linutronix.de> - 2015-12-19 12:30 +0100
      RE: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V  VMs KY Srinivasan <kys@microsoft.com> - 2015-12-19 18:30 +0100
        RE: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V  VMs Thomas Gleixner <tglx@linutronix.de> - 2015-12-19 21:30 +0100
          RE: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V  VMs KY Srinivasan <kys@microsoft.com> - 2015-12-20 06:20 +0100

#1292390 — RE: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V VMs

> -----Original Message-----
> From: jakeo@microsoft.com [mailto:jakeo@microsoft.com]
> Sent: Wednesday, December 9, 2015 2:55 PM
> To: gregkh@linuxfoundation.org; KY Srinivasan <kys@microsoft.com>; linux-
> kernel@vger.kernel.org; devel@linuxdriverproject.org; olaf@aepfle.de;
> apw@canonical.com; vkuznets@redhat.com; tglx@linutronix.de; Haiyang
> Zhang <haiyangz@microsoft.com>; marc.zyngier@arm.com;
> bhelgaas@google.com; linux-pci@vger.kernel.org
> Cc: Jake Oshins <jakeo@microsoft.com>
> Subject: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V
> VMs
> 
> From: Jake Oshins <jakeo@microsoft.com>
> 
> This version of the patch series removes warning when compiling x86
> 32-bit.
> 
> First, export functions that allow correlating Hyper-V virtual processors
> and Linux cpus, along with the means for invoking a hypercall that targets
> interrupts at chosen vectors on specific cpus.
> 
> Second, mark various parts of IRQ domain related code as exported, so that
> this PCI front-end can implement an IRQ domain as part of a module.  (The
> alternative would be to pull all tyhis into the kernel, which would pull
> in a lot of other Hyper-V related code, as this IRQ domain depends on
> vmbus.ko.)
> 
> Third, modify PCI so that new root PCI buses can be marked with an
> associated
> fwnode_handle, and so that root PCI buses can look up their associated IRQ
> domain by that handle.
> 
> Fourth, introduce a new driver, hv_pcifront, which exposes root PCI buses in
> a Hyper-V VM.  These root PCI buses expose real PCIe device, or PCI Virtual
> Functions.
> 
> 
> Jake Oshins (7):
>   drivers:hv: Export a function that maps Linux CPU num onto Hyper-V
>     proc num
>   drivers:hv: Export hv_do_hypercall()
>   PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
>   PCI: Add fwnode_handle to pci_sysdata
>   PCI: irqdomain: Look up IRQ domain by fwnode_handle
>   drivers:hv: Define the channel type of Hyper-V PCI Express
>     pass-through
>   PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
> 
>  MAINTAINERS                    |    1 +
>  arch/x86/include/asm/msi.h     |    6 +
>  arch/x86/include/asm/pci.h     |   15 +
>  arch/x86/kernel/apic/msi.c     |    8 +-
>  arch/x86/kernel/apic/vector.c  |    2 +
>  drivers/hv/hv.c                |   20 +-
>  drivers/hv/hyperv_vmbus.h      |    2 +-
>  drivers/hv/vmbus_drv.c         |   17 +
>  drivers/pci/Kconfig            |    7 +
>  drivers/pci/host/Makefile      |    1 +
>  drivers/pci/host/hv_pcifront.c | 2250
> ++++++++++++++++++++++++++++++++++++++++
>  drivers/pci/msi.c              |    4 +
>  drivers/pci/probe.c            |   15 +
>  include/linux/hyperv.h         |   14 +
>  include/linux/pci.h            |    4 +
>  kernel/irq/chip.c              |    1 +
>  kernel/irq/irqdomain.c         |    4 +
>  17 files changed, 2357 insertions(+), 14 deletions(-)
>  create mode 100644 drivers/pci/host/hv_pcifront.c
> 
> --
> 1.9.1

Of these 7 patches, Greg has committed all of the VMBUS
related supporting patches (3 patches). Thomas, can you 
take the IRQ related patches through your tree.

Regards,

K. Y

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1295361

On Tue, 15 Dec 2015, KY Srinivasan wrote:
> 
> Of these 7 patches, Greg has committed all of the VMBUS
> related supporting patches (3 patches). Thomas, can you 
> take the IRQ related patches through your tree.

That does not make any sense.

> > Jake Oshins (7):
> >   drivers:hv: Export a function that maps Linux CPU num onto Hyper-V
> >     proc num
> >   drivers:hv: Export hv_do_hypercall()
> >   PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
> >   PCI: Add fwnode_handle to pci_sysdata
> >   PCI: irqdomain: Look up IRQ domain by fwnode_handle
> >   drivers:hv: Define the channel type of Hyper-V PCI Express
> >     pass-through
> >   PCI: hv: New paravirtual PCI front-end for Hyper-V VMs

That series cannot be ripped apart. The PCI part does not even compile
w/o the drivers/hv part in place.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1295420

> -----Original Message-----
> From: Thomas Gleixner [mailto:tglx@linutronix.de]
> Sent: Saturday, December 19, 2015 3:27 AM
> To: KY Srinivasan <kys@microsoft.com>
> Cc: Jake Oshins <jakeo@microsoft.com>; gregkh@linuxfoundation.org; linux-
> kernel@vger.kernel.org; devel@linuxdriverproject.org; olaf@aepfle.de;
> apw@canonical.com; vkuznets@redhat.com; Haiyang Zhang
> <haiyangz@microsoft.com>; marc.zyngier@arm.com;
> bhelgaas@google.com; linux-pci@vger.kernel.org
> Subject: RE: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-
> V VMs
> 
> On Tue, 15 Dec 2015, KY Srinivasan wrote:
> >
> > Of these 7 patches, Greg has committed all of the VMBUS
> > related supporting patches (3 patches). Thomas, can you
> > take the IRQ related patches through your tree.
> 
> That does not make any sense.
> 
> > > Jake Oshins (7):
> > >   drivers:hv: Export a function that maps Linux CPU num onto Hyper-V
> > >     proc num
> > >   drivers:hv: Export hv_do_hypercall()
> > >   PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
> > >   PCI: Add fwnode_handle to pci_sysdata
> > >   PCI: irqdomain: Look up IRQ domain by fwnode_handle
> > >   drivers:hv: Define the channel type of Hyper-V PCI Express
> > >     pass-through
> > >   PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
> 
> That series cannot be ripped apart. The PCI part does not even compile
> w/o the drivers/hv part in place.

What I was proposing was that after you pick up the hv related patches in
Greg's tree in the next cycle, would you be willing to take the IRQ related
patches through your tree. Sorry for the confusion.

Regards,

K. Y
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1295452

On Sat, 19 Dec 2015, KY Srinivasan wrote:
> > From: Thomas Gleixner [mailto:tglx@linutronix.de]
> > On Tue, 15 Dec 2015, KY Srinivasan wrote:
> > >
> > > Of these 7 patches, Greg has committed all of the VMBUS
> > > related supporting patches (3 patches). Thomas, can you
> > > take the IRQ related patches through your tree.
> > 
> > That does not make any sense.
> > 
> > > > Jake Oshins (7):
> > > >   drivers:hv: Export a function that maps Linux CPU num onto Hyper-V
> > > >     proc num
> > > >   drivers:hv: Export hv_do_hypercall()
> > > >   PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
> > > >   PCI: Add fwnode_handle to pci_sysdata
> > > >   PCI: irqdomain: Look up IRQ domain by fwnode_handle
> > > >   drivers:hv: Define the channel type of Hyper-V PCI Express
> > > >     pass-through
> > > >   PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
> > 
> > That series cannot be ripped apart. The PCI part does not even compile
> > w/o the drivers/hv part in place.
> 
> What I was proposing was that after you pick up the hv related patches in
> Greg's tree in the next cycle, would you be willing to take the IRQ related
> patches through your tree. Sorry for the confusion.

You mean: PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.

Right? Aside from the misleading subject line, I can pick that one
up. The rest wants to go through the PCI tree.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1295524

> -----Original Message-----
> From: Thomas Gleixner [mailto:tglx@linutronix.de]
> Sent: Saturday, December 19, 2015 12:21 PM
> To: KY Srinivasan <kys@microsoft.com>
> Cc: Jake Oshins <jakeo@microsoft.com>; gregkh@linuxfoundation.org; linux-
> kernel@vger.kernel.org; devel@linuxdriverproject.org; olaf@aepfle.de;
> apw@canonical.com; vkuznets@redhat.com; Haiyang Zhang
> <haiyangz@microsoft.com>; marc.zyngier@arm.com;
> bhelgaas@google.com; linux-pci@vger.kernel.org
> Subject: RE: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-
> V VMs
> 
> On Sat, 19 Dec 2015, KY Srinivasan wrote:
> > > From: Thomas Gleixner [mailto:tglx@linutronix.de]
> > > On Tue, 15 Dec 2015, KY Srinivasan wrote:
> > > >
> > > > Of these 7 patches, Greg has committed all of the VMBUS
> > > > related supporting patches (3 patches). Thomas, can you
> > > > take the IRQ related patches through your tree.
> > >
> > > That does not make any sense.
> > >
> > > > > Jake Oshins (7):
> > > > >   drivers:hv: Export a function that maps Linux CPU num onto Hyper-V
> > > > >     proc num
> > > > >   drivers:hv: Export hv_do_hypercall()
> > > > >   PCI: Make it possible to implement a PCI MSI IRQ Domain in a
> module.
> > > > >   PCI: Add fwnode_handle to pci_sysdata
> > > > >   PCI: irqdomain: Look up IRQ domain by fwnode_handle
> > > > >   drivers:hv: Define the channel type of Hyper-V PCI Express
> > > > >     pass-through
> > > > >   PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
> > >
> > > That series cannot be ripped apart. The PCI part does not even compile
> > > w/o the drivers/hv part in place.
> >
> > What I was proposing was that after you pick up the hv related patches in
> > Greg's tree in the next cycle, would you be willing to take the IRQ related
> > patches through your tree. Sorry for the confusion.
> 
> You mean: PCI: Make it possible to implement a PCI MSI IRQ Domain in a
> module.
> 
> Right? Aside from the misleading subject line, I can pick that one
> up. The rest wants to go through the PCI tree.

That is what I meant. Thanks Thomas.

K. Y
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web