linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olof Johansson <olof@lixom.net>
Cc: LinuxPPC-dev <linuxppc-dev@ozlabs.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Paul Mackerras <paulus@samba.org>,
	Jan-Bernd Themann <themann@de.ibm.com>
Subject: Re: [PATCH v2] Force 4K pages for IO addresses.
Date: Tue, 18 Mar 2008 13:43:41 +1100	[thread overview]
Message-ID: <1205808221.26869.207.camel@pasglop> (raw)
In-Reply-To: <20080318003434.GA671@lixom.net>


On Mon, 2008-03-17 at 19:34 -0500, Olof Johansson wrote:
> On Mon, Mar 17, 2008 at 02:54:19PM +1100, Tony Breeds wrote:
> > Currently HEA requires 4K pages for IO resources.  Just set the pages size to
> > IO to 4K.
> 
> Well, that's too bad. Why penalize all platforms for it?
> 
> I.e.: Nack, we use 64K iopages on pa6t and it works well. No need to
> waste tlb and erat space.

We would have to make that pSeries specific for now I suppose...

We don't have a way to know that there "can" be an EHEA right ? It may
not be in the device-tree at boot and dynamically added to the
partition... And we can't dynamically "demote" the ioremap area like we
do for userspace as we have no tracking of bolted entries hashed in
early during boot (I plan to fix that but that will take a while).

Cheers,
Ben.

  reply	other threads:[~2008-03-18  2:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17  3:47 [PATCH] Force 4K pages for IO addresses Tony Breeds
2008-03-17  3:54 ` [PATCH v2] " Tony Breeds
2008-03-18  0:34   ` Olof Johansson
2008-03-18  2:43     ` Benjamin Herrenschmidt [this message]
2008-03-18 14:45       ` Nathan Lynch
2008-03-18 20:31         ` Benjamin Herrenschmidt
2008-03-18 21:52           ` Tony Breeds

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=1205808221.26869.207.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    --cc=themann@de.ibm.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;
as well as URLs for NNTP newsgroup(s).