From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH 0/2] XSA-171 Followup work
Date: Wed, 16 Mar 2016 20:05:47 +0000 [thread overview]
Message-ID: <1458158749-21846-1-git-send-email-andrew.cooper3@citrix.com> (raw)
Investigating XSA-171 highlighted how useless the viopl interface for PV
guests actually is. The value can only be set; it can't be queried, and will
go wrong if a 64bit guest kernel programs it with the cpl found in its
exception frames.
Introduce a better alternative.
Andrew Cooper (2):
xen/x86: Don't hold TRAPBOUNCE_flags in %cl during create_bounce_frame
xen/x86: Introduce a new VMASSIST for architectural behaviour of iopl
xen/arch/x86/domain.c | 10 +++++++---
xen/arch/x86/physdev.c | 2 +-
xen/arch/x86/traps.c | 8 ++++++--
xen/arch/x86/x86_64/asm-offsets.c | 3 +++
xen/arch/x86/x86_64/compat/entry.S | 12 ++++++++----
xen/arch/x86/x86_64/compat/traps.c | 4 ++++
xen/arch/x86/x86_64/entry.S | 12 ++++++++----
xen/arch/x86/x86_64/traps.c | 3 +++
xen/include/asm-x86/config.h | 1 +
xen/include/asm-x86/domain.h | 3 ++-
xen/include/public/xen.h | 8 ++++++++
11 files changed, 51 insertions(+), 15 deletions(-)
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-03-16 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 20:05 Andrew Cooper [this message]
2016-03-16 20:05 ` [PATCH 1/2] xen/x86: Don't hold TRAPBOUNCE_flags in %cl during create_bounce_frame Andrew Cooper
2016-03-16 20:05 ` [PATCH 2/2] xen/x86: Introduce a new VMASSIST for architectural behaviour of iopl Andrew Cooper
2016-03-17 10:25 ` Jan Beulich
2016-03-17 10:45 ` Andrew Cooper
2016-03-17 11:00 ` Jan Beulich
2016-03-17 11:05 ` 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=1458158749-21846-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=luto@amacapital.net \
--cc=xen-devel@lists.xen.org \
--subject='Re: [PATCH 0/2] XSA-171 Followup work' \
/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
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).