From: Dave Hansen <haveblue@us.ibm.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Jamie Lokier <jamie@shareable.org>,
Roland McGrath <roland@redhat.com>,
Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 uaccess to fixmap pages
Date: Fri, 09 May 2003 10:16:30 -0700 [thread overview]
Message-ID: <3EBBE26E.9090606@us.ibm.com> (raw)
In-Reply-To: Pine.LNX.4.44.0305090944420.9705-100000@home.transmeta.com
Linus Torvalds wrote:
> On Fri, 9 May 2003, Dave Hansen wrote:
>
>>We've been playing with patches in the -mjb tree which make PAGE_OFFSET
>>and TASK_SIZE move to some weird values. I have it to the point where I
>>could do a 3.875:0.125 user:kernel split.
>
> That's still not "weird" in the current sense.
>
> We've always (well, for a long time) been able to handle a TASK_SIZE that
> has a 111..00000 pattern - and in fact we used to _depend_ on that kind of
> pattern, because macros like "virt_to_phys()" were simple bitwise-and
> operations. There may be some code in the kernel that still depends on
> that kind of bitwise operation with TASK_SIZE.
>
> Your 3.875:0.125 split still fits that pattern, and thus doesn't create
> any new cases.
>
> In contrast, a TASK_SIZE of 0xc1000000 can no longer just "mask off" the
> kernel address bits. And _that_ is what I meant with "strange value".
Ahhh, weird*er* :)
These patches at least address a small class of problems where it is
assumed that the kernel pagetable entries start at the beginning of a
pmd. Anyway, 2.5.68-mjb3 boots with a 0xE1000000 PAGE_OFFSET with PAE
on a 4GB machine. It does "just work", at least in Martin's tree.
3343MB HIGHMEM available.
368MB LOWMEM available.
elm3b82:~# cat /proc/meminfo
MemTotal: 3758468 kB
MemFree: 3728368 kB
Buffers: 1696 kB
Cached: 8184 kB
SwapCached: 0 kB
Active: 7640 kB
Inactive: 4936 kB
HighTotal: 3424228 kB
HighFree: 3412224 kB
LowTotal: 334240 kB
LowFree: 316144 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 304 kB
Writeback: 0 kB
Mapped: 5900 kB
Slab: 6292 kB
Committed_AS: 7024 kB
PageTables: 472 kB
VmallocTotal: 114680 kB
VmallocUsed: 2400 kB
VmallocChunk: 112280 kB
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2003-05-09 17:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 2:03 [PATCH] i386 uaccess to fixmap pages Roland McGrath
2003-05-09 4:31 ` Andrew Morton
2003-05-09 8:55 ` Roland McGrath
2003-05-09 9:19 ` Andrew Morton
2003-05-09 9:40 ` Roland McGrath
2003-05-09 10:43 ` Roland McGrath
2003-05-09 11:42 ` Dave Jones
2003-05-09 11:55 ` Alan Cox
2003-05-09 12:40 ` Jamie Lokier
2003-05-09 16:06 ` Linus Torvalds
2003-05-09 16:38 ` Dave Hansen
2003-05-09 15:55 ` Martin J. Bligh
2003-05-09 18:20 ` William Lee Irwin III
2003-05-09 16:48 ` Linus Torvalds
2003-05-09 17:16 ` Dave Hansen [this message]
2003-05-10 3:26 ` H. Peter Anvin
2003-05-10 15:31 ` Jamie Lokier
2003-05-10 17:23 ` Ulrich Drepper
2003-05-10 19:23 ` H. Peter Anvin
2003-05-10 20:52 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 17:28 Chuck Ebbert
2003-05-09 17:49 ` Linus Torvalds
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=3EBBE26E.9090606@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=akpm@digeo.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--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