From: Wei Liu <wei.liu2@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2/5] x86/pv: map_ldt_shadow_page() cleanup
Date: Tue, 29 Aug 2017 13:35:52 +0100 [thread overview]
Message-ID: <20170829123552.azbgadkgxn6ocoyg@citrix.com> (raw)
In-Reply-To: <1504005556-30394-3-git-send-email-andrew.cooper3@citrix.com>
On Tue, Aug 29, 2017 at 12:19:13PM +0100, Andrew Cooper wrote:
> Switch the return value from int to bool, to match its semantics. Switch its
> parameter from a frame offset to a byte offset (simplifying the sole caller)
> and allowing for an extra sanity check that the fault is within the LDT limit.
>
> Drop the unnecessary gmfn and okay local variables, and correct the gva
> parameter to be named linear. Rename l1e to gl1e, and simplify the
> construction of the new pte by simply taking (the now validated) gl1e and
> ensuring that _PAGE_RW is set.
>
> Calculate the pte to updated outside of the spinlock, which halves the size of
be updated?
> the critical region.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Wei Liu <wei.liu2@citrix.com>
with some nitpicking.
> ---
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Wei Liu <wei.liu2@citrix.com>
> ---
> xen/arch/x86/mm.c | 42 +++++++++++++++++++++++-------------------
> xen/arch/x86/traps.c | 2 +-
> xen/include/asm-x86/mm.h | 2 +-
> 3 files changed, 25 insertions(+), 21 deletions(-)
>
> diff --git a/xen/arch/x86/mm.c b/xen/arch/x86/mm.c
> index 79780da..c41ed1b 100644
> --- a/xen/arch/x86/mm.c
> +++ b/xen/arch/x86/mm.c
> @@ -667,45 +667,49 @@ static int alloc_segdesc_page(struct page_info *page)
> }
>
>
> -/* Map shadow page at offset @off. */
> -int map_ldt_shadow_page(unsigned int off)
> +/*
> + * Map a guests LDT page (at @offset bytes from the start of the LDT) into
guest's
> + * Xen's virtual range. Returns true if the mapping changed, false otherwise.
if the mapping is established / successful?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-29 12:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 11:19 [PATCH 0/5] x86: Misc cleanup and improvements Andrew Cooper
2017-08-29 11:19 ` [PATCH 1/5] x86/pv: Switch {fill, zap}_ro_mpt() to using mfn_t Andrew Cooper
2017-08-29 11:52 ` Tim Deegan
2017-08-29 12:01 ` George Dunlap
2017-08-29 12:17 ` Wei Liu
2017-08-29 14:00 ` Jan Beulich
2017-08-29 11:19 ` [PATCH 2/5] x86/pv: map_ldt_shadow_page() cleanup Andrew Cooper
2017-08-29 12:35 ` Wei Liu [this message]
2017-08-29 14:14 ` Jan Beulich
2017-08-29 14:54 ` Andrew Cooper
2017-08-29 15:57 ` [PATCH v2 " Andrew Cooper
2017-08-30 8:21 ` Jan Beulich
2017-08-29 11:19 ` [PATCH 3/5] x86/pv: Consistently use typesafe helpers in all files Andrew Cooper
2017-08-29 13:39 ` Wei Liu
2017-08-29 14:19 ` Jan Beulich
2017-08-29 11:19 ` [PATCH 4/5] x86/pv: Simplify access to the LDT/GDT ptes Andrew Cooper
2017-08-29 13:43 ` Wei Liu
2017-08-29 14:23 ` Jan Beulich
2017-08-29 11:19 ` [PATCH 5/5] x86/percpu: Misc cleanup Andrew Cooper
2017-08-29 13:44 ` Wei Liu
2017-08-29 14:24 ` 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=20170829123552.azbgadkgxn6ocoyg@citrix.com \
--to=wei.liu2@citrix.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 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).