[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFy5pfzKfaDCc0jbQ5_+_+MMso_XqRcR-KqkZMwcSXAbPQ@mail.gmail.com>
Date: Mon, 16 Apr 2012 08:02:20 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc: Arnaldo Carvalho de Melo <acme@...hat.com>,
Ingo Molnar <mingo@...nel.org>, hpa@...or.com,
paulus@...ba.org, eranian@...gle.com, linux-kernel@...r.kernel.org,
efault@....de, peterz@...radead.org, namhyung@...il.com,
fweisbec@...il.com, dsahern@...il.com, tglx@...utronix.de,
linux-tip-commits@...r.kernel.org, yrl.pp-manager.tt@...achi.com
Subject: Re: [tip:perf/core] perf ui annotate browser: Allow toggling addr
offset view
On Sun, Apr 15, 2012 at 11:25 PM, Masami Hiramatsu
<masami.hiramatsu.pt@...achi.com> wrote:
>
> If we can ignore permissions, we can check whether the instruction
> at the event address is modified or not in /dev/mem.
> And that is also useful for modules. That can be done in userspace
> with using setuid'd tool.
No, please don't make a setuid tool for this.
It really would be *much* better if you could parse the
'altinstructions' section. You already have a lot of ELF parsing code.
Trust me, that's much better than trying to read the actual kernel
image - and makes things like off-line analysis easier too. The only
thing you need is the active CPU features (default to "current CPU
features"), rather than having to have the whole kernel image.
And no permission issues.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists