Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755457AbZCKR16 (ORCPT ); Wed, 11 Mar 2009 13:27:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755018AbZCKR1m (ORCPT ); Wed, 11 Mar 2009 13:27:42 -0400 Received: from waste.org ([66.93.16.53]:39894 "EHLO waste.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754705AbZCKR1m (ORCPT ); Wed, 11 Mar 2009 13:27:42 -0400 Subject: Re: [PATCH] fix/improve generic page table walker From: Matt Mackall To: Martin Schwidefsky Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Gerald Schaefer , akpm@linux-foundation.org In-Reply-To: <20090311144951.58c6ab60@skybase> References: <20090311144951.58c6ab60@skybase> Content-Type: text/plain Date: Wed, 11 Mar 2009 12:24:23 -0500 Message-Id: <1236792263.3205.45.camel@calx> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1690 Lines: 35 On Wed, 2009-03-11 at 14:49 +0100, Martin Schwidefsky wrote: > From: Martin Schwidefsky > > On s390 the /proc/pid/pagemap interface is currently broken. This is > caused by the unconditional loop over all pgd/pud entries as specified > by the address range passed to walk_page_range. The tricky bit here > is that the pgd++ in the outer loop may only be done if the page table > really has 4 levels. For the pud++ in the second loop the page table needs > to have at least 3 levels. With the dynamic page tables on s390 we can have > page tables with 2, 3 or 4 levels. Which means that the pgd and/or the > pud pointer can get out-of-bounds causing all kinds of mayhem. Not sure why this should be a problem without delving into the S390 code. After all, x86 has 2, 3, or 4 levels as well (at compile time) in a way that's transparent to the walker. > The proposed solution is to fast-forward over the hole between the start > address and the first vma and the hole between the last vma and the end > address. The pgd/pud/pmd/pte loops are used only for the address range > between the first and last vma. This guarantees that the page table > pointers stay in range for s390. For the other architectures this is > a small optimization. I've gone to lengths to keep VMAs out of the equation, so I can't say I'm excited about this solution. -- http://selenic.com : development and support for Mercurial and Linux -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/