From: Masami Hiramatsu <mhiramat@redhat.com>
To: Richard J Moore <richardj_moore@uk.ibm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>,
Anton Massoud <anton.massoud@ericsson.com>,
Arjan van de Ven <arjan@infradead.org>,
Dominique Toupin <dominique.toupin@ericsson.com>,
"H. Peter Anvin" <hpa@zytor.com>, Jason Baron <jbaron@redhat.com>,
Jim Keniston <jkenisto@us.ibm.com>,
linux-kernel@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Ingo Molnar <mingo@elte.hu>,
Nathan Sidwell <nathan@codesourcery.com>,
Prasanna S Panchamukhi <prasanna@in.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Rusty Lynch <rusty.lynch@intel.com>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vamsi Krishna S <vamsi_krishna@in.ibm.com>
Subject: Re: Immediate values
Date: Fri, 25 Sep 2009 04:12:36 -0700 [thread overview]
Message-ID: <4ABCA5A4.5000605@redhat.com> (raw)
In-Reply-To: <OF19654CE4.D069FD43-ON8025763C.0037FB4D-8025763C.00389751@uk.ibm.com>
Richard J Moore wrote:
>
>
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote on 25/09/2009 11:02:06:
>
>
>>
>> There was considerable discussion abut this when the kprobe stuff went
>> in. If I remember rightly it was stated by someone @intel.com then that
>> int3 was ok (even though its not strictly documented as such). The same
>> is not true for all instructions on all x86 processors unfortunately.
>>
>> Alan
>
> Alan, I had that discussion with Intel, and yes int3 is a special case
> because of the interrupt processing associated with it. The discussion
> went along this lines: int3 is practically useless in an MP environment
> if it's trouble by the cross-modifying erratum.
>
> I suppose it is possible the more recent microarchitectures have
> changed things. And yes, we might need to have that conversation again.
Hi,
I'm also very interested in this topic, since I'd like to replace
kprobe's int3 with jump instruction by using bypass code, which
Mathieu's new imv using.
http://lkml.org/lkml/2009/9/14/549
Actually, it is OK even if I need to use stop_machine(), because
the main goal is reducing overhead of probing, not reducing
the replacing time. :)
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-09-25 11:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 12:31 Immediate values Mathieu Desnoyers
2009-09-24 12:34 ` Ingo Molnar
2009-09-24 14:02 ` Jason Baron
2009-09-24 14:10 ` H. Peter Anvin
2009-09-24 14:16 ` Mathieu Desnoyers
2009-09-24 19:16 ` Ingo Molnar
2009-09-24 19:34 ` Ingo Molnar
2009-09-25 6:51 ` Arjan van de Ven
2009-09-25 7:35 ` Mathieu Desnoyers
2009-09-25 8:25 ` Arjan van de Ven
2009-09-25 10:02 ` Alan Cox
2009-09-25 10:14 ` Arjan van de Ven
2009-09-25 16:19 ` H. Peter Anvin
2009-09-25 16:45 ` Arjan van de Ven
2009-09-25 17:05 ` H. Peter Anvin
2009-09-25 10:18 ` Richard J Moore
2009-09-25 11:12 ` Masami Hiramatsu [this message]
2009-09-24 14:16 ` H. Peter Anvin
2009-09-24 15:39 ` Jason Baron
2009-09-24 16:52 ` H. Peter Anvin
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=4ABCA5A4.5000605@redhat.com \
--to=mhiramat@redhat.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton.massoud@ericsson.com \
--cc=arjan@infradead.org \
--cc=dominique.toupin@ericsson.com \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=nathan@codesourcery.com \
--cc=prasanna@in.ibm.com \
--cc=richardj_moore@uk.ibm.com \
--cc=rostedt@goodmis.org \
--cc=rusty.lynch@intel.com \
--cc=suparna@in.ibm.com \
--cc=tglx@linutronix.de \
--cc=vamsi_krishna@in.ibm.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