From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Sasha Levin <sasha.levin@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] improve_stack: make stack dump output useful again
Date: Fri, 14 Mar 2014 16:08:46 -0400 [thread overview]
Message-ID: <20140314200846.GA6633@redhat.com> (raw)
In-Reply-To: <CA+55aFznCT20giHq8JxCRduky-dQtVLqpUYrcrK_3XeXN+Wyow@mail.gmail.com>
On Fri, Mar 14, 2014 at 12:32:23PM -0700, Linus Torvalds wrote:
> On Fri, Mar 14, 2014 at 12:08 PM, Dave Jones <davej@redhat.com> wrote:
> >
> > ok, nokalsr makes it work too.
> > Booting with that and using the perf binary from 3.14rc6 , I just see..
> >
> > 9.30% [kernel] [k] 0xffffffffaf18e887
>
> Hmm. Do you have CONFIG_KALLSYMS enabled?
$ grep KALLSYMS .config
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
mine looks like this.. http://codemonkey.org.uk/junk/kallsyms
> I have CONFIG_RANDOMIZE_BASE=y and perf (both report and top) seems to
> work fine for me (current git, not v3.14-rc6, but still)
yeah, on current now too.
CONFIG_RANDOMIZE_BASE=y
CONFIG_RANDOMIZE_BASE_MAX_OFFSET=0x40000000
Dave
prev parent reply other threads:[~2014-03-14 20:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 0:19 [RFC] improve_stack: make stack dump output useful again Sasha Levin
2014-02-23 20:27 ` Linus Torvalds
2014-02-23 20:44 ` Joe Perches
2014-02-23 20:55 ` Linus Torvalds
2014-03-13 15:16 ` Sasha Levin
2014-03-13 22:03 ` Linus Torvalds
2014-03-13 22:20 ` Sasha Levin
2014-03-13 22:59 ` Linus Torvalds
2014-03-13 23:07 ` Sasha Levin
2014-03-14 0:50 ` Linus Torvalds
2014-03-13 23:12 ` Dave Jones
2014-03-14 18:31 ` Kees Cook
2014-03-14 18:33 ` Dave Jones
2014-03-14 19:08 ` Dave Jones
2014-03-14 19:31 ` Kees Cook
2014-03-14 19:32 ` Linus Torvalds
2014-03-14 19:41 ` Linus Torvalds
2014-03-14 20:15 ` Kees Cook
2014-03-14 20:08 ` Dave Jones [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=20140314200846.GA6633@redhat.com \
--to=davej@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.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