From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] kprobe invalidate icache of jump buffer
Date: Thu, 29 Jun 2006 12:52:27 +0000 [thread overview]
Message-ID: <yq0zmfwgm44.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <44A39D6E.1050302@intel.com>
>>>>> "Mao" = bibo, mao <bibo.mao@intel.com> writes:
Mao> Hi, Kprobe inserts breakpoint instruction in probepoint and then
Mao> jump to jmp buffer, the jump buffer icache must be consistent
Mao> with dcache. Here is the patch invalidates jump buffer icache
Mao> area. Without this patch, in some machines there will be fault
Mao> when jumping to jmp buffer where icache content is inconsistent
Mao> with dcache.
Mao> This patch has been tested in my IA32, x86_64 and IA64 box, but
Mao> is not tested in SPARC64 and powerpc architecture. It is based on
Mao> kernel 2.6.17 version. Signed-off-by: bibo,mao
Mao> <bibo.mao@intel.com> Thanks bibo,mao diff -Nruap
Your patch seems to have been mangled by your mail client. Please also
make it comply with Documentation/CodingStyle
Cheers,
Jes
prev parent reply other threads:[~2006-06-29 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 9:29 [PATCH] kprobe invalidate icache of jump buffer bibo, mao
2006-06-29 12:52 ` Jes Sorensen [this message]
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=yq0zmfwgm44.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=linux-ia64@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