From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 7/7] pcie: Mangle types to match topology
Date: Sun, 17 Mar 2013 14:19:08 +0200 [thread overview]
Message-ID: <20130317121908.GA22279@redhat.com> (raw)
In-Reply-To: <20130314220135.10566.6582.stgit@bling.home>
On Thu, Mar 14, 2013 at 04:01:35PM -0600, Alex Williamson wrote:
> Windows will fail to start drivers for devices with an Endpoint type
> PCIe capability attached to a Root Complex (code 10 - Device cannot
> start). The proper type for such a device is Root Complex Integrated
> Endpoint. Devices don't care which they are, so do this conversion
> automatically.
>
> This allows the Windows driver to load for nec-usb-xhci when attached
> to pcie.0 of a q35 machine.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
I think it's a bit ugly from the API perspective,
in that an integrated endpoint is not converted to a regular one.
I think it would be cleaner to have pcie_cap_init do exactly
what it's told to do, maybe failing if you give it an
incorrect configuration. On top of this add
pcie_endpoint_cap_init which sets the type explicitly.
Hmm?
Not critical, so applied as is for now.
> ---
> hw/pci/pcie.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
> index 485c94c..bcfbae4 100644
> --- a/hw/pci/pcie.c
> +++ b/hw/pci/pcie.c
> @@ -48,6 +48,19 @@ int pcie_cap_init(PCIDevice *dev, uint8_t offset, uint8_t type, uint8_t port)
>
> assert(pci_is_express(dev));
>
> + /*
> + * Mangle type to convert Endpoints to Root Complex Integrated Endpoints.
> + * Windows will report Code 10 (device cannot start) for regular Endpoints
> + * on the Root Complex.
> + */
> + if (pci_bus_is_express(dev->bus) && pci_bus_is_root(dev->bus)) {
> + switch (type) {
> + case PCI_EXP_TYPE_ENDPOINT:
> + type = PCI_EXP_TYPE_RC_END;
> + break;
> + }
> + }
> +
> pos = pci_add_capability(dev, PCI_CAP_ID_EXP, offset,
> PCI_EXP_VER2_SIZEOF);
> if (pos < 0) {
next prev parent reply other threads:[~2013-03-17 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 22:00 [Qemu-devel] [PATCH 0/7] pci: Create PCI Express bus type Alex Williamson
2013-03-14 22:00 ` [Qemu-devel] [PATCH 1/7] pci: Create and register a new PCI Express TypeInfo Alex Williamson
2013-03-14 22:01 ` [Qemu-devel] [PATCH 2/7] pci: Move PCI and PCIE type defines Alex Williamson
2013-03-14 22:01 ` [Qemu-devel] [PATCH 3/7] pci: Allow PCI bus creation interfaces to specify the type of bus Alex Williamson
2013-03-14 22:01 ` [Qemu-devel] [PATCH 4/7] pci: Q35, Root Ports, and Switches create PCI Express buses Alex Williamson
2013-03-14 22:01 ` [Qemu-devel] [PATCH 5/7] pci: Create pci_bus_is_express helper Alex Williamson
2013-03-14 22:01 ` [Qemu-devel] [PATCH 6/7] pci: Create and use API to determine root buses Alex Williamson
2013-03-14 22:01 ` [Qemu-devel] [PATCH 7/7] pcie: Mangle types to match topology Alex Williamson
2013-03-17 12:19 ` Michael S. Tsirkin [this message]
2013-03-18 21:17 ` Alex Williamson
2013-03-17 12:19 ` [Qemu-devel] [PATCH 0/7] pci: Create PCI Express bus type Michael S. Tsirkin
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=20130317121908.GA22279@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@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).