linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Jason Baron <jbaron@redhat.com>,
	bhelgaas@google.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH] pci hotplug: rescan bridge after device hotplug
Date: Wed, 23 May 2012 22:13:07 +0300	[thread overview]
Message-ID: <20120523191307.GE32207@redhat.com> (raw)
In-Reply-To: <CAE9FiQV4hgUGqAz3jhRrjJyEGrV-=K=LwRhr7zePncKirajoSw@mail.gmail.com>

On Tue, May 22, 2012 at 08:31:30PM -0700, Yinghai Lu wrote:
> but pciehp we could do that, because it will only have one device
> under that pcie root port or downstream port.
> 
> so you can make qemu to support pcie and pciehp.

This does not solve the problem I think because
there are still multiple devices behind an upstream port.

Also, swiching to pcie creates a host of other complexities
so we want to support pci bridges too.

-- 
MST

  parent reply	other threads:[~2012-05-23 19:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 20:11 [PATCH] pci hotplug: rescan bridge after device hotplug Jason Baron
2012-05-22 20:34 ` Yinghai Lu
2012-05-22 21:18   ` Yinghai Lu
2012-05-22 21:21 ` Yinghai Lu
2012-05-23  2:43   ` Jason Baron
2012-05-23  3:31     ` Yinghai Lu
2012-05-23  4:07       ` Yinghai Lu
2012-05-23 15:53         ` Jason Baron
2012-05-23 17:16           ` Yinghai Lu
2012-05-23 18:44             ` Jason Baron
2012-05-23 19:08               ` Michael S. Tsirkin
2012-05-23 19:20                 ` Michael S. Tsirkin
2012-05-23 20:53                 ` Yinghai Lu
2012-05-23 21:18                   ` Michael S. Tsirkin
2012-05-23 20:31               ` Yinghai Lu
2012-05-23 20:49                 ` Michael S. Tsirkin
2012-05-23 19:13       ` Michael S. Tsirkin [this message]
2012-05-23 20:52       ` Jason Baron
2012-05-24  0:00         ` Yinghai Lu
2012-05-24 13:43           ` Jason Baron

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=20120523191307.GE32207@redhat.com \
    --to=mst@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=jbaron@redhat.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=yinghai@kernel.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).