mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Olaf Hering <olh@suse.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>,
	linuxppc64-dev <linuxppc64-dev@ozlabs.org>
Subject: Re: [PATCH] ppc64: 64K pages support
Date: Wed, 16 Nov 2005 15:16:42 -0800	[thread overview]
Message-ID: <1132183002.24066.90.camel@localhost.localdomain> (raw)
In-Reply-To: <20051116230820.GA29068@suse.de>

On Thu, 2005-11-17 at 00:08 +0100, Olaf Hering wrote:
>  On Wed, Nov 09, Badari Pulavarty wrote:
> 
> > On Thu, 2005-11-10 at 09:01 +1100, Benjamin Herrenschmidt wrote:
> > > > I didn't have any luck on 2.6.14-git12 either.
> > > > I tried 64k page support on my P570. 
> > > > 
> > > > Here are the console messages:
> > > 
> > > What distro do you use in userland ? Some older glibc versions have a
> > > bug that cause issues with 64k pages, though it generally happens with
> > > login blowing up, not init ...
> > 
> > SLES9 (could be SLES9 SP1).
> 
> Can you double check? rpm -qi glibc | head should be enough.
> Would be bad if SP2 or SP3 does not work with 64k.
> 

I think I am using SLES9. Planning to update to SP3.

# rpm -qi glibc | head
Name        : glibc                        Relocations: (not
relocatable)
Version     : 2.3.3                             Vendor: SuSE Linux AG,
Nuernberg, Germany
Release     : 98.28                         Build Date: Wed Jun 30
15:55:45 2004
Install date: Wed Jul  6 17:24:44 2005      Build Host:
gooseberry.suse.de
Group       : System/Libraries              Source RPM:
glibc-2.3.3-98.28.src.rpm
Size        : 6161800                          License: GPL, LGPL
Signature   : DSA/SHA1, Wed Jun 30 16:00:21 2004, Key ID
a84edae89c800aca
Packager    : http://www.suse.de/feedback
URL         : http://www.gnu.org/software/libc/libc.html
Summary     : The standard shared libraries (from the GNU C Library)

Thanks,
Badari


  reply	other threads:[~2005-11-16 23:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1130915220.20136.14.camel@gaston>
2005-11-02  7:23 ` Benjamin Herrenschmidt
2005-11-03  3:16   ` Paul Mackerras
2005-11-03  5:26     ` ppc64: Fix bug in SLB miss handler for hugepages David Gibson
2005-11-05  0:38   ` [PATCH] ppc64: 64K pages support Christoph Hellwig
2005-11-05  0:44     ` Benjamin Herrenschmidt
2005-11-05  6:37       ` Dave Airlie
2005-11-09 17:21   ` Christoph Hellwig
2005-11-09 20:17     ` Mike Kravetz
2005-11-09 20:32       ` Benjamin Herrenschmidt
2005-11-09 21:59         ` Badari Pulavarty
2005-11-09 22:01           ` Benjamin Herrenschmidt
2005-11-09 22:07             ` Badari Pulavarty
2005-11-16 23:08               ` Olaf Hering
2005-11-16 23:16                 ` Badari Pulavarty [this message]
2005-11-16 23:27                   ` Olaf Hering
2005-11-17  1:32                     ` Andreas Schwab
     [not found]                   ` <ac0de0c00511161557o379fbc71le6d5c5e2ff9a314b@mail.gmail.com>
2005-11-17  0:33                     ` Badari Pulavarty
2005-11-09 20:36     ` Benjamin Herrenschmidt
2005-11-09 22:15     ` Paul Mackerras
2005-11-09 23:42     ` Benjamin Herrenschmidt

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=1132183002.24066.90.camel@localhost.localdomain \
    --to=pbadari@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=olh@suse.de \
    --cc=torvalds@osdl.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

Powered by JetHome