From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [HYBRID]: XEN_EMULATE_PREFIX in user process
Date: Mon, 2 Jul 2012 10:29:05 +0100 [thread overview]
Message-ID: <1341221345.4625.8.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <4FF177A3020000780008D091@nat28.tlf.novell.com>
On Mon, 2012-07-02 at 09:27 +0100, Jan Beulich wrote:
> >>> On 30.06.12 at 00:50, Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
> > On Fri, 29 Jun 2012 15:04:14 -0700 (PDT)
> > Ian Campbell <Ian.Campbell@citrix.com> wrote:
> >
> >> On Fri, 2012-06-29 at 20:07 +0100, Mukesh Rathor wrote:
> >>
> >> I don't think reducing code should come at the expense of adding
> >> special cases for hybrid to userspace programs...
> >>
> >> I think you'll have to handle the invalid op, it can't be that much
> >> code, can it?
> >
> > Not a whole lot of code, but other than xen-detect, just curious,
> > what is the possibility of any user level using XEN_EMULATE_PREFIX cpuid?
>
> Obviously any code cloned from xen-detect could, i.e. anything
> that tries to be Xen-PV-aware.
Which shouldn't be all that much code but we can't really just declare
it to be wrong...
Ian.
next prev parent reply other threads:[~2012-07-02 9:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 1:00 [HYBRID]: XEN_EMULATE_PREFIX in user process Mukesh Rathor
2012-06-29 1:09 ` Konrad Rzeszutek Wilk
2012-06-29 1:26 ` Mukesh Rathor
2012-06-29 8:09 ` Ian Campbell
2012-06-29 18:15 ` Mukesh Rathor
2012-06-29 19:07 ` Mukesh Rathor
2012-06-29 22:04 ` Ian Campbell
2012-06-29 22:50 ` Mukesh Rathor
2012-07-02 8:27 ` Jan Beulich
2012-07-02 9:29 ` Ian Campbell [this message]
2012-07-02 18:18 ` Mukesh Rathor
2012-06-29 7:56 ` Jan Beulich
2012-06-29 8:07 ` Ian Campbell
2012-06-29 8:15 ` Jan Beulich
2012-06-29 21:18 ` Mukesh Rathor
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=1341221345.4625.8.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.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.