On Wed, Sep 28, 2005 at 07:26:43PM +0200, Blaisorblade wrote:
> I'm not sure that would help anyway - if the host memory is full, it's full.
> It's just matter of waiting and retrying.
This isn't a matter of waiting and retrying. We use pages that are already
known to be good, and the rest go on a "bad pages" list and not freed, so
no one will try to use them again.
> I don't think the host would SIGBUS again on the same page specifically - or
> better, I'm almost sure this is not done.
> So, I don't see the reason for that. Catching SIGSEGV/SIGBUS is ok, taking
> another page is bad.
Catching SIGSEGV/SIGBUS at some random place in the kernel after it kmalloced
a bad page is OK? I don't think so.
The only way to keep the kernel running at that point is to get another
page and hope that it's OK. And if it's not, you try again.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
