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: "H. Peter Anvin" <hpa@xxxxxxxxx>
- Date: Sat, 11 Apr 2009 22:21:50 -0700
- Cc: Pavel Machek <pavel@xxxxxx>, Ingo Molnar <mingo@xxxxxxx>, mingo@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, hpa@xxxxxxxxxxxxxxx, rjw@xxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- In-reply-to: <49E0C1AB.2050608@xxxxxxxxxx>
- References: <49DE7F79.4030106@xxxxxxxxx> <tip-7a734e7dd93b9aea08ed51036a9a0e2c9dfd8dac@xxxxxxxxxxxxxx> <20090410080444.GC16512@xxxxxxxxxx> <20090410103934.GA21506@xxxxxxx> <20090410104648.GA31516@xxxxxxxxxx> <20090410112546.GD21506@xxxxxxx> <20090410113824.GA18823@xxxxxxxxxx> <49E0C1AB.2050608@xxxxxxxxxx>
- User-agent: Thunderbird 2.0.0.21 (X11/20090320)
Avi Kivity wrote:
kvm might help detecting these issues, but not in fixing them. If you
isolate the BIOS, then you've prevented corruption, but you've also
prevented it from doing whatever it is it was supposed to do. If you
give it access to memory and the rest of the system, then whatever evil
it has wrought affects the system.
You could try to allow the BIOS access to selected pieces of memory and
hardware, virtualizing the rest, but it seems to me it would be more
like a recipe for a giant headache that a solution.
The main thing you could do is drop or virtualize memory accesses to RAM
it should never access in the first place, like some BIOSes which
scribble over random locations in low memory.
-hpa
--
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
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]