From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Alan Jenkins" <alan-jenkins@tuffmail.co.uk>,
"Ingo Molnar" <mingo@elte.hu>,
linux-kernel@vger.kernel.org, "Hugh Dickens" <hugh@veritas.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: [PATCH 0 of 3] Low memory corruption detection and workaround
Date: Tue, 9 Sep 2008 04:44:49 +1000 [thread overview]
Message-ID: <200809090444.50038.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <48C5570B.7050109@goop.org>
On Tuesday 09 September 2008 02:47, Jeremy Fitzhardinge wrote:
> Nick Piggin wrote:
> > Why not high memory as well? We put page tables there too...
>
> Well, the specific problem is that the BIOS appears to corrupt low
> memory. It might corrupt other memory anywhere, but that would be
> pretty pathologically evil. The assumption is that it gets away with it
> because its memory that Windows doesn't otherwise use or something.
OK, fine, sorry I didn't follow the thread back.
next prev parent reply other threads:[~2008-09-08 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <patchbomb.1220777491@localhost>
[not found] ` <72081a970effa1a32861.1220777494@localhost>
2008-09-07 9:11 ` [PATCH 3 of 3] x86: clean up memory corruption check and add more kernel parameters Ingo Molnar
2008-09-07 9:37 ` [PATCH 4/3] x86: default corruption check to off, but put parameter default in Kconfig Jeremy Fitzhardinge
2008-09-07 15:40 ` Ingo Molnar
[not found] ` <20080907155030.GA24741@elte.hu>
2008-09-07 15:51 ` Ingo Molnar
2008-09-07 21:54 ` [PATCH 5/3] x86: fix compile error with corruption checking disabled Jeremy Fitzhardinge
2008-09-08 18:03 ` Ingo Molnar
2008-09-07 15:24 ` [PATCH 0 of 3] Low memory corruption detection and workaround Alan Jenkins
2008-09-08 11:23 ` Nick Piggin
2008-09-08 16:47 ` Jeremy Fitzhardinge
2008-09-08 17:01 ` Alan Cox
2008-09-08 18:44 ` Nick Piggin [this message]
2008-09-08 10:52 ` Hugh Dickins
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=200809090444.50038.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zajec5@gmail.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®