From: ZhouPeng <zpengxen@gmail.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
"Xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jiageng Yu <yujiageng734@gmail.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] libxl: Support linux-stubdom in libxl
Date: Mon, 6 Jun 2011 19:56:52 +0800 [thread overview]
Message-ID: <BANLkTinEfnw2ysYWB9jBQsmQrBxuF-NUPA@mail.gmail.com> (raw)
In-Reply-To: <1307025357.775.277.camel@zakaz.uk.xensource.com>
I think class is better than mode?
'Mode' is somewhat misleading to new newbie?
It seem be telling there is one device model instance, which has
mutiple working mode.
Just like kernel mode or user mode to describe one OS‘s current working mode.
1) device_model_class
2) device_model_deployment
3) device_model_instance
4) device_model_mode
If I have one vote for all the above chances, I will select '...class' :)
And I suggest one :
device_modele_mechanism
:)
2011/6/2 Ian Campbell <Ian.Campbell@eu.citrix.com>:
> On Thu, 2011-06-02 at 15:31 +0100, Stefano Stabellini wrote:
>> On Thu, 2 Jun 2011, Ian Campbell wrote:
>> > On Thu, 2011-06-02 at 14:40 +0100, Jiageng Yu wrote:
>> > > diff -r 37c77bacb52a tools/libxl/libxl.idl
>> > > --- a/tools/libxl/libxl.idl Mon May 23 17:38:28 2011 +0100
>> > > +++ b/tools/libxl/libxl.idl Wed Jun 01 03:24:57 2011 +0100
>> > > @@ -196,6 +196,7 @@
>> > > ("dom_name", string),
>> > > ("device_model_version", libxl_device_model_version),
>> > > ("device_model_stubdomain", bool),
>> > > + ("device_model_linux_stubdomain", bool),
>> > > ("device_model", string, False, "if you set this you must set device_model_version too"),
>> > > ("saved_state", string),
>> > > ("type", libxl_domain_type),
>> >
>> > I think what we actually want here is a single device_model_type
>> > Enumeration, values are something like "process", "stub-linux",
>> > "stub-minios", rather than multiple device_model_XXX_stubdom booleans.
>>
>> indeed
>>
>>
>> > I'm not convinced device_model_type is a good name, hopefully someone
>> > can suggest something better. (device_model_mode??)
>>
>> some suggestions:
>>
>> 1) device_model_class
>> 2) device_model_deployment
>> 3) device_model_instance
>>
>> I vote for 3)
>
> I don't think deployment or instance has the right meaning here. class
> is better but still doesn't feel right.
>
> maybe ..._mode?
>
> </bikeshed>
>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Zhou Peng
Operating System Technology Group
Institute of Software, the Chinese Academy of Sciences (ISCAS)
prev parent reply other threads:[~2011-06-06 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 13:54 [PATCH] libxl: Support linux-stubdom in libxl Jiageng Yu
2011-05-31 14:38 ` Stefano Stabellini
2011-06-01 12:58 ` Ian Campbell
2011-06-02 13:40 ` Jiageng Yu
2011-06-02 14:25 ` Ian Campbell
2011-06-02 14:31 ` Stefano Stabellini
2011-06-02 14:35 ` Ian Campbell
2011-06-06 11:56 ` ZhouPeng [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=BANLkTinEfnw2ysYWB9jBQsmQrBxuF-NUPA@mail.gmail.com \
--to=zpengxen@gmail.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xensource.com \
--cc=yujiageng734@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).