All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Jeremy Katz <katzj@redhat.com>,
	Xen Mailing List <xen-devel@lists.sourceforge.net>
Subject: Re: Proposal for init/kexec/hotplug format for Xen
Date: Sun, 27 Feb 2005 09:25:42 -0600	[thread overview]
Message-ID: <4221E676.5000008@us.ibm.com> (raw)
In-Reply-To: <68d3daa4e95f4ba6740c6c0ffd3f67b8@cl.cam.ac.uk>

Keir Fraser wrote:

>>     For kexec and bare-metal bringup, the PPC64 port uses a fairly 
>> simple
>> header + flattened tree of keyword/value pairs (on PPC64, used to hold
>> the Open Firmware tree plus Linux extras).  This offers flexibility for
>> new virtual devices, etc; I propose that we adopt this format or
>> something very similar for Xen, first by putting a pointer into it in
>> start_info_t, and then migrate entries across as appropriate.
>
>
> I like the idea of bringing out device discovery, bringup, teardown, 
> recovery all into its own driver or subsystem -- it seems the obvious 
> way to go. But I think the 'device tree' should be in the 
> to-be-designed persistent store, and we publish an interface to allow 
> guests to peek/poke that store.

I think publishing domain-information in an OF-like tree would be great.

I think we want the persistent store to be outside the OF-tree though.  
It would provide a good buffer against ill-written management apps.

The way I envision this working is to have a persistent store in 
user-space on a priviledged domain that exported within it's tree the OF 
device-tree.  This way management app information (the domain's name, an 
icon associated with it, etc.) would not be stored in the OF tree.  If 
you needed to blow away a portion of the store because of an misbehaving 
management app you do not lose any of the vital device information.

Does PPC64 or rHype provide a mechanism to notify user-space daemons 
when a value in the tree changes?

I think this is a great proposal.

Regards,
Anthony Liguori

>  -- Keir
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  parent reply	other threads:[~2005-02-27 15:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26 20:57 Proposal for init/kexec/hotplug format for Xen Rusty Russell
2005-02-27 10:53 ` Keir Fraser
2005-02-27 11:46   ` Rusty Russell
2005-02-27 15:25   ` Anthony Liguori [this message]
2005-02-27 15:48     ` Keir Fraser
2005-02-27 15:54       ` Anthony Liguori
2005-02-27 16:09         ` Keir Fraser
2005-02-27 16:16           ` Anthony Liguori
2005-02-27 16:31             ` Harry Butterworth
2005-02-27 16:42               ` Anthony Liguori
2005-02-27 17:32                 ` Keir Fraser
2005-02-27 17:59                   ` Anthony Liguori
2005-02-27 18:12                 ` Harry Butterworth
2005-02-27 18:24                   ` Anthony Liguori
2005-02-27 18:55                     ` Harry Butterworth
2005-02-27 18:57                       ` Keir Fraser
2005-02-27 19:10                         ` Anthony Liguori
2005-02-27 21:49                           ` Keir Fraser
2005-02-27 22:39                             ` Anthony Liguori
2005-02-27 23:29                               ` Harry Butterworth
2005-02-28  8:59                               ` Keir Fraser
2005-02-27 19:38                         ` Harry Butterworth
2005-02-27 16:05     ` Harry Butterworth
2005-02-28 12:06     ` Rusty Russell
2005-02-28 15:46       ` Anthony Liguori
2005-02-28 20:28       ` Jeremy Katz
2005-02-28 22:24         ` Harry Butterworth
  -- strict thread matches above, loose matches on Subject: below --
2005-02-28 13:08 Re: " harry
2005-02-28 13:32 ` Rusty Russell
2005-02-28 13:40   ` Harry Butterworth
2005-02-28 14:33     ` Keir Fraser
2005-02-28 16:46     ` Re: " Rusty Russell
2005-03-01 13:15       ` Harry Butterworth
2005-03-01 15:08         ` Keir Fraser

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=4221E676.5000008@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=katzj@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=xen-devel@lists.sourceforge.net \
    /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.