All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 0/5] xend: Notify xend of udev hardware events
Date: Fri, 13 Mar 2009 21:45:52 +0800	[thread overview]
Message-ID: <49BA6390.1050907@oracle.com> (raw)
In-Reply-To: <49BA4C20.8020403@ab.jp.nec.com>

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

  reply	other threads:[~2009-03-13 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 12:05 [PATCH 0/5] xend: Notify xend of udev hardware events Yosuke Iwamatsu
2009-03-13 13:45 ` Zhigang Wang [this message]
2009-03-16  5:31   ` Yosuke Iwamatsu

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=49BA6390.1050907@oracle.com \
    --to=zhigang.x.wang@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=y-iwamatsu@ab.jp.nec.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.