From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Shorter fast tracepoints
Date: Sat, 29 Oct 2011 10:09:00 -0000 [thread overview]
Message-ID: <838vo49mrc.fsf@gnu.org> (raw)
In-Reply-To: <4EAB573C.8040201@earthlink.net>
> Date: Fri, 28 Oct 2011 18:30:36 -0700
> From: Stan Shebs <stanshebs@earthlink.net>
>
> The ugly part is that the 2-byte address is in the low 64K of memory,
> which may or may not be available - GDB has to check
> /proc/sys/vm/mmap_min_addr. Fortunately users can tweak it manually
> (via sysctl) if the preset is to block out all of low memory.
>
> This brings up two troublesome points about this patch as it stands.
> First, documentation. As it stands, the patch to the manual says
> nothing about fooling with the kernel's mmap_min_addr.
In fact, it says nothing at all about the potential problems you
described in this mail that this patch and the packet you introduced
attempts to solve. Readers might wonder why the packet is even
needed.
> Should it? It's very system-specific, and the user would only need
> to do anything special if mmap_min_addr were set to 64K or higher,
> otherwise everything quietly works as desired.
If users of tracepoints need to know about this detail, then yes, the
manual should mention it. We can always qualify any specific info by
its being system-specific, but having the information there for
specific systems, especially popular ones, is a Good Thing.
I have no other comments for the documentation parts of your patch,
they are fine with me. Thanks.
prev parent reply other threads:[~2011-10-29 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 1:55 Stan Shebs
2011-10-29 10:09 ` Eli Zaretskii [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=838vo49mrc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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