[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F844E6B.2070005@gmail.com>
Date: Tue, 10 Apr 2012 09:14:51 -0600
From: David Ahern <dsahern@...il.com>
To: Nikunj A Dadhania <nikunj@...ux.vnet.ibm.com>
CC: mingo@...hat.com, acme@...stprotocols.net, a.p.zijlstra@...llo.nl,
paulus@...ba.org, fweisbec@...il.com, eranian@...gle.com,
linux-kernel@...r.kernel.org
Subject: Re: [BUG PATCH] perf: kvm - finding struct machine fails for PERF_RECORD_MMAP
On 4/9/12 9:40 PM, Nikunj A Dadhania wrote:
> I can think of two places where it can happen:
>
> 1) perf_event__synthesize_kernel_mmap
>
> [...]
> mmap_name = machine__mmap_name(machine, name_buff, sizeof(name_buff));
> if (machine__is_host(machine)) {
> ...
> } else {
> event->header.misc = PERF_RECORD_MISC_GUEST_KERNEL;
> if (machine__is_default_guest(machine))
> filename = (char *) symbol_conf.default_guest_kallsyms;
> else {
> sprintf(path, "%s/proc/kallsyms", machine->root_dir);
> filename = path;
> }
> }
> [...]
> event->mmap.header.type = PERF_RECORD_MMAP;
> [...]
> event->mmap.pid = machine->pid;
>
> 2) perf_event__synthesize_modules
>
> [...]
> if (machine__is_host(machine))
> event->header.misc = PERF_RECORD_MISC_KERNEL;
> else
> event->header.misc = PERF_RECORD_MISC_GUEST_KERNEL;
> [...]
> event->mmap.header.type = PERF_RECORD_MMAP;
> [...]
> event->mmap.pid = machine->pid;
>
> BTW, i am testing this on latest -tip(498c911).
>
> In my case, I am able to recreate this everytime. And have verified that
> the event->header.type that I hit here is of type PERF_RECORD_MMAP.
I was thinking runtime, not initialization. Adding -o direct_io to the
sshfs mount did the trick. Reading guest /proc files exposes the segfault.
David
--
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