From: ebiederm@xmission.com (Eric W. Biederman)
To: Anton Altaparmakov <aia21@cantab.net>
Cc: torvalds@transmeta.com (Linus Torvalds),
linux-kernel@vger.kernel.org (Linux Kernel)
Subject: Re: [BK PATCH 2.5] fs/binfmt_aout.c: Use PAGE_ALIGN_LL() on 64-bit values
Date: 28 Jul 2002 13:35:28 -0600 [thread overview]
Message-ID: <m1n0sbhchr.fsf@frodo.biederman.org> (raw)
In-Reply-To: <5.1.0.14.2.20020728194633.04207dd0@pop.cus.cam.ac.uk>
Anton Altaparmakov <aia21@cantab.net> writes:
> At 18:59 28/07/02, Eric W. Biederman wrote:
> >Anton Altaparmakov <aia21@cantab.net> writes:
> > > Following from previous patch which introduced PAGE_ALIGN_LL, this
> > > one fixes a bug in fs/binfmt_aout.c which was using PAGE_ALIGN
> > > on 64-bit values... It now uses PAGE_ALIGN_LL.
> > >
> > > Patch together with the other two patches available from:
> > >
> > > bk pull http://linux-ntfs.bkbits.net/linux-2.5-pm
> >
> >Huh?
> >
> >All virtual addresses on 32bit platforms are 32bit, as are all lengths
> >of address space.
>
> I thought (intel) CPUs did 48-bit addressing? How do we support 32GiB of RAM?
> With pure 32-bit addressing it would be limited to 4GiB only... No? (Of course I
>
> am probably confusing varius types of addresses...)
Hammers and Alphas have 48bit virtual and 40bit physical, in the
current implementations. The most common 48bit address though is that
ide recently moved from 28bit sector addresses to 48bit sector addresses.
> >Unless you are running a 32bit kernel with a 64bit user space,
> >which is simply crazy, unless you are stuck doing it that way.
>
> The code is still broken. The values ARE 64-bit (check the struct definitions if
> you don't believe me).
I just did. The values are per arch, but at least for X86 the values are
unsigned int. Which is 32bits..
Eric
next prev parent reply other threads:[~2002-07-28 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 13:44 Anton Altaparmakov
2002-07-28 17:59 ` Eric W. Biederman
2002-07-28 18:55 ` Anton Altaparmakov
2002-07-28 19:18 ` Christoph Hellwig
2002-07-28 19:35 ` Eric W. Biederman [this message]
2002-07-29 0:31 ` Anton Altaparmakov
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=m1n0sbhchr.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®