From: Daniel Jacobowitz <dan@debian.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: Takashi Ikebe <ikebe.takashi@lab.ntt.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 & x86_64: Live Patching Funcion on 2.6.11.7
Date: Sun, 17 Apr 2005 14:51:43 -0400 [thread overview]
Message-ID: <20050417185143.GA5002@nevyn.them.org> (raw)
In-Reply-To: <20050416234439.5464e188.davem@davemloft.net>
On Sat, Apr 16, 2005 at 11:44:39PM -0700, David S. Miller wrote:
>
> Takashi-san, have you ever investigated using kprobes to
> implement this feature? It seems a perfect fit, and would
> allow support on several architectures other than just x86
> and x86_64.
>
> If kprobes does not meet your needs completely, it could
> be trivially extended to do so.
>
> I think implementing something like this from scratch is
> not a good idea when we have much of the needed logic and
> infrastructure already.
Takashi-san's description was not very clear, but it sounds like it's a
patching mechanism for userspace applications - not for kernel space.
So kprobes would not be a good fit.
If I'm right, I'm not sure why some of the bits of it were done
separately instead of via the existing ptrace mechanism. And GDB
would appreciate a mechanism for mmap/munmap/mprotect in a debugged
process, also.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-17 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 3:47 [PATCH] i386 & x86_64: Live Patching Funcion on 2.6.11.7 Takashi Ikebe
2005-04-17 6:44 ` David S. Miller
2005-04-17 18:51 ` Daniel Jacobowitz [this message]
2005-04-17 20:32 ` David S. Miller
2005-04-18 1:41 ` Takashi Ikebe
2005-04-18 4:41 ` Daniel Jacobowitz
2005-04-18 5:20 ` Takashi Ikebe
2005-04-23 16:10 ` Andi Kleen
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=20050417185143.GA5002@nevyn.them.org \
--to=dan@debian.org \
--cc=davem@davemloft.net \
--cc=ikebe.takashi@lab.ntt.co.jp \
--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