qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Cc: kraxel@redhat.com, laine@redhat.com, drjones@redhat.com,
	abologna@redhat.com, alex.williamson@redhat.com,
	berrange@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V3] docs: add PCIe devices placement guidelines
Date: Mon, 31 Oct 2016 16:41:06 +0100	[thread overview]
Message-ID: <4073c546-ec33-806c-55c0-58dedc4df997@redhat.com> (raw)
In-Reply-To: <1477925211-24768-1-git-send-email-marcel@redhat.com>

On 10/31/16 15:46, Marcel Apfelbaum wrote:
> Proposes best practices on how to use PCI Express/PCI device
> in PCI Express based machines and explain the reasoning behind them.
> 
> Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
> ---
> 
> Hi,
> 
> v2->v3:
>  - Addressed the comments from Andrea Bolognani and Laszlo Ersek, which are
>    much appreciated!
>  - Added links to presentations that may help the understanding of the document.

[snip]

> +2.1.1 To plug a device into a pcie.0 as a Root Complex Integrated Endpoint use:

The typo still isn't entirely fixed (it still says "into a pcie.0"), but
I don't think it justifies another repost in itself.

There's another instance of this typo in the document, so if you do
repost, please fix that as well (section 2.3.1).

[snip]

> +2.2.1 Plugging a PCI Express device into a PCI Express Root Port:
> +          -device ioh3420,id=root_port1,slot=x[,chassis=y][,bus=pcie.0][,slot=y][,addr=z]  \
> +          -device <dev>,bus=root_port1
> +      Note that (slot, chassis) pair is mandatory and must be
> +      unique for each PCI Express Root Port.

Please remove "[,slot=y]"; it is no longer necessary. (The "slot=x"
device property has been promoted to mandatory in this version.)

[snip]

> +3. IO space issues
> +===================
> +The PCI Express Root Ports and PCI Express Downstream ports are seen by
> +Firmware/Guest OS as PCI-PCI Bridges. As required by the PCI spec, each
> +such Port should be reserved a 4K IO range for, even though only one
> +(multifunction) device can be plugged into each Port. This results in
> +poor IO space utilization.
> +
> +The firmware used by QEMU (SeaBIOS/OVMF) may try further optimizations
> +by not allocating IO space or each PCI Express Root / PCI Express

s/IO space *or* each/IO space *for* each/

With those changes:

Reviewed-by: Laszlo Ersek <lersek@redhat.com>

Thank you, Marcel!
Laszlo

      reply	other threads:[~2016-10-31 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 14:46 [Qemu-devel] [PATCH V3] docs: add PCIe devices placement guidelines Marcel Apfelbaum
2016-10-31 15:41 ` Laszlo Ersek [this message]

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=4073c546-ec33-806c-55c0-58dedc4df997@redhat.com \
    --to=lersek@redhat.com \
    --cc=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=marcel@redhat.com \
    --cc=mst@redhat.com \
    --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).