From: Arjan van de Ven <arjan@infradead.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
phil.el@wanadoo.fr, oprofile-list@lists.sourceforge.net
Subject: Re: [PATCH][RFC] x86: oprofile 32bit stack traces on 64bit kernel
Date: Thu, 7 Feb 2008 08:57:21 -0800 [thread overview]
Message-ID: <20080207085721.4a4e36ee@laptopd505.fenrus.org> (raw)
In-Reply-To: <47A88CE4.3070205@windriver.com>
On Tue, 05 Feb 2008 10:20:52 -0600
Jason Wessel <jason.wessel@windriver.com> wrote:
>
> There are multiple ways to write the same code, hence the reason this
> is listed as an RFC patch. I wanted to provide a working fix to
> account for the case of executing 32 bit and 64 bit user space code on
> a 64 bit kernel.
>
> -----CLIP HERE-------
>
> Allow oprofile's backtrace to work on a 32bit user space thread when
> running on a 64bit kernel.
>
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
looks sane; it'll be better than what is there now at least
and it's safe enough
Acked-by: Arjan van de Ven <arjan@linux.intel.com>
prev parent reply other threads:[~2008-02-07 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 16:20 Jason Wessel
2008-02-07 16:57 ` Arjan van de Ven [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=20080207085721.4a4e36ee@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=phil.el@wanadoo.fr \
/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
all inboxes | Powered by JetHome®