From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: "Jan Beulich" <jbeulich@novell.com>, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: [PATCH 2/3] reliable stack trace support (x86-64)
Date: Thu, 18 May 2006 14:25:51 +0200 [thread overview]
Message-ID: <200605181425.51442.ak@suse.de> (raw)
In-Reply-To: <446C7E61.76E4.0078.0@novell.com>
> >Maybe I'm dense but I still don't get - frame has a pt_regs so why
> >isn't the caller allowed to know about that fact?
>
> Because the fact that there is a regs fields and the PC is accessible through it is architecture specific, yet the
> caller (kernel/unwind.c) ought to be architecture independent.
I doubt we have any architecture where the instruction pointer is not in pt_regs,
but ok.
-Andi
prev parent reply other threads:[~2006-05-18 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 14:21 [PATCH 2/3] reliable stack trace support (x86-64) Jan Beulich
2006-05-16 15:09 ` Ingo Molnar
2006-05-16 16:04 ` Jan Beulich
2006-05-16 15:13 ` Andi Kleen
2006-05-16 16:06 ` Jan Beulich
2006-05-16 17:05 ` [discuss] " Andi Kleen
2006-05-18 9:37 ` Jan Beulich
2006-05-18 10:20 ` Andi Kleen
2006-05-18 12:02 ` Jan Beulich
2006-05-18 12:25 ` 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=200605181425.51442.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--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