From: Peter Zijlstra <peterz@infradead.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>, Kees Cook <keescook@chromium.org>,
crash-utility@redhat.com, linux-kernel@vger.kernel.org,
Dave Anderson <anderson@redhat.com>,
Andrew Honig <ahonig@google.com>,
Eugene Surovegin <surovegin@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Yinghai Lu <yinghai@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH v2] x86, kaslr: export offset in VMCOREINFO ELF notes
Date: Mon, 27 Jan 2014 17:19:59 +0100 [thread overview]
Message-ID: <20140127161959.GD4941@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <52E681B6.7020501@intel.com>
On Mon, Jan 27, 2014 at 05:56:38PM +0200, Adrian Hunter wrote:
> No. In fact annotation works now with kcore. Linus' problem was with vmlinux.
>
> Kcore won't be used with kaslr in the case:
> 1. record data with 'perf record'
> 2. reboot
> 3. use annotation on the previously recorded data
>
> As I noted in the commit message, you can still use kcore if you made a copy
> (with perf buildid-cache) at the time the data was recorded.
Not that I care much about this particular case; but you could also save
the offset at record time and do double offset correction assuming its
still the same kernel you booted into but at a different location.
next prev parent reply other threads:[~2014-01-27 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 17:31 [PATCH v2] x86, kaslr: export offset in VMCOREINFO ELF notes Kees Cook
2014-01-25 7:47 ` Ingo Molnar
2014-01-27 14:15 ` Adrian Hunter
2014-01-27 15:25 ` Ingo Molnar
2014-01-27 15:56 ` Adrian Hunter
2014-01-27 16:19 ` Peter Zijlstra [this message]
2014-01-27 16:22 ` Peter Zijlstra
2014-01-27 18:41 ` Andrew Honig
2014-01-27 19:33 ` Peter Zijlstra
2014-02-21 20:25 ` Kees Cook
2014-02-26 1:06 ` [tip:x86/urgent] " tip-bot for Eugene Surovegin
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=20140127161959.GD4941@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=ahonig@google.com \
--cc=anderson@redhat.com \
--cc=crash-utility@redhat.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=surovegin@google.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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