All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, pbonzini@redhat.com, jan.kiszka@web.de,
	rkrcmar@redhat.com
Subject: Re: [Qemu-devel] [PATCH] pci: fix requester id to be the one on root bus
Date: Thu, 12 May 2016 12:43:06 +0800	[thread overview]
Message-ID: <20160512044306.GA4678@pxdev.xzpeter.org> (raw)
In-Reply-To: <20160511212203.6affa0b5@t450s.home>

On Wed, May 11, 2016 at 09:22:03PM -0600, Alex Williamson wrote:
[...]
> PCI Express to PCI/PCI-X Bridge Specification rev 1.0
> 2.3 Assignment of Requester ID and Tag by the Bridge
> 
> PCIe-to-PCI bridges assign a requester ID composed of the secondary bus
> number with devfn = 0.  Although often on real hardware, the root
> complex PCI bridge uses the actual bridge requester ID even though
> it's actually a PCIe bridge.  Linux assume that if a bridge has a PCIe
> capability with type PCIe-to-PCI/X bridge we use the secondary bus
> requester ID, if it has a PCIe capability with type PCI/X-to-PCIe, we
> use the bridge requester ID.  If it does not have a PCIe capability we
> use the bridge ID except for a few quirked devices known to use the
> secondary bus ID.  Yay standards!  Thanks,

Thanks Alex!

I have found pci and pci-to-pci bridge specs, which seems useful to
me.  However, I still cannot find pcie-to-pci bridge spec online (as
you have mentioned above).  Is that only for registered users?

-- peterx

  reply	other threads:[~2016-05-12  4:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11  6:40 [Qemu-devel] [PATCH] pci: fix requester id with PCI bridges Peter Xu
2016-05-11  6:40 ` [Qemu-devel] [PATCH] pci: fix requester id to be the one on root bus Peter Xu
2016-05-11 13:53   ` Michael S. Tsirkin
2016-05-12  2:40     ` Peter Xu
2016-05-12  3:22       ` Alex Williamson
2016-05-12  4:43         ` Peter Xu [this message]
2016-05-11  6:53 ` [Qemu-devel] [PATCH] pci: fix requester id with PCI bridges Peter Xu
2016-05-12  7:11   ` Michael S. Tsirkin
2016-05-12  7:32     ` Peter Xu
2016-05-12  7:51       ` Michael S. Tsirkin
2016-05-16  7:23         ` Peter Xu

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=20160512044306.GA4678@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkrcmar@redhat.com \
    /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.