[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090412163356.GA2392@elte.hu>
Date: Sun, 12 Apr 2009 18:33:56 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: "H. Peter Anvin" <hpa@...or.com>, Avi Kivity <avi@...hat.com>,
Pavel Machek <pavel@....cz>, mingo@...hat.com,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
hpa@...ux.intel.com, rjw@...k.pl, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls --
infrastructure
* Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> Sure, go ahead and wrap them in some kind of "save and restore all
> registers" wrapping, but nothing fancier than that. It would just
> be overkill, and likely to break more than it fixes.
Yeah. I only brought up the virtualization thing as a hypothetical:
"if" corrupting the main OS ever became a widespread problem. Then i
made the argument that this is unlikely to happen, because Windows
will be affected by it just as much. (while register state
corruptions might go unnoticed much more easily, just via the random
call-environment clobbering of registers by Windows itself.)
The only case where i could see virtualization to be useful is the
low memory RAM corruption pattern that some people have observed.
The problem with it, it happens on s2ram transitions, and that is
driven by SMM mainly - which is a hypervisor sitting on top of all
the other would-be-hypervisors and thus not virtualizable.
Which leaves us without a single practical case. So it's not going
to happen.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists