All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>,
	blauwirbel@gmail.com,
	Alex Williamson <alex.williamson@redhat.com>,
	Amos Kong <akong@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] About hotplug multifunction
Date: Tue, 13 Sep 2011 13:05:19 +0300	[thread overview]
Message-ID: <20110913100519.GO21417@redhat.com> (raw)
In-Reply-To: <20110913100500.GB29872@redhat.com>

On Tue, Sep 13, 2011 at 01:05:00PM +0300, Michael S. Tsirkin wrote:
> On Tue, Sep 13, 2011 at 09:52:49AM +0300, Gleb Natapov wrote:
> > On Tue, Sep 13, 2011 at 02:57:20PM +0900, Isaku Yamahata wrote:
> > > On Sun, Sep 11, 2011 at 12:05:17PM +0300, Michael S. Tsirkin wrote:
> > > > On Sat, Sep 10, 2011 at 02:43:11AM +0900, Isaku Yamahata wrote:
> > > > > pci/pcie hot plug needs clean up for multifunction hotplug in long term.
> > > > > Only single function device case works. Multifunction case is broken somwehat.
> > > > > Especially the current acpi based hotplug should be replaced by
> > > > > the standardized hot plug controller in long term.
> > > > 
> > > > We'll need to keep supporting windows XP, which IIUC only
> > > > supports hotplug through ACPI. So it looks like we'll
> > > > need both.
> > > 
> > > Yes, we'll need both then.
> > > It would be possible to implement acpi-based hotplug with
> > > standardized hotplug controller. Not with qemu-specific controller.
> > > 
> > Where is this "standardized hotplug controller" documented?
> 
> Sorry both pci bridge and hotplug spec only reference shpc.
> The spec itself is PCI Standard Hot-Plug
> Controller and Subsystem Specification.
> 
> Revision 1.0 - get it from pcisig
> 
Thanks, Isaku is already pointed it to me.

--
			Gleb.

WARNING: multiple messages have this Message-ID (diff)
From: Gleb Natapov <gleb@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, blauwirbel@gmail.com,
	Isaku Yamahata <yamahata@valinux.co.jp>,
	Alex Williamson <alex.williamson@redhat.com>,
	Amos Kong <akong@redhat.com>
Subject: Re: [Qemu-devel] About hotplug multifunction
Date: Tue, 13 Sep 2011 13:05:19 +0300	[thread overview]
Message-ID: <20110913100519.GO21417@redhat.com> (raw)
In-Reply-To: <20110913100500.GB29872@redhat.com>

On Tue, Sep 13, 2011 at 01:05:00PM +0300, Michael S. Tsirkin wrote:
> On Tue, Sep 13, 2011 at 09:52:49AM +0300, Gleb Natapov wrote:
> > On Tue, Sep 13, 2011 at 02:57:20PM +0900, Isaku Yamahata wrote:
> > > On Sun, Sep 11, 2011 at 12:05:17PM +0300, Michael S. Tsirkin wrote:
> > > > On Sat, Sep 10, 2011 at 02:43:11AM +0900, Isaku Yamahata wrote:
> > > > > pci/pcie hot plug needs clean up for multifunction hotplug in long term.
> > > > > Only single function device case works. Multifunction case is broken somwehat.
> > > > > Especially the current acpi based hotplug should be replaced by
> > > > > the standardized hot plug controller in long term.
> > > > 
> > > > We'll need to keep supporting windows XP, which IIUC only
> > > > supports hotplug through ACPI. So it looks like we'll
> > > > need both.
> > > 
> > > Yes, we'll need both then.
> > > It would be possible to implement acpi-based hotplug with
> > > standardized hotplug controller. Not with qemu-specific controller.
> > > 
> > Where is this "standardized hotplug controller" documented?
> 
> Sorry both pci bridge and hotplug spec only reference shpc.
> The spec itself is PCI Standard Hot-Plug
> Controller and Subsystem Specification.
> 
> Revision 1.0 - get it from pcisig
> 
Thanks, Isaku is already pointed it to me.

--
			Gleb.

  reply	other threads:[~2011-09-13 10:05 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1749303074.590739.1315551830460.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2011-09-09  7:08 ` About hotplug multifunction Amos Kong
2011-09-09  7:08   ` [Qemu-devel] " Amos Kong
2011-09-09  7:32   ` Michael S. Tsirkin
2011-09-09  7:32     ` [Qemu-devel] " Michael S. Tsirkin
2011-09-09 17:05     ` Alex Williamson
2011-09-09 17:05       ` [Qemu-devel] " Alex Williamson
2011-09-09 18:34       ` Marcelo Tosatti
2011-09-09 18:34         ` [Qemu-devel] " Marcelo Tosatti
2011-09-11  9:23         ` Michael S. Tsirkin
2011-09-11  9:23           ` [Qemu-devel] " Michael S. Tsirkin
2011-09-11 15:01           ` Marcelo Tosatti
2011-09-11 15:01             ` [Qemu-devel] " Marcelo Tosatti
2011-09-11 18:51             ` Michael S. Tsirkin
2011-09-11 18:51               ` [Qemu-devel] " Michael S. Tsirkin
2011-09-12 10:21               ` Marcelo Tosatti
2011-09-12 10:21                 ` [Qemu-devel] " Marcelo Tosatti
2011-09-12 10:56                 ` Marcelo Tosatti
2011-09-12 10:56                   ` [Qemu-devel] " Marcelo Tosatti
2011-09-12 12:24                   ` Michael S. Tsirkin
2011-09-12 12:24                     ` [Qemu-devel] " Michael S. Tsirkin
2011-09-13 12:23                     ` Amos Kong
2011-09-13 12:23                       ` [Qemu-devel] " Amos Kong
2011-09-13 14:24                       ` Amos Kong
2011-09-13 14:24                         ` [Qemu-devel] " Amos Kong
2011-09-09 17:43   ` Isaku Yamahata
2011-09-09 17:43     ` [Qemu-devel] " Isaku Yamahata
2011-09-11  9:05     ` Michael S. Tsirkin
2011-09-11  9:05       ` [Qemu-devel] " Michael S. Tsirkin
2011-09-13  5:57       ` Isaku Yamahata
2011-09-13  5:57         ` [Qemu-devel] " Isaku Yamahata
2011-09-13  6:52         ` Gleb Natapov
2011-09-13  6:52           ` Gleb Natapov
2011-09-13  7:00           ` Isaku Yamahata
2011-09-13  7:00             ` Isaku Yamahata
2011-09-13 10:00           ` Michael S. Tsirkin
2011-09-13 10:00             ` Michael S. Tsirkin
2011-09-13 10:05           ` Michael S. Tsirkin
2011-09-13 10:05             ` Michael S. Tsirkin
2011-09-13 10:05             ` Gleb Natapov [this message]
2011-09-13 10:05               ` Gleb Natapov
2011-11-23  9:06   ` Amos Kong
2011-11-23  9:06     ` [Qemu-devel] " Amos Kong

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=20110913100519.GO21417@redhat.com \
    --to=gleb@redhat.com \
    --cc=akong@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /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.