From: Masami Hiramatsu <mhiramat@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jim Keniston <jkenisto@us.ibm.com>,
systemtap-ml <systemtap@sources.redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH -tip 2/6 V4.1] x86: add arch-dep register and stack access API to ptrace
Date: Fri, 03 Apr 2009 17:34:08 -0400 [thread overview]
Message-ID: <49D680D0.1090701@redhat.com> (raw)
In-Reply-To: <20090403202004.3A2B1FC3AB@magilla.sf.frob.com>
Roland McGrath wrote:
>> +static struct pt_regs_offset regoffset_table[] = {
>
> ^ const
Oops, exactly.
Perhaps, I need to update insn.c to make bitmap tables
"static const" too.
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
WARNING: multiple messages have this Message-ID (diff)
From: Masami Hiramatsu <mhiramat@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jim Keniston <jkenisto@us.ibm.com>,
systemtap-ml <systemtap@sources.redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH -tip 2/6 V4.1] x86: add arch-dep register and stack access API to ptrace
Date: Fri, 03 Apr 2009 17:34:08 -0400 [thread overview]
Message-ID: <49D680D0.1090701@redhat.com> (raw)
In-Reply-To: <20090403202004.3A2B1FC3AB@magilla.sf.frob.com>
Roland McGrath wrote:
>> +static struct pt_regs_offset regoffset_table[] = {
>
> ^ const
Oops, exactly.
Perhaps, I need to update insn.c to make bitmap tables
"static const" too.
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-04-03 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 17:24 [PATCH -tip 2/6 V4] x86: add arch-dep register and stack access API to ptrace Masami Hiramatsu
2009-04-02 17:24 ` Masami Hiramatsu
2009-04-02 23:48 ` Frederic Weisbecker
2009-04-02 23:48 ` Frederic Weisbecker
2009-04-03 0:45 ` Masami Hiramatsu
2009-04-03 0:45 ` Masami Hiramatsu
2009-04-03 16:02 ` [PATCH -tip 2/6 V4.1] " Masami Hiramatsu
2009-04-03 16:02 ` Masami Hiramatsu
2009-04-03 20:20 ` Roland McGrath
2009-04-03 21:34 ` Masami Hiramatsu [this message]
2009-04-03 21:34 ` Masami Hiramatsu
2009-04-03 23:29 ` [PATCH -tip 2/6 V4.2] " Masami Hiramatsu
2009-04-03 23:29 ` Masami Hiramatsu
2009-04-06 19:22 ` Roland McGrath
2009-04-06 19:22 ` Roland McGrath
2009-04-06 19:57 ` Masami Hiramatsu
2009-04-06 19:57 ` Masami Hiramatsu
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=49D680D0.1090701@redhat.com \
--to=mhiramat@redhat.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=andi@firstfloor.org \
--cc=fweisbec@gmail.com \
--cc=jkenisto@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.