All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	Andrew Jones <drjones@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Andrea Bolognani <abologna@redhat.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Laine Stump <laine@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V2 RESEND] docs: add PCIe devices placement guidelines
Date: Mon, 17 Oct 2016 14:07:36 +0200	[thread overview]
Message-ID: <1476706056.6417.11.camel@redhat.com> (raw)
In-Reply-To: <5880f354-9f1e-a9cf-9728-5ac5168ef9c9@redhat.com>

  Hi,

> {26} Another remark (important to me) in this section: the document
> doesn't state firmware expectations. It's clear the firmware is expected
> to reserve no IO space for PCI Express Downstream Ports and Root Ports,
> but what about MMIO?
> 
> We discussed this at length with Alex, but I think we didn't conclude
> anything. It would be nice if firmware received some instructions from
> this document in this regard, even before we implement our own ports and
> bridges in QEMU.

Where do we stand in terms of generic pcie ports btw?

I think the plan is still to communicate suggestions to the firmware via
pci config space, either by using reset defaults of the limit register,
or of that doesn't work due to initialization order issues using some
vendor specific pcie capability.

As long as we don't have that there is nothing do document, other than
maybe briefly mentioning the plans we have and documenting the current
state (2M mmio in seabios, and I think the same for ovmf).

The patches adding the generic ports can also update the documentation
of course.

> <digression>
> 
> If we think such recommendations are out of scope at this point, *and*
> noone disagrees strongly (Gerd?), then I could add some experimental
> fw_cfg knobs to OVMF for this, such as (units in MB):

Why?  Given that the virtio mmio bar size issue is solved I don't see a
strong reason to hurry with this.  Just wait until the generic ports are
there.

cheers,
  Gerd

  reply	other threads:[~2016-10-17 12:07 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 [this message]
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
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=1476706056.6417.11.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=abologna@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=drjones@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.