xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Lars Kurth" <lars.kurth@citrix.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Wei Liu" <wl@xen.org>,
	"George Dunlap" <George.Dunlap@eu.citrix.com>,
	"Julien Grall" <julien.grall@arm.com>,
	"Ian Jackson" <ian.jackson@citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] Terminology for "guest" - Was: [PATCH] docs/sphinx: Introduction
Date: Thu, 8 Aug 2019 09:43:01 +0100	[thread overview]
Message-ID: <2e3a40d8-14ec-9f84-6a43-d7389bdbebf8@citrix.com> (raw)
In-Reply-To: <ad94d279-e53c-b1ae-c333-096944b217dd@suse.com>

On 08/08/2019 07:22, Jan Beulich wrote:
> On 07.08.2019 21:41, Andrew Cooper wrote:
>> --- /dev/null
>> +++ b/docs/glossary.rst
>> @@ -0,0 +1,37 @@
>> +Glossary
>> +========
>> +
>> +.. Terms should appear in alphabetical order
>> +
>> +.. glossary::
>> +
>> +   control domain
>> +     A :term:`domain`, commonly dom0, with the permission and
>> responsibility
>> +     to create and manage other domains on the system.
>> +
>> +   domain
>> +     A domain is Xen's unit of resource ownership, and generally has
>> at the
>> +     minimum some RAM and virtual CPUs.
>> +
>> +     The terms :term:`domain` and :term:`guest` are commonly used
>> +     interchangeably, but they mean subtly different things.
>> +
>> +     A guest is a single virtual machine.
>> +
>> +     Consider the case of live migration where, for a period of
>> time, one
>> +     guest will be comprised of two domains, while it is in transit.
>> +
>> +   domid
>> +     The numeric identifier of a running :term:`domain`.  It is
>> unique to a
>> +     single instance of Xen, used as the identifier in various APIs,
>> and is
>> +     typically allocated sequentially from 0.
>> +
>> +   guest
>> +     See :term:`domain`
>
> I think you want to mention the usual distinction here: Dom0 is,
> while a domain, commonly not considered a guest.

To be honest, I had totally forgotten about that.  I guess now is the
proper time to rehash it in public.

I don't think the way it currently gets used has a clear or coherent set
of rules, because I can't think of any to describe how it does get used.

Either there are a clear and coherent (and simple!) set of rules for
what we mean by "guest", at which point they can live here in the
glossary, or the fuzzy way it is current used should cease.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-08-08  8:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07 19:41 [Xen-devel] [PATCH] docs/sphinx: Introduction Andrew Cooper
2019-08-07 22:49 ` Hans van Kranenburg
2019-08-07 23:25   ` Andrew Cooper
2019-08-08  6:22 ` Jan Beulich
2019-08-08  8:43   ` Andrew Cooper [this message]
2019-08-08  9:04     ` [Xen-devel] Terminology for "guest" - Was: " Jan Beulich
2019-08-08  9:13       ` Julien Grall
2019-08-08 10:30         ` Andrew Cooper
2019-08-08 10:49         ` Jan Beulich
2019-08-08 11:22           ` Rich Persaud
2019-08-12 14:53         ` George Dunlap
2019-08-12 15:01           ` Andrew Cooper
2019-08-13  2:59             ` Sarah Newman
2019-08-13  8:43               ` George Dunlap
2019-08-13  8:46                 ` Lars Kurth
2019-08-13 19:58                 ` Sarah Newman
2019-08-08  9:49     ` Roger Pau Monné
2019-08-12 15:36 ` [Xen-devel] " George Dunlap

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=2e3a40d8-14ec-9f84-6a43-d7389bdbebf8@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /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).