public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Winchester <kjwinchester@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: venkatesh.pallipadi@intel.com, tglx@linutronix.de, hpa@zytor.com,
	linux-kernel@vger.kernel.org, suresh.b.siddha@intel.com
Subject: Re: [patch 0/6] PAT fixes/cleanup following the pfnmap changes
Date: Sun, 11 Jan 2009 12:59:44 -0400	[thread overview]
Message-ID: <496A2580.2080103@gmail.com> (raw)
In-Reply-To: <20090111020508.GA29153@elte.hu>

Ingo Molnar wrote:
> * Kevin Winchester <kjwinchester@gmail.com> wrote:
> 
>> venkatesh.pallipadi@intel.com wrote:
>>> Individual patch header has descriptions.
>>>
>> $ git am Patches
>> Applying: x86 PAT: change track_pfn_vma_new to take pgprot_t pointer param
>> error: patch failed: mm/memory.c:1604
>> error: mm/memory.c: patch does not apply
>> Patch failed at 0001.
>> When you have resolved this problem run "git am --resolved".
>> If you would prefer to skip this patch, instead run "git am --skip".
>> To restore the original branch and stop patching run "git am --abort".
>>
>> These do not apply for me to latest Linus git, which is the tree where I 
>> experienced the problem.  Is there some way to fuzz them to get them to 
>> apply?
> 
> Could you check tip/master:
> 
>   http://people.redhat.com/mingo/tip.git/README
> 
> do you still get the messages? [ Btw., did you also experience any 3D 
> performance problems that are solved via Venki's fixes in tip/master? ]
> 

I just checked tip/master, and I do still get the messages:

[   66.895807] X:5022 map pfn expected mapping type write-back for d0000000-d0101000, got write-combining
[   66.895873] X:5022 freeing invalid memtype d0000000-d0101000

As for 3D performance issues, glxgears without any other applications running gives:

    457 frames in 5.0 seconds = 91.312 FPS
    475 frames in 5.0 seconds = 94.887 FPS
    478 frames in 5.0 seconds = 95.411 FPS

I can't say for sure, but I expect those numbers should be much higher for a 3D accelerated radeon card (even if it is a little old):

    01:00.0 VGA compatible controller: ATI Technologies Inc M9+ 5C61 [Radeon Mobility 9200 (AGP)] (rev 01)

glxinfo gives:

    direct rendering: Yes


Anything else I can try?

-- 
Kevin Winchester

  reply	other threads:[~2009-01-11 17:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10  0:13 [patch 0/6] PAT fixes/cleanup following the pfnmap changes venkatesh.pallipadi
2009-01-10  0:13 ` [patch 1/6] x86 PAT: remove PFNMAP type on track_pfn_vma_new() error venkatesh.pallipadi
2009-01-10  0:13 ` [patch 2/6] x86 PAT: consolidate old memtype new memtype check into a function venkatesh.pallipadi
2009-01-10  0:13 ` [patch 3/6] x86 PAT: change track_pfn_vma_new to take pgprot_t pointer param venkatesh.pallipadi
2009-01-10  0:13 ` [patch 4/6] x86 PAT: return compatible mapping to remap_pfn_range callers venkatesh.pallipadi
2009-01-10  0:13 ` [patch 5/6] x86 PAT: ioremap_wc should take resource_size_t parameter venkatesh.pallipadi
2009-01-10  0:13 ` [patch 6/6] x86 PAT: Remove CPA WARN_ON for zero pte venkatesh.pallipadi
2009-01-10 13:02 ` [patch 0/6] PAT fixes/cleanup following the pfnmap changes Kevin Winchester
2009-01-11  2:05   ` Ingo Molnar
2009-01-11 16:59     ` Kevin Winchester [this message]
2009-01-15  0:02     ` Kevin Winchester

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=496A2580.2080103@gmail.com \
    --to=kjwinchester@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox