From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Dan Smith <danms@us.ibm.com>,
Xen-devel <xen-devel@lists.xensource.com>,
Ewan Mellor <ewan@xensource.com>
Subject: Re: xm-test domain creation delay
Date: Mon, 14 Nov 2005 21:05:36 -0600 [thread overview]
Message-ID: <43795080.8000304@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E9AD@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
> > > Right, which is why I asked if this sort of thing would be
>
>
>>needed in a
>>
>>
>>>generic sense.
>>>
>>>
>>Yes, it would be nice for more general cases, but that of
>>course means controlling the guest environment, and that
>>would mean more interaction with distro-specific aspects than
>>I personally would like to take on at the moment.
>>It's not scary when we're doing it for xm-test, because we do
>>control that environment, but doing it for general guests is
>>more fiddly. However, I'm sure somebody somewhere will want
>>to know when the guest is actually booted, as opposed to
>>merely started, and writing to xenstore seems like a good way
>>to go about it.
>>
>>
>
>It's arguable that having a irtual filesystem inplemented in the kernel
>for accessing xenstore would be good.
>
2.6.14 now has FUSE which allows for virtual filesystems to be
implemented in userspace.
Regards,
Anthony Liguori
>Ideally, it would need to support
>mkdir and creating new files which is slightly tricky. Allowing
>read/write of existing nodes should be straightforward building on sys
>or proc.
>
>Ian
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
>
next prev parent reply other threads:[~2005-11-15 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 16:58 xm-test domain creation delay Ian Pratt
2005-11-15 3:05 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-14 15:48 Ewan Mellor
2005-11-14 16:00 ` Dan Smith
2005-11-14 16:10 ` Ewan Mellor
2005-11-14 16:26 ` Sean Dague
2005-11-14 16:28 ` Dan Smith
2005-11-14 16:41 ` Ewan Mellor
2005-11-14 16:38 ` Nivedita Singhvi
2005-11-14 16:43 ` Nivedita Singhvi
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=43795080.8000304@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=danms@us.ibm.com \
--cc=ewan@xensource.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.