[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7E82351C108FA840AB1866AC776AEC464399F2D6@orsmsx505.amr.corp.intel.com>
Date: Tue, 6 Jan 2009 11:05:51 -0800
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To: "H. Peter Anvin" <hpa@...or.com>,
Alexey Fisher <bug-track@...her-privat.net>
CC: "kernel-testers-owner@...r.kernel.org"
<kernel-testers-owner@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
Kevin Winchester <kjwinchester@...il.com>,
Ingo Molnar <mingo@...e.hu>
Subject: RE: [regression] glx performance drop with: "x86: PAT: implement
track/untrack of pfnmap regions for x86 - v3"
>-----Original Message-----
>From: H. Peter Anvin [mailto:hpa@...or.com]
>Sent: Tuesday, January 06, 2009 10:52 AM
>To: Alexey Fisher
>Cc: kernel-testers-owner@...r.kernel.org;
>linux-kernel@...r.kernel.org; Siddha, Suresh B; Pallipadi, Venkatesh
>Subject: Re: [regression] glx performance drop with: "x86:
>PAT: implement track/untrack of pfnmap regions for x86 - v3"
>
>Alexey Fisher wrote:
>> glx perfomance regression after this patch.
>> goot kernel: glxgears = 1400 fps
>> bad kernel: glxgears = 300 fps ( same speed with disabled
>drm module )
>>
>> kernel log:
>> glxgears:5775 map pfn expected mapping type write-back for
>> d1000000-d1c80000, got uncached-minus
>> glxgears:5775 freeing invalid memtype d1000000-d1c80000
>>
>
>Have we caught a case of actual overlap, i.e. a driver bug here?
>
This error is similar to one reported by Kevin here.
http://lkml.indiana.edu/hypermail/linux/kernel/0901.0/00970.html
[ 111.775378] X:5010 map pfn expected mapping type write-back for d0000000-d0101000, got write-combining
[ 111.775456] X:5010 freeing invalid memtype d0000000-d0101000
The sequence seems to be somewhat like this
- Kernel driver sets the whole graphics region to uc-minus or write-combining
- There is a remap_pfn_range() to map a portion of this region to user with "write-back" mapping.
Now there may be a MTRR for this region or there may be none. It will depend on specific system and
whether there were available MTRRs or MTRR setting was possible at all.If there are no MTRR settings,
then we have caught a valid aliasing here.
I have reproduced this problem on a local system here and looking for a sane solution....
Thanks,
Venki--
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