From: David Ahern <dsahern@gmail.com>
To: Ingo Molnar <mingo@elte.hu>, Joerg Roedel <joerg.roedel@amd.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
LKML <linux-kernel@vger.kernel.org>,
Jason Wang <jasowang@redhat.com>
Subject: Re: perf: record segfaults for cycles event when collecting data on a VM
Date: Thu, 09 Feb 2012 07:43:20 -0700 [thread overview]
Message-ID: <4F33DB88.2080209@gmail.com> (raw)
In-Reply-To: <20120209133446.GD8830@elte.hu>
On 02/09/2012 06:34 AM, Ingo Molnar wrote:
>
> * Joerg Roedel <joerg.roedel@amd.com> wrote:
>
>> On Thu, Feb 09, 2012 at 08:30:24AM +0100, Ingo Molnar wrote:
>>>
>>> * Joerg Roedel <joerg.roedel@amd.com> wrote:
>>>
>>>>> which makes sense. It forces
>>>>> perf_session__find_machine_for_cpumode() to return the host
>>>>> machine always.
>>>>
>>>> Great, thanks. I will send two patches tomorrow to fix Jason's
>>>> problem and change the default for perf_guest.
>>>
>>> Well, if the crash is fixed then the the default can stay,
>>> right?
>>
>> David's crash is fixed by changing the default back to its
>> original value :)
>
> Then that's the wrong fix really.
You can't enable perf_guest unless guest info has been configured as
done with perf-kvm.
The problem is triggered in perf_session__find_machine_for_cpumode(). If
perf_session__find_machine() is changed to
perf_session__findnew_machine() you get into machines__findnew() which
shows the root cause: the event is for a VM but symbol_conf.guestmount
is not set.
So, really perf_guest cannot be enabled unless guest info has been given.
David
prev parent reply other threads:[~2012-02-09 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 16:55 perf: record segfaults for cycles event when collecting data on a VM David Ahern
2012-02-08 17:44 ` Joerg Roedel
2012-02-08 17:53 ` David Ahern
2012-02-08 17:57 ` Joerg Roedel
2012-02-09 7:30 ` Ingo Molnar
2012-02-09 11:14 ` Joerg Roedel
2012-02-09 13:34 ` Ingo Molnar
2012-02-09 14:32 ` Joerg Roedel
2012-02-09 15:28 ` Joerg Roedel
2012-02-09 15:47 ` David Ahern
2012-02-09 14:43 ` David Ahern [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=4F33DB88.2080209@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=jasowang@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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