From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
david.vrabel@citrix.com, boris.ostrovsky@oracle.com
Subject: Re: [Patch V5 00/16] xen: support pv-domains larger than 512GB
Date: Wed, 15 Jul 2015 08:07:11 -0400 [thread overview]
Message-ID: <1EB58ABC-2F53-4B36-A2D7-FDF4C7332EA3@oracle.com> (raw)
In-Reply-To: <55A5E100.3070900@suse.com>
On July 15, 2015 12:26:40 AM EDT, Juergen Gross <jgross@suse.com> wrote:
>On 07/10/2015 03:39 PM, Konrad Rzeszutek Wilk wrote:
>> On Fri, Jul 10, 2015 at 02:47:45PM +0200, Juergen Gross wrote:
>>> Support 64 bit pv-domains with more than 512GB of memory.
>>>
>>> Following test have been done:
>>> - 64 bit dom0 on 8GB machine
>>> - 64 bit dom0 on 1TB machine (resolving p2m/E820-map conflict)
>>> - 32 bit dom0 on 8GB machine
>>> - 64 bit dom0 on 8GB machine with faked kernel/E820-map conflict
>>> - 64 bit dom0 on 8GB machine with faked pgtable/E820-map conflict
>>> - 64 bit dom0 on 8GB machine with faked initrd/E820-map conflict
>>> - 64 bit dom0 on 8GB machine with faked p2m/E820-map conflict
>>> - 64 bit domU (sizes up to 900GB)
>>> - 32 bit domU
>>
>> Woot!
>>
>> Thank you for doing that. I noticed that you used the 'normal'
>> sizes, but nothing as odd as '3145M' or such to try to break
>> things. Not sure if it is worht it - as the test suite that
>> Boris runs does run with some odd sizes to catch this.
>
>How did you notice the domU sizes from these lines? :-)
Intuition :-)
>
>I tested with sizes being power of 2 as well as other values (e.g.
>100000 MB).
>
>> I only had one comment about the #13 patch, otherwise I think
>> we are OK with this patchset?
>
>Can I take this as an "Acked-by" for the other patches?
Yes!
>
>
>Juergen
prev parent reply other threads:[~2015-07-15 12:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 12:47 Juergen Gross
2015-07-10 12:47 ` [Patch V5 01/16] xen: sync with xen headers Juergen Gross
2015-07-10 12:47 ` [Patch V5 02/16] xen: save linear p2m list address in shared info structure Juergen Gross
2015-07-10 12:47 ` [Patch V5 03/16] xen: don't build mfn tree if tools don't need it Juergen Gross
2015-07-10 12:47 ` [Patch V5 04/16] xen: eliminate scalability issues from initial mapping setup Juergen Gross
2015-07-10 12:47 ` [Patch V5 05/16] xen: move static e820 map to global scope Juergen Gross
2015-07-10 12:47 ` [Patch V5 06/16] xen: split counting of extra memory pages from remapping Juergen Gross
2015-07-10 12:47 ` [Patch V5 07/16] xen: check memory area against e820 map Juergen Gross
2015-07-10 12:47 ` [Patch V5 08/16] xen: find unused contiguous memory area Juergen Gross
2015-07-10 12:47 ` [Patch V5 09/16] xen: check for kernel memory conflicting with memory layout Juergen Gross
2015-07-10 12:47 ` [Patch V5 10/16] xen: check pre-allocated page tables for conflict with memory map Juergen Gross
2015-07-10 12:47 ` [Patch V5 11/16] xen: check for initrd conflicting with e820 map Juergen Gross
2015-07-10 12:47 ` [Patch V5 12/16] mm: provide early_memremap_ro to establish read-only mapping Juergen Gross
2015-07-10 12:47 ` [Patch V5 13/16] xen: add explicit memblock_reserve() calls for special pages Juergen Gross
2015-07-10 13:36 ` Konrad Rzeszutek Wilk
2015-07-13 4:10 ` Juergen Gross
2015-07-13 14:01 ` Konrad Rzeszutek Wilk
2015-07-10 12:47 ` [Patch V5 14/16] xen: move p2m list if conflicting with e820 map Juergen Gross
2015-07-10 12:48 ` [Patch V5 15/16] xen: allow more than 512 GB of RAM for 64 bit pv-domains Juergen Gross
2015-07-10 12:48 ` [Patch V5 16/16] xen: remove no longer needed p2m.h Juergen Gross
2015-07-10 13:39 ` [Patch V5 00/16] xen: support pv-domains larger than 512GB Konrad Rzeszutek Wilk
2015-07-15 4:26 ` Juergen Gross
2015-07-15 12:07 ` Konrad Rzeszutek Wilk [this message]
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=1EB58ABC-2F53-4B36-A2D7-FDF4C7332EA3@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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
all inboxes | Powered by JetHome®