From: Laszlo Ersek <lersek@redhat.com>
To: Kevin Locke <kevin@kevinlocke.name>, qemu-devel@nongnu.org
Cc: Marcel Apfelbaum <marcel@redhat.com>,
Laine Stump <laine@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [RFC][PATCH] docs: note exception for PCIe IO port access
Date: Thu, 9 Jun 2022 09:50:21 +0200 [thread overview]
Message-ID: <06171fb8-3a7e-81f3-12dd-b5332d99c1dd@redhat.com> (raw)
In-Reply-To: <63e991af-0dd2-3aea-2f15-7460a6fb87db@redhat.com>
On 06/09/22 09:45, Laszlo Ersek wrote:
> +Alex
>
> On 06/09/22 04:00, Kevin Locke wrote:
> *In theory*, scenario (b) applies to "bochs-display" and
> "virtio-gpu-pci" when you plug them into a legacy PCI slot:
>
>> Plugging a PCI Express device into a PCI slot will hide the Extended
>> Configuration Space thus is also not recommended.
>
> But this is fine, as these device models don't have extended
> capabilities in practice. IOW, I'd imagine them (if they were physical
> cards) as PCI Express devices without any use for their extended config
> spaces. You could plug them into legacy PCI slots, but would see no
> difference in behavior (apart from speed perhaps).
Ignore the part starting with "IOW", that seems like brain fart on my
part, apologies! :/
next prev parent reply other threads:[~2022-06-09 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 2:00 [RFC][PATCH] docs: note exception for PCIe IO port access Kevin Locke
2022-06-09 7:45 ` Laszlo Ersek
2022-06-09 7:50 ` Laszlo Ersek [this message]
2022-06-09 8:41 ` Gerd Hoffmann
2022-06-09 14:03 ` Kevin Locke
2022-06-10 7:00 ` Laszlo Ersek
2022-06-12 17:32 ` [PATCH v2] docs: add PCIe root bus for VGA compat guideline Kevin Locke
2022-06-13 13:47 ` Laszlo Ersek
2022-06-14 8:52 ` Gerd Hoffmann
2022-06-14 18:14 ` Kevin Locke
2022-06-15 6:42 ` Gerd Hoffmann
2022-06-15 20:05 ` Alex Williamson
2022-06-13 13:55 ` [PATCH v3] " Kevin Locke
2022-06-22 0:56 ` [PATCH v4] docs: mention devices with VBE on Root Complex Kevin Locke
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=06171fb8-3a7e-81f3-12dd-b5332d99c1dd@redhat.com \
--to=lersek@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=kevin@kevinlocke.name \
--cc=laine@redhat.com \
--cc=marcel@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).