All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xen.org
Subject: Re: Xen 4.2 and PCI hotplug.
Date: Wed, 19 Dec 2012 14:36:24 +0000	[thread overview]
Message-ID: <50D1D0E8.7050203@citrix.com> (raw)
In-Reply-To: <B6C2EB9186482D47BD0C5A9A48345644033BA621@SHSMSX101.ccr.corp.intel.com>

On 19/12/2012 09:14, Zhang, Xiantao wrote:
>> -----Original Message-----
>> From: Jan Beulich [mailto:JBeulich@suse.com]
>> Sent: Wednesday, December 19, 2012 4:48 PM
>> To: Zhang, Xiantao
>> Cc: Konrad Rzeszutek Wilk; xen-devel
>> Subject: Re: [Xen-devel] Xen 4.2 and PCI hotplug.
>>
>>>>> On 19.12.12 at 09:13, "Zhang, Xiantao" <xiantao.zhang@intel.com>
>> wrote:
>>> Are you playing with Xen ?  so far,  Xen doesn't support PCIe device
>>> hot-plug feature yet.
>> When saying Xen, I assume you mean the pv-ops kernel instead? So far I was
>> under the impression that this worked even with the very old 2.6.18 tree (as
>> much or as little as hotplug there worked in the native case). And given that
>> there are no special requirements on the hypervisor to make this work, it's
>> not even obvious to me what would be missing in the pv-ops kernel to make
>> it work. 
> Oh, my fault!  Perhaps we don't need to do anything for pv-ops kernel to support device hot-plug if native system has it supported.  Actually, we didn't do such testings before, since it is a native feature, not a Xen-specific one. 
> Xiantao

My current understanding is that on boot, Xen scans the PCI bus, then
dom0 rescans it later.  If a hotplug event gets serviced by dom0, does
there not need to be some hypercall informing Xen that a new device has
appeared?  I expect PCIPassthrough would not work correctly on a
hotplugged device which Xen is unaware of.

(But if I have got the wrong end of the stick, or this mechanism already
exist, please ignore me.  It just strikes me as a little xen-specific,
even if the bulk of it is native)

~Andrew

>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2012-12-19 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 22:46 Xen 4.2 and PCI hotplug Konrad Rzeszutek Wilk
2012-12-19  8:13 ` Zhang, Xiantao
2012-12-19  8:47   ` Jan Beulich
2012-12-19  9:14     ` Zhang, Xiantao
2012-12-19 14:36       ` Andrew Cooper [this message]
2012-12-19 15:08         ` Jan Beulich
2012-12-21 21:13           ` Konrad Rzeszutek Wilk
2012-12-21 21:09     ` Konrad Rzeszutek Wilk

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=50D1D0E8.7050203@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.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 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.