public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	systemtap@sources.redhat.com, rusty.lynch@intel.com,
	davidm@napali.hpl.hp.com, alen.brunelle@hp.com,
	anil.s.keshavamurthy@intel.com
Subject: [patch 0/3] Kprobes Ia64 more fixes....
Date: Mon, 06 Jun 2005 10:36:52 -0700	[thread overview]
Message-ID: <20050606173652.059047000@csdlinux-2.jf.intel.com> (raw)

Hi All,
	Based on the feedback obtained from the community, I have
have address the below issues in the Kprobes.

1) When patching the original instruction with the break instruction,
we need to preserve the original qualifying predicate for all instruction
except for some special instruction like
(qp) cmp.crel.ctype p1,p2=r1,r2
where ctype == unc, which always needs to be emulated irrespective of
original qp.

2) Fail register_kprobes() for unsupported instruction. Currently
Kprobes of some speculation chk instruction and mov r1=ip 
kind of instructions are not supported. Hence when user
tries to register kprobes on these instruction, fail register_kprobe()
instead of handling badly.

Comments welcome.

Thanks,
Anil Keshavamurthy
--


             reply	other threads:[~2005-06-06 17:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06 17:36 Anil S Keshavamurthy [this message]
2005-06-06 17:36 ` [patch 1/3] Kprobes IA64 arch prepare kprobes cleanup Anil S Keshavamurthy
2005-06-06 17:36 ` [patch 2/3] Kprobes IA64 cmp ctype unc support Anil S Keshavamurthy
2005-06-06 17:36 ` [patch 3/3] Kprobes IA64 safe register kprobe 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=20050606173652.059047000@csdlinux-2.jf.intel.com \
    --to=anil.s.keshavamurthy@intel.com \
    --cc=akpm@osdl.org \
    --cc=alen.brunelle@hp.com \
    --cc=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty.lynch@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox