From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/2] x86: limit page type width
Date: Wed, 31 May 2017 04:09:58 -0600 [thread overview]
Message-ID: <592EB296020000780015E27E@prv-mh.provo.novell.com> (raw)
In-Reply-To: <c130e90e-3aa9-712c-9ed5-b9389b9940b6@citrix.com>
>>> On 31.05.17 at 12:01, <andrew.cooper3@citrix.com> wrote:
> On 31/05/17 08:14, Jan Beulich wrote:
>> There's no reason to burn 4 bits on page type when we only have 7 types
>> (plus "none") at present. This requires changing one use of
>> PGT_shared_page, which so far assumed that the type is both a power of
>> 2 and the only type with the high bit set.
>>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> Any particular reason why you reverse the order of shared and writeable?
I've become very used to know that type 7 is "writable", and since
there was a gap at 6 it seemed reasonable to put "shared" there
instead of shifting both down by one.
> Either way, Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Thanks.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-31 10:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 7:04 [PATCH 0/2] x86: XSA_214 follow-up Jan Beulich
2017-05-31 7:14 ` [PATCH 1/2] x86: limit page type width Jan Beulich
2017-05-31 10:01 ` Andrew Cooper
2017-05-31 10:09 ` Jan Beulich [this message]
2017-06-06 8:26 ` Jan Beulich
2017-05-31 7:15 ` [PATCH 2/2] x86: don't allow clearing of TF_kernel_mode for other than 64-bit PV Jan Beulich
2017-05-31 11:08 ` Andrew Cooper
2017-05-31 11:54 ` Jan Beulich
2017-07-03 14:56 ` Ping: " Jan Beulich
2017-12-04 10:15 ` Ping#2: " Jan Beulich
2017-12-04 15:11 ` Andrew Cooper
2017-12-04 17:05 ` 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=592EB296020000780015E27E@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.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 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.