From: "Jan Beulich" <JBeulich@suse.com>
To: Juergen Gross <JGross@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
David Vrabel <david.vrabel@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] tools: fix xen-detect to correctly identify domU type
Date: Tue, 29 Mar 2016 00:49:10 -0600 [thread overview]
Message-ID: <56FA418602000078000E0AD3@prv-mh.provo.novell.com> (raw)
In-Reply-To: <56F4FCBF.3060606@suse.com>
>>> On 25.03.16 at 09:54, <JGross@suse.com> wrote:
> Another sum up:
>
> - common sense seems to be the current way xen-detect is trying to
> guess the guest type is unreliable and should be dropped (Jan
> would like to keep it, but I guess he just wants the information
> to be available - is this correct, Jan?)
I just didn't want something that might be useful (even if only
for debugging purposes) to get dropped without some further
thinking about it. It's a tools/ component, so I'll trust the
judgment of the tools maintainers in this regard.
Jan
> - the command line options of xen-detect are not necessary any more
> - the information which guest type we are should be obtainable from
> inside the guest, the consumer of this information should be humans
> only
> - the OS already knows in which mode it is running, so it should be the
> kernel to present that information (David disagrees here: he isn't
> convinced this information is it worth to add another kernel
> interface)
>
> As there is no real hurry to have this topic settled I'd suggest we just
> discuss it at the Hackathon (all involved in the discussion so far but
> George will be there). What do you think?
>
>
> Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-29 6:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 7:50 [PATCH] tools: fix xen-detect to correctly identify domU type Juergen Gross
2016-03-23 9:10 ` Jan Beulich
[not found] ` <56F26B7C02000078000DF896@suse.com>
2016-03-23 9:19 ` Juergen Gross
2016-03-23 9:29 ` Jan Beulich
[not found] ` <56F26FF602000078000DF8C8@suse.com>
2016-03-23 10:14 ` Juergen Gross
2016-03-23 10:25 ` Jan Beulich
2016-03-23 10:32 ` David Vrabel
2016-03-23 10:52 ` Juergen Gross
2016-03-23 10:55 ` Andrew Cooper
2016-03-23 10:59 ` David Vrabel
2016-03-23 11:12 ` Andrew Cooper
2016-03-23 11:18 ` David Vrabel
2016-03-23 11:25 ` Andrew Cooper
2016-03-23 19:03 ` Juergen Gross
2016-03-24 10:22 ` David Vrabel
2016-03-24 10:58 ` Juergen Gross
2016-03-24 11:23 ` Andrew Cooper
2016-03-24 11:38 ` George Dunlap
2016-03-25 8:54 ` Juergen Gross
2016-03-29 6:49 ` Jan Beulich [this message]
2016-03-29 13:54 ` George Dunlap
2016-03-29 14:00 ` Juergen Gross
2016-03-29 14:05 ` George Dunlap
2016-03-23 11:33 ` Juergen Gross
2016-03-23 12:50 ` Boris Ostrovsky
2016-03-23 10:34 ` Andrew Cooper
2016-03-23 10:48 ` Juergen Gross
2016-03-23 10:29 ` Andrew Cooper
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=56FA418602000078000E0AD3@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JGross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.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 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).