From: Lars Kurth <lars.kurth@xen.org>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Cleaning up user confusion about different virt modes in Xen
Date: Thu, 08 May 2014 12:02:04 +0100 [thread overview]
Message-ID: <536B642C.2010104@xen.org> (raw)
Folks,
have a look at
http://brendangregg.com/blog/2014-05-07/what-color-is-your-xen.html ...
It's a well made case about the confusion our terminology has created in
user-land. Admittedly, it was a lot worse before we came up with the
virtualization spectrum. But since then ARM created extra complexity.
The article makes some very good points, and a sensible solution, but
also throws up new problems. Maybe it is time to clean up the confusion
in terminology, use it consistently and fix our documentation.
But before we consider this, I wanted put the article up for debate
Best Regards
Lars
next reply other threads:[~2014-05-08 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 11:02 Lars Kurth [this message]
2014-05-12 9:56 ` Cleaning up user confusion about different virt modes in Xen George Dunlap
2014-05-12 10:29 ` Lars Kurth
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=536B642C.2010104@xen.org \
--to=lars.kurth@xen.org \
--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 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).