All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org, psuriset@linux.vnet.ibm.com,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Ingo Molnar <mingo@kernel.org>, Namhyung Kim <namhyung@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] perf kvm: fix segfault with default guest arguments
Date: Mon, 25 Jun 2012 12:44:52 -0600	[thread overview]
Message-ID: <4FE8B1A4.9050704@gmail.com> (raw)
In-Reply-To: <20120625160847.GE30293@krava.brq.redhat.com>

On 6/25/12 10:08 AM, Jiri Olsa wrote:
>> perf's handling of default kallsyms and guest-modules needs to be reworked.
> agreed ;) any plans on that?

I am working on it as time allows. After debugging this latest data 
point (running longer avoid the segfault) I certainly understand the 
problem better, but the problem keeps expanding too -- like wrong paths 
on guest side modules. It really suggests that this notion of a 
'default' guest is just wrong - too little information. We'll see.

David

  reply	other threads:[~2012-06-25 18:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25  4:41 [PATCH] perf kvm: fix segfault with default guest arguments David Ahern
2012-06-25  8:39 ` Namhyung Kim
2012-06-25 12:51   ` David Ahern
2012-06-25 19:04     ` David Ahern
2012-06-26  0:35       ` Namhyung Kim
2012-06-25 16:08 ` Jiri Olsa
2012-06-25 18:44   ` David Ahern [this message]
     [not found] ` <20120628144418.GG4038@infradead.org>
2012-06-28 14:51   ` David Ahern
2012-06-28 14:52   ` David Ahern
2012-06-30  0:40   ` David Ahern
2012-07-01 22:16 ` David Ahern
  -- strict thread matches above, loose matches on Subject: below --
2012-06-25  4:37 David Ahern

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=4FE8B1A4.9050704@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@gmail.com \
    --cc=peterz@infradead.org \
    --cc=psuriset@linux.vnet.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.