mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: robert.richter@amd.com
Cc: linux-kernel@vger.kernel.org,
	oprofile-list@lists.sourceforge.net, oleg@redhat.com
Subject: [PATCHv2 0/2] oprofile, x86: allow backtrace for 32bit apps under 64bit kernel
Date: Wed, 29 Sep 2010 16:46:45 +0200	[thread overview]
Message-ID: <1285771607-12089-1-git-send-email-jolsa@redhat.com> (raw)

hi,

I'm sending reworked version of the support for backtrace of ia32
applications under 64bit kernels.

updates are based on comments by Robert Richter

v2:
	- using struct stack_frame for 64bit processes
	- using struct stack_frame_ia32 for compat processes
	- added inline function x86_backtrace_32 which is
	  just empty stub for !CONFIG_COMPAT
	- I did not figure out a smart way to share dump code between
	  32 and 64 bits. I'm currently under impression the code is
	  so far easy and light enough to live separately and mixing
	  the code would come with more complexity.


attached patches:
- 1/2 using struct stack_frame for 64bit processes dump
- 2/2 adding backtrace dump for 32bit process in compat mode

please let me know what you think

thanks,
jirka
---
 arch/x86/oprofile/backtrace.c |   70 ++++++++++++++++++++++++++++++++++------
 1 files changed, 59 insertions(+), 11 deletions(-)

             reply	other threads:[~2010-09-29 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 14:46 Jiri Olsa [this message]
2010-09-29 14:46 ` [PATCHv2 1/2] oprofile, x86: using struct stack_frame for 64bit processes dump Jiri Olsa
2010-09-29 14:46 ` [PATCHv2 2/2] oprofile, x86: adding backtrace dump for 32bit process in compat mode Jiri Olsa
2010-10-01 15:03 ` [PATCHv2 0/2] oprofile, x86: allow backtrace for 32bit apps under 64bit kernel Robert Richter

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=1285771607-12089-1-git-send-email-jolsa@redhat.com \
    --to=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=robert.richter@amd.com \
    /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®