public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Fisher <bug-track@fisher-privat.net>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	venkatesh.pallipadi@intel.com, jbarnes@virtuousgeek.org,
	keithp@keithp.com, airlied@gmail.com
Subject: Re: [Bug 10328] New: [regression] performance drop for glx
Date: Sat, 26 Apr 2008 13:43:57 +0200	[thread overview]
Message-ID: <1209210237.4583.4.camel@zwerg> (raw)
In-Reply-To: <20080426000722.GJ14062@linux-os.sc.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]

Am Freitag, den 25.04.2008, 17:07 -0700 schrieb Suresh Siddha:
> On Fri, Apr 25, 2008 at 07:35:23AM +0200, Alexey Fisher wrote:
> > > >> On Tue, 25 Mar 2008 15:11:15 -0700 (PDT)
> > > >> bugme-daemon@bugzilla.kernel.org wrote:
> > > >>
> > > >>> http://bugzilla.kernel.org/show_bug.cgi?id=10328
> > > >>>
> > > >>>            Summary: [regression] performance drop for glx
> > > > 
> > > > Alexey, Can you please try the appended patch?
> > > > 
> > > > Andrew, can you please push the appended patch for 2.6.25? Thanks.
> > > > ---
> > > > 
> > 
> > 
> > This issue come again with commit:
> > 
> > commit 2e5d9c857d4e6c9e7b7d8c8c86a68a7842d213d6
> > Author: venkatesh.pallipadi@intel.com <venkatesh.pallipadi@intel.com>
> > Date:   Tue Mar 18 17:00:14 2008 -0700
> > 
> >     x86: PAT infrastructure patch
> > 
> >     Sets up pat_init() infrastructure.
> > 
> 
> Alexey, Sorry. I missed posting a fix in the post PAT series for this issue. Can you
> please try the appended patch and Ack?
> 
> copying X folks get their attention and their Ack on the patch and next steps outlined.
> 
> Thanks.
> ---
> 
> [patch] use UC minus for ioremap(), ioremap_nocache() and pci_mmap_page_range()
> 
> Use UC_MINUS for ioremap(), ioremap_nocache() instead of strong UC.
> Once all the X drivers move to ioremap_wc(), we can go back to strong
> UC semantics for ioremap() and ioremap_nocache().
> 

Thank you. This patch working.

Ack ?

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-04-26 11:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10328-27@http.bugzilla.kernel.org/>
2008-03-25 22:28 ` [Bug 10328] New: [regression] performance drop for glx Andrew Morton
2008-03-26  0:39   ` Suresh Siddha
2008-03-26  4:42     ` Arjan van de Ven
2008-04-25  5:35       ` Alexey Fisher
2008-04-26  0:07         ` Suresh Siddha
2008-04-26 11:43           ` Alexey Fisher [this message]
2008-04-28 16:34           ` Ingo Molnar
2008-03-26  5:29     ` Ingo Molnar
2008-03-26 17:55       ` Suresh Siddha

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=1209210237.4583.4.camel@zwerg \
    --to=bug-track@fisher-privat.net \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=keithp@keithp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --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