[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1205438038.14987.1.camel@bodhitayantram.eng.vmware.com>
Date: Thu, 13 Mar 2008 12:53:58 -0700
From: Zachary Amsden <zach@...are.com>
To: Hugh Dickins <hugh@...itas.com>
Cc: Jeremy Fitzhardinge <jeremy@...p.org>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
virtualization@...ts.osdl.org, akpm@...ux-foundation.org,
nickpiggin@...oo.com.au, frankeh@...son.ibm.com,
rusty@...tcorp.com.au, andrea@...ranet.com, clameter@....com,
a.p.zijlstra@...llo.nl, Keir Fraser <keir@...source.com>,
Ian Pratt <ian.pratt@...source.com>
Subject: Re: [patch 0/6] Guest page hinting version 6.
On Thu, 2008-03-13 at 18:55 +0000, Hugh Dickins wrote:
> On Thu, 13 Mar 2008, Jeremy Fitzhardinge wrote:
> >
> > My other concern is just correctness over time on the Linux side. We already
> > have enough trouble keeping things like the pte and page structure state in
> > sync, with resulting rare data-loss bugs. Adding another layer which only
> > applies in specific environments raises the possibility for new bugs to be
> > un-noticed for a long time. How can we structure the VM changes to make sure
> > that its robust in the face of maintenance?
>
> Yes, that's the main concern, as whenever lots of subtlety is added.
> I wonder if there's any chance of a CONFIG_DEBUG mode, which could be
> run on anybody's x86 machine, without involving any virtualization, but
> in which the PAGE_STATEs become essential to the correct working of the mm.
How about a fake hypervisor, which is really just a random page evictor,
following the rules of CMM?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists