From: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
To: Keith Owens <kaos@sgi.com>
Cc: Robin Holt <holt@sgi.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
Dean Nelson <dcn@sgi.com>
Subject: Re: Is notify_die being overloaded?
Date: Mon, 17 Apr 2006 09:50:27 -0700 [thread overview]
Message-ID: <20060417095026.B20168@unix-os.sc.intel.com> (raw)
In-Reply-To: <2059.1145260330@ocs3.ocs.com.au>; from kaos@sgi.com on Mon, Apr 17, 2006 at 05:52:10PM +1000
On Mon, Apr 17, 2006 at 05:52:10PM +1000, Keith Owens wrote:
>
> [*] It does not help that IA64 break.b <n> does not store the value of
> <n> in cr.iim. All break.b values look like break.b 0. There used
> to be code in traps.c to detect this and extract the value of
> break.b, but a kprobes patch removed that code.
Yes, Kprobes code removed it because, by the time this cpu reads the ia64 instruction
to decode the break value, at the same time on the other cpu, due to unregister_kprobes()
call, this instruction might be replace with the original instruction. Hence the
reading/decoding the instruction might result in wrong break number. So not a good idea to
decode the instruction.
-Anil
next prev parent reply other threads:[~2006-04-17 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 19:46 Is notify_die being overloaded? Robin Holt
2006-04-15 6:19 ` Keith Owens
2006-04-15 10:43 ` Robin Holt
2006-04-17 7:52 ` Keith Owens
2006-04-17 10:51 ` Robin Holt
2006-04-17 11:25 ` Robin Holt
2006-04-18 0:23 ` Keith Owens
2006-04-18 22:16 ` ia64_do_page_fault shows 19.4% slowdown from notify_die Robin Holt
2006-04-18 23:03 ` Keshavamurthy Anil S
2006-04-19 0:30 ` Andi Kleen
2006-04-19 11:11 ` Robin Holt
2006-04-17 16:50 ` Keshavamurthy Anil S [this message]
2006-04-17 16:45 ` Is notify_die being overloaded? Keshavamurthy Anil S
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=20060417095026.B20168@unix-os.sc.intel.com \
--to=anil.s.keshavamurthy@intel.com \
--cc=akpm@osdl.org \
--cc=dcn@sgi.com \
--cc=holt@sgi.com \
--cc=kaos@sgi.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