From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>,
<xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] xen/p2m: fix extra memory regions accounting
Date: Thu, 3 Sep 2015 16:38:25 +0200 [thread overview]
Message-ID: <55E85B61.4070203@citrix.com> (raw)
In-Reply-To: <55E83C46.8010701@suse.com>
El 03/09/15 a les 14.25, Juergen Gross ha escrit:
> On 09/03/2015 02:05 PM, Roger Pau Monne wrote:
>> On systems with memory maps with ranges that don't end at page
>> boundaries,
>> like:
>>
>> [...]
>> (XEN) 0000000000100000 - 00000000dfdf9c00 (usable)
>> (XEN) 00000000dfdf9c00 - 00000000dfe4bc00 (ACPI NVS)
>> [...]
>>
>> xen_add_extra_mem will create a protected range that ends up at
>> 0xdfdf9c00,
>> but the function used to check if a memory address is inside of a
>> protected
>> range works with pfns, which means that an attempt to map 0xdfdf9c00
>> will be
>> refused because the check is performed against 0xdfdf9000 instead of
>> 0xdfdf9c00.
>>
>> In order to fix this, make sure that the ranges that are added to the
>> xen_extra_mem array are aligned to page boundaries.
>>
>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> Cc: David Vrabel <david.vrabel@citrix.com>
>> Cc: Juergen Gross <jgross@suse.com>
>> Cc: xen-devel@lists.xenproject.org
>> ---
>> AFAICT this patch needs to be backported to 3.19, 4.0, 4.1 and 4.2.
>> ---
>> arch/x86/xen/setup.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
>> index 55f388e..dcf5865 100644
>> --- a/arch/x86/xen/setup.c
>> +++ b/arch/x86/xen/setup.c
>> @@ -68,6 +68,9 @@ static void __init xen_add_extra_mem(phys_addr_t
>> start, phys_addr_t size)
>> {
>> int i;
>>
>> + start = PAGE_ALIGN(start);
>> + size &= PAGE_MASK;
>
> This is not correct. If start wasn't page aligned and size was, you'll
> add one additional page to xen_extra_mem.
I'm not understanding this, let's put an example:
start = 0x8c00
size = 0x1000
After the fixup added above this would become:
start = 0x9000
size = 0x1000
So if anything, I'm adding one page less (because 0x8000 was partly
added, and with the fixup it is not added).
Roger.
next prev parent reply other threads:[~2015-09-03 14:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 12:05 [PATCH] xen/p2m: fix extra memory regions accounting Roger Pau Monne
2015-09-03 12:15 ` Roger Pau Monné
2015-09-03 12:26 ` Juergen Gross
2015-09-03 12:25 ` Juergen Gross
2015-09-03 14:38 ` Roger Pau Monné [this message]
2015-09-03 14:45 ` David Vrabel
2015-09-03 14:52 ` [Xen-devel] " David Vrabel
2015-09-03 14:55 ` Juergen Gross
2015-09-03 15:01 ` David Vrabel
2015-09-03 15:20 ` Juergen Gross
2015-09-03 15:39 ` Roger Pau Monné
2015-09-03 15:46 ` Juergen Gross
2015-09-04 5:07 ` Juergen Gross
2015-09-04 7:37 ` Roger Pau Monné
2015-09-04 7:47 ` Juergen Gross
2015-09-04 7:57 ` Roger Pau Monné
2015-09-04 8:07 ` Juergen Gross
2015-09-03 14:50 ` Juergen Gross
-- strict thread matches above, loose matches on Subject: below --
2015-09-03 12:03 Roger Pau Monne
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=55E85B61.4070203@citrix.com \
--to=roger.pau@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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).