Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
- From: Ingo Molnar <mingo@xxxxxxx>
- Date: Mon, 13 Apr 2009 06:24:59 +0200
- Cc: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Pavel Machek <pavel@xxxxxx>, mingo@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, hpa@xxxxxxxxxxxxxxx, rjw@xxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <20090413041625.GF11652@xxxxxxx>
- References: <20090410103934.GA21506@xxxxxxx> <20090410104648.GA31516@xxxxxxxxxx> <20090410112546.GD21506@xxxxxxx> <20090410113824.GA18823@xxxxxxxxxx> <49E0C1AB.2050608@xxxxxxxxxx> <49E17A6E.5000104@xxxxxxxxx> <alpine.LFD.2.00.0904120754240.4583@xxxxxxxxxxxxxxxxxxxxx> <20090412163356.GA2392@xxxxxxx> <49E2398A.3050405@xxxxxxxxxx> <20090413041625.GF11652@xxxxxxx>
- User-agent: Mutt/1.5.18 (2008-05-17)
* Ingo Molnar <mingo@xxxxxxx> wrote:
>
> * Avi Kivity <avi@xxxxxxxxxx> wrote:
>
> > Ingo Molnar 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.
> >
> > You could easily check that by checksumming pages (or actually
> > copying them to high memory) before the call, and verifying after
> > the call.
>
> 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 :-)
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
- References:
- Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
- Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
- Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
- Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
- Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
- Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
- Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
- Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
- Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
- Re: [tip:x86/setup] x86, setup: "glove box" BIOS calls -- infrastructure
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]