From: David Mosberger <davidm@napali.hpl.hp.com>
To: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
Cc: Keith Owens <kaos@sgi.com>,
"Alan D. Brunelle" <Alan.Brunelle@hp.com>,
"Lynch, Rusty" <rusty.lynch@intel.com>,
akpm@osdl.org, "Luck, Tony" <tony.luck@intel.com>,
"Seth, Rohit" <rohit.seth@intel.com>,
prasanna@in.ibm.com, ananth@in.ibm.com,
systemtap@sources.redhat.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch 1/4] Kprobes support for IA64
Date: Thu, 26 May 2005 19:40:53 +0000 [thread overview]
Message-ID: <17046.9797.422792.800821@napali.hpl.hp.com> (raw)
In-Reply-To: <20050525180652.B10277@unix-os.sc.intel.com>
>>>>> On Wed, 25 May 2005 18:06:52 -0700, Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com> said:
Keshavamurthy> I agree with Keith, when a person taking a instructin
Keshavamurthy> dump, a different value will help uniquely identify
Keshavamurthy> that this is a kprobe break instruction which is a
Keshavamurthy> replaced instrucion of the original instruction. So
Keshavamurthy> we will leave with what we have now, i.e handle the
Keshavamurthy> same with two cases.
We could read the imm21 value from the break.b instruction.
--david
next prev parent reply other threads:[~2005-05-26 19:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 15:39 [patch 0/4] Kprobes support for IA64 Anil S Keshavamurthy
2005-05-23 15:39 ` [patch 1/4] " Anil S Keshavamurthy
2005-05-24 5:40 ` Keith Owens
2005-05-24 16:20 ` Lynch, Rusty
2005-05-25 13:59 ` Alan D. Brunelle
2005-05-25 16:46 ` Lynch, Rusty
2005-05-26 0:49 ` Keith Owens
2005-05-26 1:06 ` Keshavamurthy Anil S
2005-05-26 19:40 ` David Mosberger [this message]
2005-05-23 15:39 ` [patch 2/4] " Anil S Keshavamurthy
2005-05-23 15:39 ` [patch 3/4] " Anil S Keshavamurthy
2005-05-23 15:39 ` [patch 4/4] " Anil S Keshavamurthy
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=17046.9797.422792.800821@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=Alan.Brunelle@hp.com \
--cc=akpm@osdl.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=kaos@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
--cc=rohit.seth@intel.com \
--cc=rusty.lynch@intel.com \
--cc=systemtap@sources.redhat.com \
--cc=tony.luck@intel.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