From: Hollis Blanchard <hollisb@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: "Magenheimer,
Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: Xen/ia64 presentation
Date: Wed, 27 Apr 2005 14:31:16 -0500 [thread overview]
Message-ID: <426FE884.2010904@us.ibm.com> (raw)
In-Reply-To: <fc7f187f35a21cfa7933a2b66afbd7b6@cl.cam.ac.uk>
Keir Fraser wrote:
>
> I think I agree that 'struct vcpu' is nicer than 'struct exec_domain'.
> exec_domain appears hardly at all at the hypervisor interface, and
> having two different terms used interchangeably within Xen itself is weird.
>
> Another I can think of is cpuset vs. cpumask: I went with the former but
> I like the latter equally well and there is no good reason not to go
> with the Linux convention on this one.
>
> Perhaps we should have a flag day to move to agreed consistent naming on
> some of these? The changes are trivially scriptable for the most part,
> but annoying for those with pending patches.
Sounds good to me.
On this subject, I'd also like to ask about full_execution_context_t.
execution_context_t is used in a fair number of places in the Xen core;
however full_execution_context_t seems to only be used in the dom0
interface.
The in-Xen analog to full_execution_context_t is arch_exec_domain, with
many fields duplicated between the two. Could we consolidate these, or
at least give full_execution_context_t a name that better describes its
purpose?
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2005-04-27 19:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 17:25 Xen/ia64 presentation Magenheimer, Dan (HP Labs Fort Collins)
2005-04-27 19:12 ` Hollis Blanchard
2005-04-27 19:24 ` Keir Fraser
2005-04-27 19:31 ` Hollis Blanchard [this message]
2005-04-27 19:34 ` Keir Fraser
2005-04-27 20:08 ` Hollis Blanchard
2005-04-28 8:32 ` Keir Fraser
2005-04-28 8:54 ` Keir Fraser
2005-04-28 18:10 ` Hollis Blanchard
2005-04-28 18:38 ` Keir Fraser
2005-04-28 18:58 ` Hollis Blanchard
2005-04-28 19:47 ` Keir Fraser
2005-04-28 20:11 ` Hollis Blanchard
2005-04-27 19:31 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 21:47 Magenheimer, Dan (HP Labs Fort Collins)
2005-04-27 22:34 ` Hollis Blanchard
2005-04-28 14:53 Dong, Eddie
2005-04-28 19:05 Magenheimer, Dan (HP Labs Fort Collins)
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=426FE884.2010904@us.ibm.com \
--to=hollisb@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=dan.magenheimer@hp.com \
--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.