From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Avi Kivity <avi@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Pavel Machek <pavel@ucw.cz>,
mingo@redhat.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, hpa@linux.intel.com, rjw@sisk.pl,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
Date: Mon, 13 Apr 2009 09:27:20 -0700 [thread overview]
Message-ID: <49E367E8.7080202@zytor.com> (raw)
In-Reply-To: <20090413042459.GA6479@elte.hu>
Ingo Molnar wrote:
>> Yes, we could do memory checks, and ... hey, we already do that:
>>
>> bb577f9: x86: add periodic corruption check
>> 5394f80: x86: check for and defend against BIOS memory corruption
>>
>> ... and i seem to be the one who implemented it! ;-)
>
> s/implemented/merged+fixed :-)
Actually, what would probably be more productive than trying to track
corruption would be to drop the low 1 MB of memory before suspend to RAM
- make sure that it is as close to completely unused as possible.
All *known* cases of low memory corruption are either boot time or due
to s2ram.
I don't know how realistic it is to make the low 1 MB completely unused
over the s2ram cycle. The trivial way of doing it is to simply not use
it -- it's only some 600K after all; a more sophisticated way would be
to explicitly constrain it to transient uses that would be dead at s2ram.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-04-13 16:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 23:06 [PATCH 0/6] x86, setup: "glove box" BIOS interrupts H. Peter Anvin
2009-04-09 23:12 ` [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure H. Peter Anvin
2009-04-10 8:04 ` Pavel Machek
2009-04-10 10:39 ` Ingo Molnar
2009-04-10 10:46 ` Pavel Machek
2009-04-10 11:25 ` Ingo Molnar
2009-04-10 11:38 ` Pavel Machek
2009-04-10 11:49 ` Ingo Molnar
2009-04-11 16:13 ` Avi Kivity
2009-04-12 5:21 ` H. Peter Anvin
2009-04-12 14:01 ` Ingo Molnar
2009-04-12 14:39 ` Avi Kivity
2009-04-12 14:59 ` Linus Torvalds
2009-04-12 16:33 ` Ingo Molnar
2009-04-12 18:57 ` Avi Kivity
2009-04-13 4:16 ` Ingo Molnar
2009-04-13 4:24 ` Ingo Molnar
2009-04-13 16:27 ` H. Peter Anvin [this message]
2009-04-13 16:57 ` Pavel Machek
2009-04-13 17:00 ` H. Peter Anvin
2009-04-13 18:34 ` Alan Jenkins
2009-04-13 19:08 ` H. Peter Anvin
2009-04-14 0:06 ` Ingo Molnar
2009-04-14 4:42 ` H. Peter Anvin
2009-04-14 9:03 ` Jeremy Fitzhardinge
2009-04-14 15:59 ` H. Peter Anvin
2009-04-13 6:44 ` Avi Kivity
2009-04-12 17:51 ` H. Peter Anvin
2009-04-10 17:17 ` H. Peter Anvin
2009-04-10 17:19 ` H. Peter Anvin
2009-04-09 23:13 ` [tip:x86/setup] x86, setup: "glove box" BIOS interrupts in the core boot code H. Peter Anvin
2009-04-09 23:13 ` [tip:x86/setup] x86, setup: "glove box" BIOS interrupts in the APM code H. Peter Anvin
2009-04-09 23:13 ` [tip:x86/setup] x86, setup: "glove box" BIOS interrupts in the EDD code H. Peter Anvin
2009-04-09 23:13 ` [tip:x86/setup] x86, setup: "glove box" BIOS interrupts in the MCA code H. Peter Anvin
2009-04-09 23:13 ` [tip:x86/setup] x86, setup: "glove box" BIOS interrupts in the video code H. Peter Anvin
2009-04-10 8:05 ` Pavel Machek
2009-04-10 18:05 ` [PATCH 0/6] x86, setup: "glove box" BIOS interrupts Rafael J. Wysocki
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=49E367E8.7080202@zytor.com \
--to=hpa@zytor.com \
--cc=avi@redhat.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 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.