From: Andrea Bolognani <abologna@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, Laine Stump <laine@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Andrew Jones <drjones@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Daniel Berrange <berrange@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V2 RESEND] docs: add PCIe devices placement guidelines
Date: Mon, 17 Oct 2016 16:53:15 +0200 [thread overview]
Message-ID: <1476715995.3742.11.camel@redhat.com> (raw)
In-Reply-To: <fcd1a6f0-1159-1039-9aad-436312257539@redhat.com>
On Mon, 2016-10-17 at 16:26 +0200, Laszlo Ersek wrote:
> > > > +2.1 Root Bus (pcie.0)
> > > > +=====================
> > > > +Place only the following kinds of devices directly on the Root Complex:
> > > > + (1) Devices with dedicated, specific functionality (network card,
> > > > + graphics card, IDE controller, etc); place only legacy PCI devices on
> > > > + the Root Complex. These will be considered Integrated Endpoints.
> > > > + Note: Integrated devices are not hot-pluggable.
> >
> > s/Integrated devices/Integrated Endpoints/ (which I assume
> > is a Spec-Originated Term) in the last sentence, to be
> > consistent with the one right before it.
> >
> > I'm also not sure what you mean by devices with "dedicated,
> > specific functionality", and unfortunately the examples don't
> > seem to be helping me.
>
> That language is from me (I suggested it earlier). It means devices that
> you want to use for some actual task, rather than just to build your PCI
> (Express) hierarchy with them. "Leaf nodes" or whatever. "Everything
> non-bridge".
Isn't that basically the definition of Endpoint? It certainly
is what I convinced myself "Endpoint" means :)
Either way, I think we should spend a few more words there,
for clarity's sake. Rewording the phrase to put more emphasis
on the "legacy PCI devices only" part would probably be
warranted as well.
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2016-10-17 14:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 13:52 [Qemu-devel] [PATCH V2 RESEND] docs: add PCIe devices placement guidelines Marcel Apfelbaum
2016-10-13 14:05 ` Marcel Apfelbaum
2016-10-14 11:36 ` Laszlo Ersek
2016-10-17 12:07 ` Gerd Hoffmann
2016-10-17 14:07 ` Laszlo Ersek
2016-10-27 11:28 ` Marcel Apfelbaum
2016-10-27 11:27 ` Marcel Apfelbaum
2016-10-27 15:44 ` Laszlo Ersek
2016-10-27 18:06 ` Marcel Apfelbaum
2016-10-17 14:18 ` Andrea Bolognani
2016-10-17 14:26 ` Laszlo Ersek
2016-10-17 14:53 ` Andrea Bolognani [this message]
2016-10-27 14:36 ` Marcel Apfelbaum
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=1476715995.3742.11.camel@redhat.com \
--to=abologna@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=drjones@redhat.com \
--cc=kraxel@redhat.com \
--cc=laine@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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.