From: "Jan Beulich" <jbeulich@novell.com>
To: "Chuck Ebbert" <76306.1226@compuserve.com>
Cc: "Andi Kleen" <ak@suse.de>, <linux-kernel@vger.kernel.org>
Subject: Re: [patch] i386: fix stuck unwind into kernel thread
Date: Mon, 07 Aug 2006 09:07:21 +0100 [thread overview]
Message-ID: <44D710D9.76E4.0078.0@novell.com> (raw)
In-Reply-To: <200608061458_MC3-1-C742-330A@compuserve.com>
>>> Chuck Ebbert <76306.1226@compuserve.com> 06.08.06 20:56 >>>
>We cannot unwind past kernel_thread_helper.
Just as mentioned before - we shouldn't add endless special cases to the code that interprets the unwind
information, but rather fix the unwind information so that it properly reflect the actual state. Like in the
other case, the piece of code should be properly annotated, which would require it to be moved into
an assembly file (it escapes me why code like that was ever placed in a C file).
Jan
next prev parent reply other threads:[~2006-08-07 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 18:56 [patch] i386: fix stuck unwind into kernel thread Chuck Ebbert
2006-08-07 8:07 ` Jan Beulich [this message]
2006-08-07 8:11 ` Andi Kleen
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=44D710D9.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox