From: Marcel Apfelbaum <marcel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Laszlo Ersek <lersek@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC] docs: add PCIe devices placement guidelines
Date: Thu, 1 Sep 2016 16:51:47 +0300 [thread overview]
Message-ID: <349c47f7-6fd8-2d6c-23da-c4fb188bb4a6@redhat.com> (raw)
In-Reply-To: <CAFEAcA8yJxCbGRj+eu7yqUc=9vMf9=L2ZhEcKeUZegWkKJY8wQ@mail.gmail.com>
On 09/01/2016 04:27 PM, Peter Maydell wrote:
> On 1 September 2016 at 14:22, Marcel Apfelbaum <marcel@redhat.com> wrote:
>> Proposes best practices on how to use PCIe/PCI device
>> in PCIe based machines and explain the reasoning behind them.
>>
>> Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
>> ---
>>
>> Hi,
>>
>> Please add your comments on what to add/remove/edit to make this doc usable.
>
Hi Peter,
> As somebody who doesn't really understand the problem space, my
> thoughts:
>
> (1) is this intended as advice for developers writing machine
> models and adding pci controllers to them, or is it intended as
> advice for users (and libvirt-style management layers) about
> how to configure QEMU?
>
Is it intended for management layers as they have no way to
understand how to "consume" the Q35 machine,
but also for firmware developers (OVMF/SeaBIOS) to help them
understand the usage model so they can optimize IO/MEM
resources allocation for both boot time and hot-plug.
QEMU users/developers can also benefit from it as the PCIe arch
is more complex supporting both PCI/PCIe devices and
several PCI/PCIe controllers with no clear rules on what goes where.
> (2) it seems to be a bit short on concrete advice (either
> "you should do this" instructions to machine model developers,
> or "use command lines like this" instructions to end-users.
>
Thanks for the point. I'll be sure to add detailed command line examples
to the next version.
Thanks,
Marcel
> thanks
> -- PMM
>
next prev parent reply other threads:[~2016-09-01 13:51 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 13:22 [Qemu-devel] [PATCH RFC] docs: add PCIe devices placement guidelines Marcel Apfelbaum
2016-09-01 13:27 ` Peter Maydell
2016-09-01 13:51 ` Marcel Apfelbaum [this message]
2016-09-01 17:14 ` Laszlo Ersek
2016-09-05 16:24 ` Laszlo Ersek
2016-09-05 20:02 ` Marcel Apfelbaum
2016-09-06 13:31 ` Laszlo Ersek
2016-09-06 14:46 ` Marcel Apfelbaum
2016-09-07 6:21 ` Gerd Hoffmann
2016-09-07 8:06 ` Laszlo Ersek
2016-09-07 8:23 ` Marcel Apfelbaum
2016-09-07 8:06 ` Marcel Apfelbaum
2016-09-07 16:08 ` Alex Williamson
2016-09-07 19:32 ` Marcel Apfelbaum
2016-09-07 17:55 ` Laine Stump
2016-09-07 19:39 ` Marcel Apfelbaum
2016-09-07 20:34 ` Laine Stump
2016-09-15 8:38 ` Andrew Jones
2016-09-15 14:20 ` Marcel Apfelbaum
2016-09-16 16:50 ` Andrea Bolognani
2016-09-08 7:33 ` Gerd Hoffmann
2016-09-06 11:35 ` Gerd Hoffmann
2016-09-06 13:58 ` Laine Stump
2016-09-07 7:04 ` Gerd Hoffmann
2016-09-07 18:20 ` Laine Stump
2016-09-08 7:26 ` Gerd Hoffmann
2016-09-06 14:47 ` Marcel Apfelbaum
2016-09-07 7:53 ` Laszlo Ersek
2016-09-07 7:57 ` Marcel Apfelbaum
2016-10-04 14:59 ` Daniel P. Berrange
2016-10-04 15:40 ` Laszlo Ersek
2016-10-04 16:10 ` Laine Stump
2016-10-04 16:43 ` Laszlo Ersek
2016-10-04 18:08 ` Laine Stump
2016-10-04 18:52 ` Alex Williamson
2016-10-10 12:02 ` Andrea Bolognani
2016-10-10 14:36 ` Marcel Apfelbaum
2016-10-11 15:37 ` Andrea Bolognani
2016-10-04 18:56 ` Laszlo Ersek
2016-10-04 17:54 ` Laine Stump
2016-10-05 9:17 ` Marcel Apfelbaum
2016-10-10 11:09 ` Andrea Bolognani
2016-10-10 14:15 ` Marcel Apfelbaum
2016-10-11 13:30 ` Andrea Bolognani
2016-10-04 15:45 ` Alex Williamson
2016-10-04 16:25 ` Laine Stump
2016-10-05 10:03 ` Marcel Apfelbaum
2016-09-06 15:38 ` Alex Williamson
2016-09-06 18:14 ` Marcel Apfelbaum
2016-09-06 18:32 ` Alex Williamson
2016-09-06 18:59 ` Marcel Apfelbaum
2016-09-07 7:44 ` Laszlo Ersek
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=349c47f7-6fd8-2d6c-23da-c4fb188bb4a6@redhat.com \
--to=marcel@redhat.com \
--cc=lersek@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 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).