All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/e6500: TLB miss handler with hardware tablewalk support
Date: Sun, 09 Sep 2012 09:09:01 +1000	[thread overview]
Message-ID: <1347145741.2385.68.camel@pasglop> (raw)
In-Reply-To: <1339722302.9220.175.camel@pasglop>

On Fri, 2012-06-15 at 11:05 +1000, Benjamin Herrenschmidt wrote:
> > -#define MMU_PAGE_COUNT       14
> > +#define MMU_PAGE_2M  6
> > +#define MMU_PAGE_4M  7
> > +#define MMU_PAGE_8M  8
> > +#define MMU_PAGE_16M 9
> > +#define MMU_PAGE_64M 10
> > +#define MMU_PAGE_256M        11
> > +#define MMU_PAGE_1G  12
> > +#define MMU_PAGE_16G 13
> > +#define MMU_PAGE_64G 14
> > +
> > +#define MMU_PAGE_COUNT       15 

BTW. We are getting close to 16 here which is the max since we encode
the size into a 4-bit field in the slice masks on server.

Any chance if/when you respin, to add a BUILD_BUG_ON somewhere to ensure
that we never accidentally break that limit ? (With a comment).

If we need to scavenge a size, we can always get rid of the AP one, it's
not actually useful (we'll have to find a different way to store the
encodings on server if we ever support multiple size per segment).

Cheers,
Ben.

  parent reply	other threads:[~2012-09-08 23:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 23:41 [PATCH 2/2] powerpc/e6500: TLB miss handler with hardware tablewalk support Scott Wood
2012-06-15  1:05 ` Benjamin Herrenschmidt
2012-06-15 16:50   ` Scott Wood
2012-06-15 22:02     ` Benjamin Herrenschmidt
2012-07-19 20:12   ` Scott Wood
2012-09-08 23:09   ` Benjamin Herrenschmidt [this message]
2012-09-07  4:41 ` Benjamin Herrenschmidt
     [not found]   ` <504A4C3D.3040709@freescale.com>
2012-09-07 23:01     ` Scott Wood
2012-09-07 23:50       ` Benjamin Herrenschmidt
2012-09-08  0:55         ` Nishanth Aravamudan
2012-09-08 10:15           ` Benjamin Herrenschmidt
2012-09-11  0:26         ` Scott Wood
2012-09-11 17:06 ` Caraman Mihai Claudiu-B02008
2012-09-11 17:24   ` Scott Wood

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=1347145741.2385.68.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.