From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dan Magenheimer <dan.magenheimer@oracle.com>
Subject: RE: Memory fragmentation, order>0 allocation,
 and 4.0 dynamic RAM optimization features
Date: Thu, 18 Feb 2010 09:32:05 -0800 (PST)
Message-ID: <bbcd9419-ecf3-46f2-bd8b-adfdbc8e4d7e@default>
References: <4B7D02B302000078000300BF@vpn.id2.novell.com>
	<b5a8d8a9-e991-4118-9783-8be1f29fef52@default
	4B7D767D0200007800030229@vpn.id2.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4B7D767D0200007800030229@vpn.id2.novell.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com, Tim Deegan <Tim.Deegan@citrix.com>, GeorgeDunlap <george.dunlap@eu.citrix.com>, PatrickColp <pjcolp@cs.ubc.ca>, Ian Pratt <Ian.Pratt@eu.citrix.com>, Andrew Peace <Andrew.Peace@eu.citrix.com>, Keir Fraser <keir.fraser@eu.citrix.com>, Grzegorz Milos <gm281@cam.ac.uk>
List-Id: xen-devel@lists.xenproject.org

> Since you are so eager to point out and fix all order > 0 allocations

"eager" is a rather poor word choice :-)

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@novell.com]
> Sent: Thursday, February 18, 2010 9:19 AM
> To: Dan Magenheimer
> Cc: Grzegorz Milos; Tim Deegan; PatrickColp; Andrew Peace;
> GeorgeDunlap; Ian Pratt; Keir Fraser; xen-devel@lists.xensource.com
> Subject: RE: Memory fragmentation, order>0 allocation, and 4.0 dynamic
> RAM optimization features
>=20
> >>> Dan Magenheimer <dan.magenheimer@oracle.com> 18.02.10 17:09 >>>
> >But ignoring my flimsy excuses, Jan, do you have some debug code
> >you are using to identify order>0 allocations?  If so, could I
> >have a copy... and perhaps Keir would consider adding
> >it post-4.0 to make it easier to search-and-destroy.
>=20
> I actually noticed this only as a side effect from a much uglier
> debugging
> patch - observing apparent memory corruption with no apparent pattern
> during save/restore/migrate, I finally decided to try a brute force
> method
> and track all allocations. Since you are so eager to point out and fix
> all
> order > 0 allocations, I was quite surprised to see one while tmem
> itself initialized its state for Dom0. Hence I thought I'd point it
> out. The
> patch as it stands is, I think, not really a general debugging aid - if
> you
> think differently, I can of course still share it.
>=20
> Jan
>=20