From: Ingo Molnar <mingo@elte.hu>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Venki Pallipadi <venkatesh.pallipadi@intel.com>,
Dave Airlie <airlied@gmail.com>,
"Li, Shaohua" <shaohua.li@intel.com>,
Yinghai Lu <yhlu.kernel@gmail.com>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
Arjan van de Ven <arjan@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Dave Jones <davej@codemonkey.org.uk>
Subject: Re: AGP PAT issue.
Date: Thu, 11 Sep 2008 10:17:02 +0200 [thread overview]
Message-ID: <20080911081702.GA27425@elte.hu> (raw)
In-Reply-To: <48C8259B.7040702@keyaccess.nl>
* Rene Herman <rene.herman@keyaccess.nl> wrote:
> On 22-08-08 22:02, Rene Herman wrote:
>
>> On 22-08-08 06:15, Ingo Molnar wrote:
>
>>> The frontside cache itself is in x86/urgent:
>>>
>>> # 80c5e73: x86: fix Xorg startup/shutdown slowdown with PAT
>>>
>>> ... and should at least solve the symptom that you've hit in practice
>>> (the slowdown), without changing the underlying PAT machinery. (which
>>> would be way too dangerous for v2.6.27)
>>
>> Well, please note that that specific commit only fixes X startup -- it
>> doesn't do anything for shutdown. With only that one, I'm still at 14
>> seconds for X shutdown (first time after boot that is, 5 seconds
>> subsequent shutdowns) versus 1 (or sub 1, feels immediate) normally.
>>
>> It's also a black-screen "hang", so we'll probably be getting a lot of
>> "long hang at shutdown" reports without something additionally for .27.
>>
>> Venki?
>
> Haven't been subcribed to any lists recently and someone was talking
> about "the other thread" before but just noticed that an -rc6 was cut.
>
> Please note that the shutdown issue remains unfixed in it (I'm doing
> my coalescing changes locally).
here's what is pending in tip/x86/pat for v2.6.28:
110e035: x86: make sure the CPA test code's use of _PAGE_UNUSED1 is obvious
c09ff7e: linux-next: fix x86 tree build failure
01de05a: x86: have set_memory_array_{uc,wb} coalesce memtypes, fix
5f310b6: agp: enable optimized agp_alloc_pages methods
c5e147c: x86: have set_memory_array_{uc,wb} coalesce memtypes.
9a79f4f: x86: {reverve,free}_memtype() take a physical address
8b53b57: Merge branch 'x86/urgent' into x86/pat
ab7e792: x86: fix pageattr-test
bd07928: agp: add agp_generic_destroy_pages()
37acee1: agp: generic_alloc_pages()
d75586a: x86, pageattr: introduce APIs to change pageattr of a page array
cacf890: Revert "introduce two APIs for page attribute"
9326d61: Revert "reduce tlb/cache flush times of agpgart memory allocation"
5843d9a: x86, pat: avoid highmem cache attribute aliasing
466ae83: reduce tlb/cache flush times of agpgart memory allocation
1ac2f7d: introduce two APIs for page attribute
012f09e: x86: compile pat debugfs interface only if CONFIG_X86_PAT is set
that includes your coalescing optimizations and fixes. None of that is
really v2.6.27 material i think.
Btw., if you track -tip as per:
http://people.redhat.com/mingo/tip.git/README
you can merge these changes alone into latest -git just by doing:
git merge tip/x86/pat
or you can use tip/master for the full range of pending features and
fixes.
Ingo
next prev parent reply other threads:[~2008-09-11 8:17 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 16:30 AGP and PAT (induced?) problem (on AMD family 6) Rene Herman
2008-08-06 13:51 ` Andreas Herrmann
2008-08-06 20:57 ` Rene Herman
2008-08-11 9:46 ` Rene Herman
2008-08-15 14:22 ` Ingo Molnar
2008-08-15 15:24 ` Rene Herman
2008-08-19 10:11 ` Rene Herman
2008-08-19 10:26 ` Ingo Molnar
2008-08-19 14:19 ` Rene Herman
2008-08-19 19:07 ` Venki Pallipadi
2008-08-19 19:22 ` Rene Herman
2008-08-19 23:28 ` Venki Pallipadi
2008-08-20 10:09 ` Ingo Molnar
2008-08-20 10:04 ` Ingo Molnar
2008-08-20 10:50 ` Rene Herman
2008-08-20 14:27 ` Rene Herman
2008-08-20 19:41 ` Venki Pallipadi
2008-08-20 21:40 ` Rene Herman
2008-08-20 21:46 ` Dave Airlie
2008-08-20 22:16 ` Venki Pallipadi
2008-08-21 3:42 ` Andi Kleen
2008-08-21 21:13 ` Suresh Siddha
2008-08-22 2:12 ` Andi Kleen
2008-08-21 12:06 ` Ingo Molnar
2008-08-21 17:15 ` Rene Herman
2008-08-21 22:10 ` [PATCH] x86: {reverve,free}_memtype() take a physical address Rene Herman
2008-08-21 22:16 ` Pallipadi, Venkatesh
2008-08-21 22:26 ` Rene Herman
2008-08-21 22:57 ` Pallipadi, Venkatesh
2008-08-21 23:06 ` Rene Herman
2008-08-21 23:02 ` [PATCH] x86: have set_memory_array_{uc,wb} coalesce memtypes Rene Herman
2008-08-22 4:15 ` Ingo Molnar
2008-08-22 19:08 ` Venki Pallipadi
2008-08-22 20:15 ` Rene Herman
2008-08-23 15:33 ` Ingo Molnar
2008-08-22 20:02 ` Rene Herman
2008-09-10 19:52 ` AGP PAT issue Rene Herman
2008-09-11 8:17 ` Ingo Molnar [this message]
2008-09-11 8:30 ` Rene Herman
2008-09-13 0:26 ` Pallipadi, Venkatesh
2008-09-13 0:44 ` Rene Herman
2008-10-09 15:53 ` Thomas Hellstrom
2008-10-13 17:10 ` Pallipadi, Venkatesh
2008-10-13 19:26 ` Thomas Hellström
2008-08-20 21:02 ` AGP and PAT (induced?) problem (on AMD family 6) Dave Airlie
2008-08-20 21:16 ` Rene Herman
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=20080911081702.GA27425@elte.hu \
--to=mingo@elte.hu \
--cc=airlied@gmail.com \
--cc=andreas.herrmann3@amd.com \
--cc=arjan@infradead.org \
--cc=davej@codemonkey.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--cc=shaohua.li@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
--cc=yhlu.kernel@gmail.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