From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: "Chuck Ebbert" <76306.1226@compuserve.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] i386: fix stuck unwind into kernel thread
Date: Mon, 7 Aug 2006 10:11:31 +0200 [thread overview]
Message-ID: <200608071011.31473.ak@suse.de> (raw)
In-Reply-To: <44D710D9.76E4.0078.0@novell.com>
On Monday 07 August 2006 10:07, Jan Beulich wrote:
> >>> 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).
I can do that.
-Andi
prev parent reply other threads:[~2006-08-07 8:11 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
2006-08-07 8:11 ` Andi Kleen [this message]
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=200608071011.31473.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=jbeulich@novell.com \
--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