| |||||||||||||
KHB: Recovering Device Drivers: From Sandboxing to SurvivingKHB: Recovering Device Drivers: From Sandboxing to SurvivingPosted Jan 26, 2007 13:38 UTC (Fri) by alext (guest, #7589)Parent article: KHB: Recovering Device Drivers: From Sandboxing to Surviving "What we really don'tneed is a lightweight, unintrusive system to not only catch device driver ..." (my change in bold) but it will do when we can't have what we really need which is drivers that work properly.
(Log in to post comments)
KHB: Recovering Device Drivers: From Sandboxing to Surviving Posted Jan 29, 2007 23:09 UTC (Mon) by slamb (guest, #1070) [Link] You're saying we wouldn't need fault isolation/tolerance/recovery if we didn't have faults. That's true, but unless someone comes up with a way to prevent all faults, it's not a useful statement. Barring that, schemes like this are at least interesting, and I'm not sure why parts of it aren't in place. In particular, if someone has a way to make most of the core kernel's memory read-only to drivers at low cost, I'm all for it.
|
|||||||||||||