Re: [patch 0/6] Strong Access Ordering page attributes for POWER7

2008-07-07 Thread Benjamin Herrenschmidt
On Mon, 2008-07-07 at 16:23 -0500, Joel Schopp wrote: > >> We haven't defined a user-visible feature bit (and besides, we're really > >> getting short on these...). This is becoming a bit of concern btw (the > >> running out of bits). Maybe we should start defining an AT_HWCAP2 for > >> powerpc and

Re: [patch 0/6] Strong Access Ordering page attributes for POWER7

2008-07-07 Thread Joel Schopp
We haven't defined a user-visible feature bit (and besides, we're really getting short on these...). This is becoming a bit of concern btw (the running out of bits). Maybe we should start defining an AT_HWCAP2 for powerpc and get libc updated to pick it up ? Joel, Any thoughts? Is it a r

Re: [patch 0/6] Strong Access Ordering page attributes for POWER7

2008-07-07 Thread Dave Kleikamp
On Fri, 2008-07-04 at 09:39 +1000, Benjamin Herrenschmidt wrote: > On Wed, 2008-06-18 at 17:32 -0500, [EMAIL PROTECTED] wrote: > > Andrew, > > > > The first patch in this series hits architecture independent code, but the > > rest is contained in the powerpc subtree. Could you pick up the first >

Re: [patch 0/6] Strong Access Ordering page attributes for POWER7

2008-07-03 Thread Benjamin Herrenschmidt
On Wed, 2008-06-18 at 17:32 -0500, [EMAIL PROTECTED] wrote: > Andrew, > > The first patch in this series hits architecture independent code, but the > rest is contained in the powerpc subtree. Could you pick up the first > patch into -mm? I can send the rest of them through the powerpc git tree.

[patch 0/6] Strong Access Ordering page attributes for POWER7

2008-06-18 Thread shaggy
Andrew, The first patch in this series hits architecture independent code, but the rest is contained in the powerpc subtree. Could you pick up the first patch into -mm? I can send the rest of them through the powerpc git tree. The first patch and the rest of the set are independent and can be me