From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Prasanna S Panchamukhi <prasanna@in.ibm.com>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch] i386: entry.s::error_code is not safe for kprobes
Date: Fri, 4 Aug 2006 08:08:22 +0200 [thread overview]
Message-ID: <200608040808.22385.ak@suse.de> (raw)
In-Reply-To: <200608030623_MC3-1-C6F0-24AD@compuserve.com>
On Thursday 03 August 2006 12:20, Chuck Ebbert wrote:
> Because code marked unsafe for kprobes jumps directly to
> entry.S::error_code, that must be marked unsafe as well.
> The easiest way to do that is to move the page fault entry
> point to just before error_code and let it inherit the same
> section.
>
> Also moved all the ".previous" asm directives for kprobes
> sections to column 1 and removed ".text" from them.
Ok added thanks
-Andi
next prev parent reply other threads:[~2006-08-04 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 10:20 [patch] i386: entry.s::error_code is not safe for kprobes Chuck Ebbert
2006-08-04 6:08 ` Andi Kleen [this message]
2006-08-04 11:05 ` S. P. Prasanna
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=200608040808.22385.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.