From: "Han, Huaitong" <huaitong.han@intel.com>
To: "JBeulich@suse.com" <JBeulich@suse.com>
Cc: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [V2 PATCH 9/9] x86/hvm: pkeys, add pkeys support for gva2gfn funcitons
Date: Thu, 3 Dec 2015 08:50:30 +0000 [thread overview]
Message-ID: <1449132634.4187.13.camel@intel.com> (raw)
In-Reply-To: <565EE5A502000078000BB38D@prv-mh.provo.novell.com>
On Wed, 2015-12-02 at 04:35 -0700, Jan Beulich wrote:
> >>> On 27.11.15 at 10:52, <huaitong.han@intel.com> wrote:
> > --- a/xen/arch/x86/hvm/hvm.c
> > +++ b/xen/arch/x86/hvm/hvm.c
> > @@ -4304,7 +4304,8 @@ static enum hvm_copy_result
> > __hvm_clear(paddr_t addr, int size)
> > p2m_type_t p2mt;
> > char *p;
> > int count, todo = size;
> > - uint32_t pfec = PFEC_page_present | PFEC_write_access;
> > + uint32_t pfec = PFEC_page_present | PFEC_write_access |
> > + hvm_pku_enabled(curr) ? PFEC_prot_key : 0;
> >
> > /*
> > * XXX Disable for 4.1.0: PV-on-HVM drivers will do grant
> > -table ops
> > @@ -4405,7 +4406,8 @@ enum hvm_copy_result hvm_copy_to_guest_virt(
> > {
> > return __hvm_copy(buf, vaddr, size,
> > HVMCOPY_to_guest | HVMCOPY_fault |
> > HVMCOPY_virt,
> > - PFEC_page_present | PFEC_write_access |
> > pfec);
> > + PFEC_page_present | PFEC_write_access | pfec
> > |
> > + hvm_pku_enabled(current) ? PFEC_prot_key :
> > 0);
> > }
> >
> > enum hvm_copy_result hvm_copy_from_guest_virt(
> > @@ -4413,7 +4415,8 @@ enum hvm_copy_result
> > hvm_copy_from_guest_virt(
> > {
> > return __hvm_copy(buf, vaddr, size,
> > HVMCOPY_from_guest | HVMCOPY_fault |
> > HVMCOPY_virt,
> > - PFEC_page_present | pfec);
> > + PFEC_page_present | pfec |
> > + hvm_pku_enabled(current) ? PFEC_prot_key :
> > 0);
> > }
> >
> > enum hvm_copy_result hvm_fetch_from_guest_virt(
> > @@ -4431,7 +4434,8 @@ enum hvm_copy_result
> > hvm_copy_to_guest_virt_nofault(
> > {
> > return __hvm_copy(buf, vaddr, size,
> > HVMCOPY_to_guest | HVMCOPY_no_fault |
> > HVMCOPY_virt,
> > - PFEC_page_present | PFEC_write_access |
> > pfec);
> > + PFEC_page_present | PFEC_write_access | pfec
> > |
> > + hvm_pku_enabled(current) ? PFEC_prot_key :
> > 0);
> > }
> >
> > enum hvm_copy_result hvm_copy_from_guest_virt_nofault(
> > @@ -4439,7 +4443,8 @@ enum hvm_copy_result
> > hvm_copy_from_guest_virt_nofault(
> > {
> > return __hvm_copy(buf, vaddr, size,
> > HVMCOPY_from_guest | HVMCOPY_no_fault |
> > HVMCOPY_virt,
> > - PFEC_page_present | pfec);
> > + PFEC_page_present | pfec |
> > + hvm_pku_enabled(current) ? PFEC_prot_key :
> > 0);
> > }
> >
> > enum hvm_copy_result hvm_fetch_from_guest_virt_nofault(
>
> Was this patch tested at all? The lack of parentheses in all the
> changes you make result - afaict - in PFEC_prot_key to be
> unconditionally passed to __hvm_copy(), which can't be right.
Yes, the patch can work, I understand, if the pfec parameter of __hvm_c
opy is zero, it means that memory permission check is not to be
required, when pfec is not 0, PKRU has access disable and write
disable, so, PFEC_prot_key is unconditionally passed to the functions.
Thanks
Huaitong.
next prev parent reply other threads:[~2015-12-03 8:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 9:51 [V2 PATCH 0/9] x86/hvm: pkeys, add memory protection-key support Huaitong Han
2015-11-27 9:51 ` [V2 PATCH 1/9] x86/hvm: pkeys, add pkeys support for cpuid handling Huaitong Han
2015-12-01 20:03 ` Andrew Cooper
2015-12-02 11:06 ` Jan Beulich
2015-12-03 1:53 ` Han, Huaitong
2015-12-03 10:41 ` Jan Beulich
2015-12-02 11:19 ` Jan Beulich
2015-11-27 9:51 ` [V2 PATCH 2/9] x86/hvm: pkeys, add the flag to enable Memory Protection Keys Huaitong Han
2015-12-01 20:04 ` Andrew Cooper
2015-12-02 11:21 ` Jan Beulich
2015-11-27 9:51 ` [V2 PATCH 3/9] x86/hvm: pkeys, add pkeys support when setting CR4 Huaitong Han
2015-12-01 20:05 ` Andrew Cooper
2015-11-27 9:51 ` [V2 PATCH 4/9] x86/hvm: pkeys, disable pkeys for guests in non-paging mode Huaitong Han
2015-11-27 9:51 ` [V2 PATCH 5/9] x86/hvm: pkeys, add functions to get pkeys value from PTE Huaitong Han
2015-12-01 20:11 ` Andrew Cooper
2015-12-02 11:24 ` Jan Beulich
2015-11-27 9:52 ` [V2 PATCH 6/9] x86/hvm: pkeys, add functions to support PKRU access Huaitong Han
2015-12-01 20:12 ` Andrew Cooper
2015-11-27 9:52 ` [V2 PATCH 7/9] x86/hvm: pkeys, add pkeys support for guest_walk_tables Huaitong Han
2015-12-01 20:30 ` Andrew Cooper
2015-12-02 8:23 ` Han, Huaitong
2015-12-02 11:14 ` Jan Beulich
2015-12-02 11:16 ` Jan Beulich
2015-12-02 11:29 ` Jan Beulich
2015-11-27 9:52 ` [V2 PATCH 8/9] x86/hvm: pkeys, add xstate support for pkeys Huaitong Han
2015-12-01 20:43 ` Andrew Cooper
2015-12-02 7:20 ` Han, Huaitong
2015-12-02 11:31 ` Jan Beulich
2015-12-03 1:58 ` Han, Huaitong
2015-12-03 10:42 ` Jan Beulich
2015-12-03 10:56 ` Andrew Cooper
2015-11-27 9:52 ` [V2 PATCH 9/9] x86/hvm: pkeys, add pkeys support for gva2gfn funcitons Huaitong Han
2015-12-02 11:35 ` Jan Beulich
2015-12-03 8:50 ` Han, Huaitong [this message]
2015-12-03 10:47 ` Jan Beulich
2015-11-27 12:59 ` [V2 PATCH 0/9] x86/hvm: pkeys, add memory protection-key support Andrew Cooper
2015-11-27 16:22 ` Han, Huaitong
2015-11-27 16:31 ` 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=1449132634.4187.13.camel@intel.com \
--to=huaitong.han@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@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 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.