From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] x86/hvm: Allow the guest to permit the use of userspace hypercalls
Date: Thu, 14 Jan 2016 10:50:59 +0000 [thread overview]
Message-ID: <1452768659.2185.18.camel@citrix.com> (raw)
In-Reply-To: <1452520774-16794-1-git-send-email-andrew.cooper3@citrix.com>
On Mon, 2016-01-11 at 13:59 +0000, Andrew Cooper wrote:
> Arm folks: Is something like this sufficiently generic to be useful on
> Arm, perhaps with more generic naming?
ARM's HVC instruction is always invalid from userspace, i.e. it would
result in #UNDEF and there is no control bit to make it do otherwise, so I
think there isn't much point.
Ian.
prev parent reply other threads:[~2016-01-14 10:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 13:59 [PATCH] x86/hvm: Allow the guest to permit the use of userspace hypercalls Andrew Cooper
2016-01-11 14:32 ` Paul Durrant
2016-01-11 14:44 ` Jan Beulich
2016-01-11 17:17 ` Andrew Cooper
2016-01-11 18:26 ` David Vrabel
2016-01-11 18:32 ` Andrew Cooper
2016-01-11 18:40 ` David Vrabel
2016-01-11 18:50 ` Andrew Cooper
2016-01-12 12:07 ` Stefano Stabellini
2016-01-12 15:06 ` Jan Beulich
2016-01-12 17:05 ` Stefano Stabellini
2016-01-12 17:10 ` Juergen Gross
2016-01-12 17:23 ` Stefano Stabellini
2016-01-13 5:12 ` Juergen Gross
2016-01-13 10:41 ` Stefano Stabellini
2016-01-13 11:14 ` Juergen Gross
2016-01-13 11:26 ` Stefano Stabellini
2016-01-13 11:32 ` Juergen Gross
2016-01-13 11:42 ` David Vrabel
2016-01-13 12:51 ` Stefano Stabellini
2016-01-12 7:33 ` Jan Beulich
2016-01-12 10:57 ` Andrew Cooper
2016-01-12 11:03 ` George Dunlap
2016-01-14 10:50 ` Ian Campbell [this message]
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=1452768659.2185.18.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=stefano.stabellini@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).