Re: [PATCH] Identify which executable object the userspace addressbelongs to. Store thread group leader id, and use it to lookup theaddress in the process's map. We could have looked up the addresson thread's map, but the thread might not exist by the time we arecalled. The process might not exist either, but if you are readingtrace_pipe, that is unlikely.

From: Christoph Hellwig
Date: Thu Nov 06 2008 - 07:27:22 EST

Next message: Pavel Machek: "Re: [PATCH] hibernation should work ok with memory hotplug"
Previous message: Hugh Dickins: "[PATCH] x86: align DirectMap in /proc/meminfo"
In reply to: Ingo Molnar: "Re: [PATCH] Identify which executable object the userspace addressbelongs to. Store thread group leader id, and use it to lookup theaddress in the process's map. We could have looked up the addresson thread's map, but the thread might not exist by the time we arecalled. The process might not exist either, but if you are readingtrace_pipe, that is unlikely."
Next in thread: Ingo Molnar: "Re: [PATCH] Identify which executable object the userspace addressbelongs to. Store thread group leader id, and use it to lookup theaddress in the process's map. We could have looked up the addresson thread's map, but the thread might not exist by the time we arecalled. The process might not exist either, but if you are readingtrace_pipe, that is unlikely."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Nov 06, 2008 at 10:55:47AM +0100, Ingo Molnar wrote:
> > On Mon, Nov 03, 2008 at 08:32:57AM +0100, Ingo Molnar wrote:
> > > could you please help out with such a helper? This is really about
> > > visualization, not to rely on it.
> >
> > Is this kindergarten? [...]
>
> No, this is lkml where, if you decide to stand in the way of a patch,
> you are supposed to back up your NAK's with a path out of that NAK.
> Instead of forcing people into multiple email ping-pongs trying to
> figure out what exactly the objections mean.

Even if that was true, which would be avery sad world I should be
easy enough for you or anyone to look at what seq_path does and how
to have a version that doesn't use the seq_file insterface. Takes
about two minutes with most of the time spent on finding where seq_file
is implemented.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/