From: Michael Neuling <mikey@neuling•org>
To: Masami Hiramatsu <mhiramat@redhat•com>
Cc: Mahesh Salgaonkar <mahesh@linux•vnet.ibm.com>, linuxppc-dev@ozlabs•org
Subject: Re: [PATCH -tip tracing/kprobes] PPC: Powerpc port of the kprobe-based event tracer
Date: Thu, 17 Dec 2009 20:43:03 +1100 [thread overview]
Message-ID: <11626.1261042983@neuling.org> (raw)
In-Reply-To: <4B29C3E3.3060905@redhat.com>
In message <4B29C3E3.3060905@redhat•com> you wrote:
> Hi Michael,
>
> Michael Neuling wrote:
> >> +
> >> +static const struct pt_regs_offset regoffset_table[] = {
> >> + REG_OFFSET_NAME(gpr[0]),
> >> + REG_OFFSET_NAME(gpr[1]),
> >> + REG_OFFSET_NAME(gpr[2]),
> >> + REG_OFFSET_NAME(gpr[3]),
> >> + REG_OFFSET_NAME(gpr[4]),
> >> + REG_OFFSET_NAME(gpr[5]),
> >> + REG_OFFSET_NAME(gpr[6]),
> >> + REG_OFFSET_NAME(gpr[7]),
> >> + REG_OFFSET_NAME(gpr[8]),
> >> + REG_OFFSET_NAME(gpr[9]),
> >> + REG_OFFSET_NAME(gpr[10]),
> >> + REG_OFFSET_NAME(gpr[11]),
> >> + REG_OFFSET_NAME(gpr[12]),
> >> + REG_OFFSET_NAME(gpr[13]),
> >> + REG_OFFSET_NAME(gpr[14]),
> >> + REG_OFFSET_NAME(gpr[15]),
> >> + REG_OFFSET_NAME(gpr[16]),
> >> + REG_OFFSET_NAME(gpr[17]),
> >> + REG_OFFSET_NAME(gpr[18]),
> >> + REG_OFFSET_NAME(gpr[19]),
> >> + REG_OFFSET_NAME(gpr[20]),
> >> + REG_OFFSET_NAME(gpr[21]),
> >> + REG_OFFSET_NAME(gpr[22]),
> >> + REG_OFFSET_NAME(gpr[23]),
> >> + REG_OFFSET_NAME(gpr[24]),
> >> + REG_OFFSET_NAME(gpr[25]),
> >> + REG_OFFSET_NAME(gpr[26]),
> >> + REG_OFFSET_NAME(gpr[27]),
> >> + REG_OFFSET_NAME(gpr[28]),
> >> + REG_OFFSET_NAME(gpr[29]),
> >> + REG_OFFSET_NAME(gpr[30]),
> >> + REG_OFFSET_NAME(gpr[31]),
> >> + REG_OFFSET_NAME(nip),
> >> + REG_OFFSET_NAME(msr),
> >> + REG_OFFSET_NAME(orig_gpr3),
> >> + REG_OFFSET_NAME(ctr),
> >> + REG_OFFSET_NAME(link),
> >> + REG_OFFSET_NAME(xer),
> >> + REG_OFFSET_NAME(ccr),
> >> +#ifdef CONFIG_PPC64
> >> + REG_OFFSET_NAME(softe),
> >> +#else
> >> + REG_OFFSET_NAME(mq),
> >> +#endif
> >> + REG_OFFSET_NAME(trap),
> >> + REG_OFFSET_NAME(dar),
> >> + REG_OFFSET_NAME(dsisr),
> >> + REG_OFFSET_NAME(result),
> >> + REG_OFFSET_END,
> >
> > Do we need to add something for FP and VMX registers here?
>
> Hmm, are FP and VMX registers actually used inside kernel on PPC?
Yes. Look for enable_kernel_fp/altivec
Mikey
> Actually, the main purpose of this code is to provide accessing method
> of in-kernel pt_regs fields (registers used in kernel) by name.
next prev parent reply other threads:[~2009-12-17 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091216043619.963539987@mars.in.ibm.com>
2009-12-16 4:39 ` [PATCH -tip tracing/kprobes] PPC: Powerpc port of the kprobe-based event tracer Mahesh Salgaonkar
2009-12-17 2:22 ` Michael Neuling
2009-12-17 5:38 ` Masami Hiramatsu
2009-12-17 9:43 ` Michael Neuling [this message]
2009-12-17 7:07 ` Benjamin Herrenschmidt
2009-12-17 8:39 ` Mahesh Jagannath Salgaonkar
2009-12-17 9:57 ` Michael Neuling
2009-12-18 5:10 ` Mahesh Jagannath Salgaonkar
2009-12-18 14:35 ` Masami Hiramatsu
2009-12-20 20:54 ` Michael Neuling
2009-12-23 1:32 ` Masami Hiramatsu
2009-12-23 2:37 ` Michael Neuling
2009-12-20 20:59 ` Michael Neuling
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=11626.1261042983@neuling.org \
--to=mikey@neuling$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mahesh@linux$(echo .)vnet.ibm.com \
--cc=mhiramat@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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