From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754803AbZHFJ73 (ORCPT ); Thu, 6 Aug 2009 05:59:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751721AbZHFJ72 (ORCPT ); Thu, 6 Aug 2009 05:59:28 -0400 Received: from mga14.intel.com ([143.182.124.37]:10409 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751361AbZHFJ72 (ORCPT ); Thu, 6 Aug 2009 05:59:28 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.43,332,1246863600"; d="scan'208";a="172942806" Date: Thu, 6 Aug 2009 17:59:05 +0800 From: Wu Fengguang To: Avi Kivity Cc: "Dike, Jeffrey G" , Rik van Riel , "Yu, Wilfred" , "Kleen, Andi" , Andrea Arcangeli , Hugh Dickins , Andrew Morton , Christoph Lameter , KOSAKI Motohiro , Mel Gorman , LKML , linux-mm Subject: Re: [RFC] respect the referenced bit of KVM guest pages? Message-ID: <20090806095905.GA30410@localhost> References: <20090805024058.GA8886@localhost> <4A79C70C.6010200@redhat.com> <9EECC02A4CC333418C00A85D21E89326B651C1FE@azsmsx502.amr.corp.intel.com> <4A79D88E.2040005@redhat.com> <9EECC02A4CC333418C00A85D21E89326B651C21C@azsmsx502.amr.corp.intel.com> <4A7AA0CF.2020700@redhat.com> <20090806092516.GA18425@localhost> <4A7AA3FF.9070808@redhat.com> <20090806093507.GA24669@localhost> <4A7AA999.8050309@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A7AA999.8050309@redhat.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 06, 2009 at 05:59:53PM +0800, Avi Kivity wrote: > On 08/06/2009 12:35 PM, Wu Fengguang wrote: > > On Thu, Aug 06, 2009 at 05:35:59PM +0800, Avi Kivity wrote: > > > >> On 08/06/2009 12:25 PM, Wu Fengguang wrote: > >> > >>>> So you're effectively running a 256M guest on a 128M host? > >>>> > >>>> Do cgroups have private active/inactive lists? > >>>> > >>>> > >>> Yes, and they reuse the same page reclaim routines with the global > >>> LRU lists. > >>> > >>> > >> Then this looks like a bug in the shadow accessed bit handling. > >> > > > > Yes. One question is: why only stack pages hurts if it is a > > general page reclaim problem? > > > > Do we know for a fact that only stack pages suffer, or is it what has > been noticed? It shall be the first case: "These pages are nearly all stack pages.", Jeff said.