From: Andi Kleen <andi@firstfloor.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Ingo Molnar <mingo@elte.hu>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Christoph Hellwig <hch@infradead.org>,
hpa@zytor.com, tglx@linutronix.de, linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [patch 2/2] x86, fpu: lazy allocation of FPU area - v3
Date: 06 Mar 2008 21:52:48 +0100 [thread overview]
Message-ID: <87r6enfucf.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080306202446.GA4225@ucw.cz>
Pavel Machek <pavel@ucw.cz> writes:
>
> Well, we should not be sending SIGSEGV...? SIGBUS would be cleaner, or
> SIGKILL... what happens when userland tries to catch this one?
When this happens the kernel is already in a severe out of memory
situation and no matter what you do user land will not be able
to handle this well.
-Andi
next prev parent reply other threads:[~2008-03-06 20:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 23:02 [patch 1/2] x86, fpu: split FPU state from task struct - v3 Suresh Siddha
2008-03-03 23:02 ` [patch 2/2] x86, fpu: lazy allocation of FPU area " Suresh Siddha
2008-03-04 1:20 ` Christoph Hellwig
2008-03-04 1:43 ` Suresh Siddha
2008-03-04 10:32 ` Ingo Molnar
2008-03-04 17:55 ` Suresh Siddha
2008-03-05 19:47 ` Pavel Machek
2008-03-06 15:51 ` Ingo Molnar
2008-03-06 19:10 ` Suresh Siddha
2008-03-06 20:24 ` Pavel Machek
2008-03-06 20:52 ` Andi Kleen [this message]
2008-03-07 12:29 ` H. Peter Anvin
2008-03-07 13:06 ` Arjan van de Ven
2008-03-07 13:18 ` Andi Kleen
2008-03-07 13:20 ` Arjan van de Ven
2008-03-07 13:27 ` Andi Kleen
2008-03-05 19:48 ` Pavel Machek
2008-03-06 19:26 ` Suresh Siddha
2008-03-06 21:21 ` Pavel Machek
2008-03-04 1:18 ` [patch 1/2] x86, fpu: split FPU state from task struct " Christoph Hellwig
2008-03-04 1:36 ` Suresh Siddha
2008-03-04 8:20 ` Ingo Molnar
2008-03-06 12:39 ` Christoph Hellwig
2008-03-04 10:28 ` Ingo Molnar
2008-03-04 17:59 ` Suresh Siddha
2008-03-04 20:53 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r6enfucf.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.