From: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
To: zhigang.x.wang@oracle.com
Cc: xen-devel@lists.xensource.com
Subject: [PATCH 0/5] xend: Notify xend of udev hardware events
Date: Mon, 16 Mar 2009 14:31:01 +0900 [thread overview]
Message-ID: <49BDE415.7000805@ab.jp.nec.com> (raw)
In-Reply-To: <49BA6390.1050907@oracle.com>
Zhigang Wang wrote:
> 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?
XendMonitor is only used to fetch the usage statistics of some devices from
from procfs and is not suitable to monitor the configuration changes of
physical devices, I think. We may be able to implement in XendMonitor a
detection mechanism of physical device's hot-plugging by polling sysfs entries,
but that would take some amount of effort and I don't see any advantage to do it
instead of utilizing udev mechanism.
Thanks,
-- Yosuke
prev parent reply other threads:[~2009-03-16 5:31 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
2009-03-16 5:31 ` Yosuke Iwamatsu [this message]
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=49BDE415.7000805@ab.jp.nec.com \
--to=y-iwamatsu@ab.jp.nec.com \
--cc=xen-devel@lists.xensource.com \
--cc=zhigang.x.wang@oracle.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.