Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	David Daney <ddaney@caviumnetworks.com>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: Kernel crash in 2.6.32.6 / bcm1480 with 16k page size
Date: Mon, 1 Feb 2010 13:12:17 -0800	[thread overview]
Message-ID: <1265058737.5825.55.camel@groeck-laptop> (raw)
In-Reply-To: <20100201204912.GC17381@linux-mips.org>

On Mon, 2010-02-01 at 15:49 -0500, Ralf Baechle wrote:
> On Mon, Feb 01, 2010 at 12:21:17PM -0800, Guenter Roeck wrote:
> 
> > > Write a value with all bits set to c0_entryhi, then read it back again.
> > > The set bits in the VPN2 bitfield will indicate the size of the virtual
> > > address range supported.  The MIPS64 documentation also calls this value
> > > SEGBITS.  The nice thing about this probe is that it is supported for
> > > all 64-bit MIPS processors except the R8000 which has an entirely different
> > > TLB scheme anyway.
> > 
> > Are you sure that this doesn't work for the R8000 ? From the user's
> > manual (section 2.1.9, EntryHi) it looks like it should work.
> 
> The probe itself will work if it's carefully written not to get fooled by
> difference in bits 12..18 but that's easy) but still the R8000 has a fairly
> different TLB architecture which Linux doesn't support - the machines are
> rare and none of the active developers has one.
> 
Looks like my code should work. I'll send out a patch in a couple of
minutes.

Guenter

  reply	other threads:[~2010-02-01 21:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 15:55 Kernel crash in 2.6.32.6 / bcm1480 with 16k page size Guenter Roeck
2010-01-29 13:24 ` Ralf Baechle
2010-01-29 15:12   ` Guenter Roeck
2010-01-29 17:11     ` David Daney
2010-01-29 18:06       ` Ralf Baechle
2010-01-29 18:21         ` Guenter Roeck
2010-01-30  2:05           ` Ralf Baechle
2010-01-30 21:34             ` Guenter Roeck
2010-01-31  3:19               ` Guenter Roeck
2010-01-29 18:39         ` Guenter Roeck
2010-01-29 18:56           ` David Daney
2010-01-29 19:25             ` Guenter Roeck
2010-01-29 19:28               ` David Daney
2010-01-29 19:58                 ` Guenter Roeck
2010-01-31  9:10                   ` Maciej W. Rozycki
2010-01-31 16:55                     ` Guenter Roeck
2010-02-01  2:18                       ` Ralf Baechle
2010-02-01 14:50                         ` Maciej W. Rozycki
2010-02-01 15:26                           ` Ralf Baechle
2010-02-01 23:11                             ` Maciej W. Rozycki
2010-02-01 15:04                         ` Guenter Roeck
2010-02-01 20:21                         ` Guenter Roeck
2010-02-01 20:49                           ` Ralf Baechle
2010-02-01 21:12                             ` Guenter Roeck [this message]
2010-01-29 20:00                 ` Guenter Roeck
2010-01-29 20:23                   ` David Daney
2010-01-29 22:19                     ` Guenter Roeck
2010-01-29 18:24       ` Guenter Roeck

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=1265058737.5825.55.camel@groeck-laptop \
    --to=guenter.roeck@ericsson.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=ralf@linux-mips.org \
    /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