xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Han, Huaitong" <huaitong.han@intel.com>
To: "JBeulich@suse.com" <JBeulich@suse.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
	"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
	"stefano.stabellini@eu.citrix.com"
	<stefano.stabellini@eu.citrix.com>,
	"george.dunlap@eu.citrix.com" <george.dunlap@eu.citrix.com>,
	"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
	"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
	"george.dunlap@citrix.com" <george.dunlap@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"keir@xen.org" <keir@xen.org>
Subject: Re: [V3 PATCH 7/9] x86/hvm: pkeys, add pkeys support for guest_walk_tables
Date: Wed, 16 Dec 2015 08:16:54 +0000	[thread overview]
Message-ID: <1450253821.4539.3.camel@intel.com> (raw)
In-Reply-To: <566FE51902000078000BF67A@prv-mh.provo.novell.com>

On Tue, 2015-12-15 at 02:02 -0700, Jan Beulich wrote:
> > > > On 15.12.15 at 09:14, <huaitong.han@intel.com> wrote:
> > On Fri, 2015-12-11 at 02:26 -0700, Jan Beulich wrote:
> > > > > > On 10.12.15 at 19:19, <george.dunlap@citrix.com> wrote:
> > > > On 07/12/15 09:16, Huaitong Han wrote:
> > > > > +    if ( likely(!pte_pkeys) )
> > > > > +        return 0;
> > > > > +
> > > > > +    /* Update vcpu xsave area */
> > > > > +    fpu_xsave(vcpu);
> > > > 
> > > > Is there a reason you're calling fpu_xsave() directly here,
> > > > rather
> > > > than
> > > > just calling vcpu_save_fpu()?  That saves you actually doing
> > > > the
> > > > xsave
> > > > if the fpu hasn't been modified since the last time you read
> > > > it.
> > > 
> > > I've already said on an earlier version that wholesale saving of
> > > the
> > > entire XSAVE state is wrong here. It should just be the single
> > > piece
> > > that we're actually interested in, and it quite likely shouldn't
> > > go
> > > into
> > > struct vcpu (but e.g. into a local buffer).
> > 
> > The comments on V2 version said using vcpu_save_fpu is wrong
> > because of
> >  v->fpu_dirtied, but why wholesale saving of the entire XSAVE state
> > is
> > wrong here? I understand xsave maybe cost a little more.
> 
> "A little" is quite a bit of an understatement.
> 
> > But if we just
> > save the single piece, many functions are not reused because
> > xstate_comp_offsets is pointless, and we need add a new function as
> > follow that looks not good:
> 
> Well, I wouldn't want you to introduce a brand new function, but
> instead just factor out the necessary piece from xsave() (making
> the new one take a struct xsave_struct * instead of a struct vcpu *,
> and calling it from what is now xsave()).
So the function looks like this:
unsigned int get_xsave_pkru(struct vcpu *v)
{
    void *offset;
    struct xsave_struct *xsave_area;
    uint64_t mask = XSTATE_PKRU;
    unsigned int index = fls64(mask) - 1;
    unsigned int pkru = 0;

    if ( !cpu_has_xsave )
        return 0;
    
    BUG_ON(xsave_cntxt_size < XSTATE_AREA_MIN_SIZE);
    xsave_area = _xzalloc(xsave_cntxt_size, 64);
    if ( xsave_area == NULL )
        return 0;

    xsave(xsave_area, mask);
    offset = (void *)xsave_area + (xsave_area_compressed(xsave) ? 
            XSTATE_AREA_MIN_SIZE : xstate_offsets[index] );
    memcpy(&pkru, offset, sizeof(pkru));

    xfree(xsave_area);

    return pkru;
}
> 
> Jan
> 

  reply	other threads:[~2015-12-16  8:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07  9:16 [V3 PATCH 0/9] x86/hvm: pkeys, add memory protection-key support Huaitong Han
2015-12-07  9:16 ` [V3 PATCH 1/9] x86/hvm: pkeys, add the flag to enable Memory Protection Keys Huaitong Han
2015-12-10 15:37   ` George Dunlap
2015-12-07  9:16 ` [V3 PATCH 2/9] x86/hvm: pkeys, add pkeys support when setting CR4 Huaitong Han
2015-12-07  9:16 ` [V3 PATCH 3/9] x86/hvm: pkeys, disable pkeys for guests in non-paging mode Huaitong Han
2015-12-07  9:16 ` [V3 PATCH 4/9] x86/hvm: pkeys, add functions to get pkeys value from PTE Huaitong Han
2015-12-10 15:48   ` George Dunlap
2015-12-10 18:47     ` Andrew Cooper
2015-12-07  9:16 ` [V3 PATCH 5/9] x86/hvm: pkeys, add functions to support PKRU access Huaitong Han
2015-12-10 18:48   ` Andrew Cooper
2015-12-07  9:16 ` [V3 PATCH 6/9] x86/hvm: pkeys, add xstate support for pkeys Huaitong Han
2015-12-10 17:39   ` George Dunlap
2015-12-10 18:57   ` Andrew Cooper
2015-12-11  9:36   ` Jan Beulich
2015-12-07  9:16 ` [V3 PATCH 7/9] x86/hvm: pkeys, add pkeys support for guest_walk_tables Huaitong Han
2015-12-10 18:19   ` George Dunlap
2015-12-11  9:16     ` Wu, Feng
2015-12-11  9:23       ` Jan Beulich
2015-12-16 15:36       ` George Dunlap
2015-12-16 16:28         ` Tim Deegan
2015-12-16 16:34           ` Andrew Cooper
2015-12-16 17:33             ` Tim Deegan
2015-12-16 16:50           ` George Dunlap
2015-12-16 17:21             ` Tim Deegan
2015-12-18  8:21         ` Han, Huaitong
2015-12-18 10:03           ` George Dunlap
2015-12-18 11:46           ` Tim Deegan
2015-12-11  9:23     ` Han, Huaitong
2015-12-11  9:50       ` Jan Beulich
2015-12-11  9:26     ` Jan Beulich
2015-12-15  8:14       ` Han, Huaitong
2015-12-15  9:02         ` Jan Beulich
2015-12-16  8:16           ` Han, Huaitong [this message]
2015-12-16  8:32             ` Jan Beulich
2015-12-16  9:03               ` Han, Huaitong
2015-12-16  9:12                 ` Jan Beulich
2015-12-17  9:18                   ` Han, Huaitong
2015-12-17 10:05                     ` Jan Beulich
2015-12-10 18:59   ` Andrew Cooper
2015-12-11  7:18     ` Han, Huaitong
2015-12-11  8:48       ` Andrew Cooper
2015-12-07  9:16 ` [V3 PATCH 8/9] x86/hvm: pkeys, add pkeys support for gva2gfn funcitons Huaitong Han
2015-12-07  9:16 ` [V3 PATCH 9/9] x86/hvm: pkeys, add pkeys support for cpuid handling Huaitong Han
2015-12-11  9:47   ` Jan Beulich

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=1450253821.4539.3.camel@intel.com \
    --to=huaitong.han@intel.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.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).