From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
boris.ostrovsky@oracle.com, Aravind.Gopalakrishnan@amd.com,
suravee.suthikulpanit@amd.com
Subject: Re: [RFH]: AMD CR intercept for lmsw/clts
Date: Tue, 5 Aug 2014 15:22:10 -0700 [thread overview]
Message-ID: <20140805152210.38d7de5d@mantra.us.oracle.com> (raw)
In-Reply-To: <53E0A7EC02000078000294FF@mail.emea.novell.com>
On Tue, 05 Aug 2014 08:46:20 +0100
"Jan Beulich" <JBeulich@suse.com> wrote:
> >>> On 05.08.14 at 03:33, <mukesh.rathor@oracle.com> wrote:
> > Hi,
> >
> > On AMD, clts/lmsw will cause "mov cr" vmexit, but unlike intel, they
> > can't be handled via svm_vmexit_do_cr_access and are emulated thru
> > handle_mmio() which is a problem for pvh because of:
> >
.....
> > Or, should I just create a new function for clts/lmsw and call it
> > directly from vmexit switch itself?
>
> I'd prefer this - it seems pretty ugly to me that handle_mmio()/
> x86_emulate() gets used for this purpose - but am not certain this
> will actually work out nicely for other than CLTS: All the
> instructions currently handled specially are ones with fixed
> operands, and only CLTS fits that.
>
> You'll btw have the same problem with SMSW and DRx accesses,
> string I/O instructions, as well as (on older CPUs) with moves to/from
> CRx and INVLPG.
I see, I'd be duplicating from x86_emulate more than just couple cases, so
I think the best thing would be to just call x86_emulate directly, which
is what should've been done in the first place for the CR intercepts.
BTW, as regards INVLPG, I'm *requiring* svm decode for pvh.
thanks,
Mukesh
prev parent reply other threads:[~2014-08-05 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 1:33 [RFH]: AMD CR intercept for lmsw/clts Mukesh Rathor
2014-08-05 7:46 ` Jan Beulich
2014-08-05 11:16 ` Andrew Cooper
2014-08-05 12:11 ` Jan Beulich
2014-08-05 13:00 ` Andrew Cooper
2014-08-05 13:15 ` Jan Beulich
2014-08-05 22:30 ` Mukesh Rathor
2014-08-06 9:34 ` Andrew Cooper
2014-08-15 21:04 ` Konrad Rzeszutek Wilk
2014-08-15 21:48 ` Andrew Cooper
2014-08-05 22:22 ` Mukesh Rathor [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=20140805152210.38d7de5d@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xenproject.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).