From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756492Ab1JQWet (ORCPT ); Mon, 17 Oct 2011 18:34:49 -0400 Received: from smtp-out.google.com ([74.125.121.67]:37649 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756309Ab1JQWer (ORCPT ); Mon, 17 Oct 2011 18:34:47 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:date:from:x-x-sender:to:cc:subject: in-reply-to:message-id:references:user-agent:mime-version:content-type:x-system-of-record; b=rqAzB8sDHLzM1BfWTr/HvusZsliSC4tHWSQCytl88M/87pODEk5WRrU2qoInQw+Af w2MSB88qvF/s9nIPku9Jg== Date: Mon, 17 Oct 2011 15:34:29 -0700 (PDT) From: Hugh Dickins X-X-Sender: hugh@sister.anvils To: Alan Cox cc: Rob Clark , Patrik Jakobsson , Andrew Morton , Christoph Hellwig , greg@kroah.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 34/49] gma500: the GEM and GTT code is device independant In-Reply-To: <20111017223928.4d5ed2c6@lxorguk.ukuu.org.uk> Message-ID: References: <20110705141038.23872.55303.stgit@localhost.localdomain> <20110705144140.23872.86541.stgit@localhost.localdomain> <20110708093859.299958df@lxorguk.ukuu.org.uk> <20110711172517.46907e62@lxorguk.ukuu.org.uk> <20111017223928.4d5ed2c6@lxorguk.ukuu.org.uk> User-Agent: Alpine 2.00 (LSU 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 17 Oct 2011, Alan Cox wrote: > > It feels to me like GEM is pulling shmem in an ever more alien direction: > > these device constraints are so foreign to the nature of tmpfs; and > > beyond my expertise, so that I'd be ever more likely to make the wrong > > decisions (mixing swap and uncached pages? hmmm). > > For the most part we fixed that. You can now have a GEM object that is > backed by a private memory object rather than having to be tmpfs. > GMA500 uses it to attach 'stolen' memory to GEM handles, and at least > one other pending submission uses it with a private CMA style allocator. Sounds good. > > The gma500 report seems an odd one - no GMA500 box has >4GB memory so how > did the test code get a page that was unsuitable - is the test buggy ? This is the first I heard of some gma500 test seeing a problem with >4GB. In this thread we have Patrik hitting the oops in read_cache_page_gfp() because of some changes he is preparing, but I thought he and Rob were just thinking ahead when they raise the 4GB issue. Can you point us to another thread on a another list? Hugh