From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zhigang Wang Subject: Re: [PATCH 0/5] xend: Notify xend of udev hardware events Date: Fri, 13 Mar 2009 21:45:52 +0800 Message-ID: <49BA6390.1050907@oracle.com> References: <49BA4C20.8020403@ab.jp.nec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49BA4C20.8020403@ab.jp.nec.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Yosuke Iwamatsu Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Yosuke Iwamatsu wrote: > There are several xen-api classes that represent physical devices, > such as PIF, PPCI and PSCSI. At the initialization step, xend creates > instances of these classes and stores them, so as to later expose > the host's available physical resources to remote clients. > > The problem is that, when you hot-add of hot-remove a physical device > to of from the host, currently there is no way xend can detect that. > So the physical resource information kept in xend may become inconsistent > with the real state. > > This series of patches makes xend get notification of hardware changes > and update the physical resource information. Inside xend, we runs a thread > which opens a socket and listens to events of hardware configuration changes > from udev mechanism. > we already have XendMonitor to do that. Is it right to add these patches? > For now, these patches only support the configuration change of pci devices, > but it would be easy to add support for other types of physical devices > (e.g. net or scsi). > > Regards, > ----------------------- > Yosuke Iwamatsu > NEC Corporation > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel