PCI mini-summit

3 messages, 3 authors, 2012-07-26 · open the first message on its own page

PCI mini-summit

From: bhelgaas@google.com (Bjorn Helgaas)
Date: 2012-07-25 03:33:32

We're planning a PCI mini-summit on Tuesday, August 28, in San Diego.
If you'd like an invitation, let me know.

We haven't drafted an agenda yet, but based on ideas we've heard so
far, we'll likely talk about some of the following topics:

      Host bridge hotplug
      PCI hotplug core rework
      VFIO v2 for KVM
      Dynamic resource assignment
      SRIOV
          Management: driver (module parms) vs core (sysfs?)
          Dynamic/static: changing number of VFs requires driver cooperation
      Candidates for unification/moving from arch code to the core:
          res->parent usage
          Claiming resources
          Unassigned BAR detection
          ECAM (a.k.a. MMCONFIG)
          Domain (a.k.a. PCI segment) support
          MPS config
          MPS safety with respect to hotplug

I've also heard that PCI-on-ARM may be of interest, so if you want to
talk about that and possibly add some topics, let me know.

Bjorn

PCI mini-summit

From: Jiang Liu <hidden>
Date: 2012-07-26 01:40:53

Hi Bjorn,
	Really want to attend the mini-summit, have strong interests in host 
bridge hotplug and PCI hotplug core rework. But it may be a little later
for me to apply for VISA:(
	I'll try to send out a draft version for PCI hotplug rework for
comments soon.

	Thanks!
	Gerry

On 07/25/2012 11:33 AM, Bjorn Helgaas wrote:
We're planning a PCI mini-summit on Tuesday, August 28, in San Diego.
If you'd like an invitation, let me know.

We haven't drafted an agenda yet, but based on ideas we've heard so
far, we'll likely talk about some of the following topics:

      Host bridge hotplug
      PCI hotplug core rework
      VFIO v2 for KVM
      Dynamic resource assignment
      SRIOV
          Management: driver (module parms) vs core (sysfs?)
          Dynamic/static: changing number of VFs requires driver cooperation
      Candidates for unification/moving from arch code to the core:
          res->parent usage
          Claiming resources
          Unassigned BAR detection
          ECAM (a.k.a. MMCONFIG)
          Domain (a.k.a. PCI segment) support
          MPS config
          MPS safety with respect to hotplug

I've also heard that PCI-on-ARM may be of interest, so if you want to
talk about that and possibly add some topics, let me know.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

PCI mini-summit

From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
Date: 2012-07-26 21:45:21

On Tue, 2012-07-24 at 21:33 -0600, Bjorn Helgaas wrote:
We're planning a PCI mini-summit on Tuesday, August 28, in San Diego.
If you'd like an invitation, let me know.

We haven't drafted an agenda yet, but based on ideas we've heard so
far, we'll likely talk about some of the following topics:

      Host bridge hotplug
      PCI hotplug core rework
      VFIO v2 for KVM
      Dynamic resource assignment
      SRIOV
          Management: driver (module parms) vs core (sysfs?)
          Dynamic/static: changing number of VFs requires driver cooperation
      Candidates for unification/moving from arch code to the core:
          res->parent usage
          Claiming resources
          Unassigned BAR detection
          ECAM (a.k.a. MMCONFIG)
          Domain (a.k.a. PCI segment) support
          MPS config
          MPS safety with respect to hotplug

I've also heard that PCI-on-ARM may be of interest, so if you want to
talk about that and possibly add some topics, let me know.
We don't necessarily need a firm agenda, we can put the list of topics
and pick them in time with a hourly stop to decide whether to move on to
a different one.

Unless some people want to actually present something in which case we
can allocate them a slot (those people need to let us know asap).

Cheers,
Ben.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help