From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: PCI mini-summit
Date: Fri, 27 Jul 2012 07:45:21 +1000 [thread overview]
Message-ID: <1343339121.2118.5.camel@pasglop> (raw)
In-Reply-To: <CAErSpo5Ea_Rd2QSUXT13riDgHrkMGiN43+QiFTZYepHi-rg0Vw@mail.gmail.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: PCI mini-summit
Date: Fri, 27 Jul 2012 07:45:21 +1000 [thread overview]
Message-ID: <1343339121.2118.5.camel@pasglop> (raw)
In-Reply-To: <CAErSpo5Ea_Rd2QSUXT13riDgHrkMGiN43+QiFTZYepHi-rg0Vw@mail.gmail.com>
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.
next prev parent reply other threads:[~2012-07-26 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 3:33 PCI mini-summit Bjorn Helgaas
2012-07-25 3:33 ` Bjorn Helgaas
2012-07-26 1:40 ` Jiang Liu
2012-07-26 1:40 ` Jiang Liu
2012-07-26 21:45 ` Benjamin Herrenschmidt [this message]
2012-07-26 21:45 ` Benjamin Herrenschmidt
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=1343339121.2118.5.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.