From: Roland Dreier <roland@topspin.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: jmerkey@comcast.net, alan@lxorguk.ukuu.org.uk,
wli@holomorphy.com, linux-kernel@vger.kernel.org,
jmerkey@drdos.com
Subject: Re: 1GB/2GB/3GB User Space Splitting Patch 2.6.8.1 (PSEUDO SPAM)
Date: Mon, 30 Aug 2004 11:28:56 -0700 [thread overview]
Message-ID: <524qmk7a53.fsf@topspin.com> (raw)
In-Reply-To: <20040830111019.5ddc99ab.rddunlap@osdl.org> (Randy Dunlap's message of "Mon, 30 Aug 2004 11:10:19 -0700")
Randy> It doesn't barf on me. I added one other patch on top of
Randy> yours: one from Roland Dreier, for
Randy> arch/i386/kernel/doublefault.c [below].
BTW, I can't imagine my patch would make any difference -- it only
affects what gets printed out right before the kernel locks up on a
double fault.
I am running a 2.6.8.1 kernel with PAGE_OFFSET set to 0xb000000 on my
desktop with USB mouse and keyboard (and 1 GB of RAM) with no problems.
- R.
next prev parent reply other threads:[~2004-08-30 18:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 5:56 1GB/2GB/3GB User Space Splitting Patch 2.6.8.1 (PSEUDO SPAM) jmerkey
2004-08-30 18:10 ` Randy.Dunlap
2004-08-30 18:28 ` Roland Dreier [this message]
2004-09-22 18:52 ` Timothy Miller
2004-09-22 18:51 ` Roland Dreier
2004-09-22 20:22 ` Timothy Miller
2004-09-27 14:55 ` Roland Dreier
-- strict thread matches above, loose matches on Subject: below --
2004-08-31 22:50 jmerkey
2004-08-30 4:01 jmerkey
2004-08-30 4:35 ` Randy.Dunlap
2004-08-26 23:47 linux
2004-08-26 21:08 jmerkey
2004-08-26 21:43 ` William Lee Irwin III
2004-08-26 20:24 jmerkey
2004-08-26 20:38 ` William Lee Irwin III
2004-08-26 21:41 ` Dave Jones
2004-08-26 4:21 jmerkey
2004-08-26 4:33 ` William Lee Irwin III
2004-08-26 4:46 ` Roland Dreier
2004-08-26 4:49 ` William Lee Irwin III
2004-08-26 8:40 ` Ryan Cumming
2004-08-29 12:48 ` Alan Cox
2004-08-29 16:42 ` William Lee Irwin III
2004-08-29 15:45 ` Alan Cox
2004-08-29 17:00 ` William Lee Irwin III
2004-08-26 4:38 ` Martin J. Bligh
2004-08-26 4:42 ` Roland Dreier
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=524qmk7a53.fsf@topspin.com \
--to=roland@topspin.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jmerkey@comcast.net \
--cc=jmerkey@drdos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=wli@holomorphy.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.