Re: [Xen-devel] [PATCH 2 of 5] x86: make the pv-only e820 array

On Fri, Apr 08, 2011 at 09:22:05AM +0100, Ian Campbell wrote:
> On Thu, 2011-04-07 at 21:25 +0100, Konrad Rzeszutek Wilk wrote:
> > # HG changeset patch
> > # User Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
> > # Date 1302202697 14400
> > # Node ID 01d0d338b97491a3aa816dab43cc709a234214f7
> > # Parent  decab6c21cc3d7ce4d4dad949d34ba35d4600490
> > x86: make the pv-only e820 array be dynamic.
> > 
> > During creation of the PV domain we allocate the E820 structure to be
> > the E820MAX. This will allow the tool stack to fill the E820 with more
> > than three entries.
> 
> Is it possible to defer this allocation to set_memory_map time so we can
> allocate only the required size? I guess E820MAX (128) entries is only
> 2.5k but a typical e820 is capped at more like 20 entries in practice
> (<0.5k).

The later patch does that. If I figure out how to "squash" the hg commits
together I can post it as one patch..

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Xen-devel] [PATCH 1 of 5] tools: Add xc_domain_set_memory_map and xc_get_machine_memory_map calls, Konrad Rzeszutek Wilk

Next by Date:

Re: [Xen-devel] [PATCH 0 of 5] Patches for PCI passthrough with modified E820., Konrad Rzeszutek Wilk

Previous by Thread:

Re: [Xen-devel] [PATCH 2 of 5] x86: make the pv-only e820 array be dynamic, Ian Campbell

Next by Thread:

[Xen-devel] [PATCH 5 of 5] libxl: Convert E820_UNUSABLE and E820_RAM to E820_UNUSABLE as appropriate, Konrad Rzeszutek Wilk

Indexes:

[Date] [Thread] [Top] [All Lists]

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] [PATCH 2 of 5] x86: make the pv-only e820 array be dynam