From: Andi Kleen <ak@muc.de>
To: Roland McGrath <roland@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-64 kprobes: handle %RIP-relative addressing mode
Date: Sun, 13 Mar 2005 17:37:46 +0100 [thread overview]
Message-ID: <m18y4ry011.fsf@muc.de> (raw)
In-Reply-To: <200503130954.j2D9sgjB028594@magilla.sf.frob.com> (Roland McGrath's message of "Sun, 13 Mar 2005 01:54:42 -0800")
Roland McGrath <roland@redhat.com> writes:
> The existing x86-64 kprobes implementation doesn't cope with the
> %RIP-relative addressing mode. Kprobes work by single-stepping a copy of
Thanks for fixing that long standing bug.
> + static const unsigned char onebyte_has_modrm[256] = {
Can you turn these two arrays into a bitmap please?
> + * This basically replicates __vmalloc, except that it uses a
This shouldn't be opencoded here. Instead make a utility function
like vmalloc_range() that takes a start and end address and
make the module allocation use it too.
Also you should fix up asm-x86_64/page.h and Documentation/x86_64/mm.txt
with the new fixed allocation.
> + * range of addresses starting a MODULE_END. This also
> + * allocates a single page of address space with no following
> + * guard page (__get_vm_area always adds PAGE_SIZE to the size,
> + * so by passing zero we get the one page). We set up all the
I think Andrea has just changed that and the patch went into
mainline. Be careful with merging.
-Andi
next prev parent reply other threads:[~2005-03-13 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 9:54 [PATCH] x86-64 kprobes: handle %RIP-relative addressing mode Roland McGrath
2005-03-13 16:37 ` Andi Kleen [this message]
2005-03-15 8:59 ` Roland McGrath
2005-03-13 21:48 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-03-13 19:22 Oleg Nesterov
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=m18y4ry011.fsf@muc.de \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.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 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.