All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Julien Grall <julien.grall@arm.com>
Cc: Stefano Stabellini <stefanos@xilinx.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	andrii_anisov@epam.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v4 03/23] xen/arm: document dom0less
Date: Mon, 22 Oct 2018 17:12:00 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.10.1810221701260.31582@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <4954c486-9663-552c-0fd8-9f59421146b5@arm.com>

On Tue, 9 Oct 2018, Julien Grall wrote:
> Hi Stefano,
> 
> On 05/10/2018 19:47, Stefano Stabellini wrote:
> > Add a new document to provide information on how to use dom0less related
> > features and their current limitations.
> > 
> > Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
> > 
> > ---
> > Changes in v4:
> > - rename to .txt
> > - improve wording
> > 
> > Changes in v3:
> > - add patch
> > ---
> >   docs/misc/arm/dom0less.txt | 47
> > ++++++++++++++++++++++++++++++++++++++++++++++
> 
> As said on the previous version, you likely need to add an entry in
> docs/INDEX.

OK

> >   1 file changed, 47 insertions(+)
> >   create mode 100644 docs/misc/arm/dom0less.txt
> > 
> > diff --git a/docs/misc/arm/dom0less.txt b/docs/misc/arm/dom0less.txt
> > new file mode 100644
> > index 0000000..df96b41
> > --- /dev/null
> > +++ b/docs/misc/arm/dom0less.txt
> > @@ -0,0 +1,47 @@
> > +Dom0less
> > +========
> > +
> > +"Dom0less" is a set of Xen features that enable the deployment of a Xen
> > +system without an hardware domain (often referred to as "dom0").
> I realize I suggested the wording hardware domain. But reading this again, it
> feels that "control domain" may be the best wording here. Indeed what we avoid
> is the toolstack and domain control the domains.

OK


> You begin the document writing "it is a set of Xen featueres that enable
> deployment of a Xen system without an hardware domain". I understand this
> sentence as there would be no "hardware domain". But then you write "create a
> set of DomU alongside Dom0".
> 
> Furthermore, at some point the control domain would disappear and the DomID 0
> may be allocated to a DomUs. Adding further confusion to a user seen the ID
> would be 0.
> 
> So I still think that using "Dom0" within the document is misleading and also
> the feature name. I don't have a good suggestion for the feature name. But at
> very least I would avoid the word "Dom0" everywhere in that document.
 
I'll reword the document to avoid "Dom0"

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

  parent reply	other threads:[~2018-10-23  0:12 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 18:47 [PATCH v4 00/23] dom0less step1: boot multiple domains from device tree Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 01/23] xen: allow console_io hypercalls from certain DomUs Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 02/23] xen/arm: extend device tree based multiboot protocol Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 03/23] xen/arm: document dom0less Stefano Stabellini
2018-10-09 11:52   ` Julien Grall
2018-10-16  7:58     ` Lars Kurth
2018-10-22 23:58       ` Stefano Stabellini
2018-10-23  0:12     ` Stefano Stabellini [this message]
2018-10-05 18:47 ` [PATCH v4 04/23] xen/arm: increase MAX_MODULES Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 05/23] xen/arm: introduce bootcmdlines Stefano Stabellini
2018-10-09 13:24   ` Julien Grall
2018-10-23  1:59     ` Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 06/23] xen/arm: don't add duplicate boot modules, introduce domU flag Stefano Stabellini
2018-10-09 13:35   ` Julien Grall
2018-10-19 23:36     ` Stefano Stabellini
2018-10-20 12:10       ` Julien Grall
2018-10-05 18:47 ` [PATCH v4 07/23] xen/arm: probe domU kernels and initrds Stefano Stabellini
2018-10-15 14:27   ` Julien Grall
2018-10-20  0:42     ` Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 08/23] xen/arm: rename get_11_allocation_size to get_allocation_size Stefano Stabellini
2018-10-15 14:28   ` Julien Grall
2018-10-05 18:47 ` [PATCH v4 09/23] xen/arm: rename allocate_memory to allocate_memory_11 Stefano Stabellini
2018-10-15 14:29   ` Julien Grall
2018-10-05 18:47 ` [PATCH v4 10/23] xen/arm: introduce allocate_memory Stefano Stabellini
2018-10-15 14:43   ` Julien Grall
2018-10-19 22:28     ` Stefano Stabellini
2018-10-20 11:58       ` Julien Grall
2018-10-22 23:53         ` Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 11/23] xen/arm: refactor construct_dom0 Stefano Stabellini
2018-10-15 14:49   ` Julien Grall
2018-10-17 15:06     ` Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 12/23] xen/arm: introduce create_domUs Stefano Stabellini
2018-10-15 15:05   ` Julien Grall
2018-10-19 22:37     ` Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 13/23] xen/arm: implement construct_domU Stefano Stabellini
2018-10-15 15:15   ` Julien Grall
2018-10-19 22:53     ` Stefano Stabellini
2018-10-20 12:01       ` Julien Grall
2018-10-22 19:46         ` Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 14/23] xen/arm: generate a simple device tree for domUs Stefano Stabellini
2018-10-15 15:24   ` Julien Grall
2018-10-17 15:09     ` Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 15/23] xen/arm: make set_interrupt_ppi able to handle non-PPI Stefano Stabellini
2018-10-15 15:25   ` Julien Grall
2018-10-05 18:47 ` [PATCH v4 16/23] xen/arm: generate vpl011 node on device tree for domU Stefano Stabellini
2018-10-15 15:47   ` Julien Grall
2018-10-17 14:59     ` Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 17/23] xen/arm: introduce a union in vpl011 Stefano Stabellini
2018-10-15 15:49   ` Julien Grall
2018-10-05 18:47 ` [PATCH v4 18/23] xen/arm: refactor vpl011_data_avail Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 19/23] xen/arm: Allow vpl011 to be used by DomU Stefano Stabellini
2018-10-15 15:56   ` Julien Grall
2018-10-05 18:47 ` [PATCH v4 20/23] xen: support console_switching between Dom0 and DomUs on ARM Stefano Stabellini
2018-10-08  9:50   ` Jan Beulich
2018-10-19 23:10     ` Stefano Stabellini
2018-10-25  9:37       ` Jan Beulich
2018-10-05 18:47 ` [PATCH v4 21/23] xen/vpl011: buffer out chars when the backend is xen Stefano Stabellini
2018-10-08  9:41   ` Jan Beulich
2018-10-19 23:20     ` Stefano Stabellini
2018-10-20 12:07       ` Julien Grall
2018-10-22 23:46         ` Stefano Stabellini
2018-10-15 16:10   ` Julien Grall
2018-10-17 15:24     ` Stefano Stabellini
2018-10-05 18:47 ` [PATCH v4 22/23] xen/arm: move kernel.h to asm-arm/ Stefano Stabellini
2018-10-15 16:17   ` Julien Grall
2018-10-17 14:42     ` Stefano Stabellini
2018-10-17 16:11       ` Julien Grall
2018-10-17 16:26         ` Andrew Cooper
2018-10-19 21:54         ` Stefano Stabellini
2018-10-20 10:49           ` Julien Grall
2018-10-05 18:47 ` [PATCH v4 23/23] xen/arm: split domain_build.c Stefano Stabellini

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=alpine.DEB.2.10.1810221701260.31582@sstabellini-ThinkPad-X260 \
    --to=sstabellini@kernel.org \
    --cc=andrii_anisov@epam.com \
    --cc=julien.grall@arm.com \
    --cc=stefanos@xilinx.com \
    --cc=xen-devel@lists.xen.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 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.