All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Avi Kivity <avi@redhat.com>, Pekka Enberg <penberg@kernel.org>,
	"Yan, Zheng" <zheng.z.yan@linux.intel.com>,
	Sasha Levin <levinsasha928@gmail.com>,
	Asias He <asias.hejun@gmail.com>,
	Cyrill Gorcunov <gorcunov@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	KVM General <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>
Subject: Re: perf uncore & lkvm woes
Date: Thu, 16 Aug 2012 08:28:33 -0600	[thread overview]
Message-ID: <502D0391.2040700@gmail.com> (raw)
In-Reply-To: <1345115846.29668.16.camel@twins>

On 8/16/12 5:17 AM, Peter Zijlstra wrote:
> If you don't mind printing a warning every time a Linux guest boots ;-)

That feature already exists today for perf related probing. e.g.,

[585929.678746] kvm [10752]: vcpu0 unhandled rdmsr: 0x345
[585929.709870] kvm_set_msr_common: 54 callbacks suppressed
[585929.709986] kvm [10752]: vcpu0 unhandled wrmsr: 0x680 data 0
[585929.710104] kvm [10752]: vcpu0 unhandled wrmsr: 0x6c0 data 0
[585929.710221] kvm [10752]: vcpu0 unhandled wrmsr: 0x681 data 0
[585929.710352] kvm [10752]: vcpu0 unhandled wrmsr: 0x6c1 data 0
[585929.710467] kvm [10752]: vcpu0 unhandled wrmsr: 0x682 data 0
[585929.710581] kvm [10752]: vcpu0 unhandled wrmsr: 0x6c2 data 0
[585929.710707] kvm [10752]: vcpu0 unhandled wrmsr: 0x683 data 0
[585929.710822] kvm [10752]: vcpu0 unhandled wrmsr: 0x6c3 data 0
[585929.710937] kvm [10752]: vcpu0 unhandled wrmsr: 0x684 data 0
[585929.711052] kvm [10752]: vcpu0 unhandled wrmsr: 0x6c4 data 0


David

      parent reply	other threads:[~2012-08-16 14:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  7:01 perf uncore & lkvm woes Pekka Enberg
2012-08-16  7:07 ` Cyrill Gorcunov
2012-08-16  7:16   ` Cyrill Gorcunov
2012-08-16  7:16   ` Pekka Enberg
2012-08-16  7:19 ` Peter Zijlstra
2012-08-16  7:38   ` Yan, Zheng
2012-08-16  7:41     ` Pekka Enberg
2012-08-16  7:46       ` Cyrill Gorcunov
2012-08-16  8:45         ` Avi Kivity
2012-08-16  9:06           ` Cyrill Gorcunov
2012-08-16  9:23             ` Pekka Enberg
2012-08-16  8:40       ` Avi Kivity
2012-08-16 11:06         ` Avi Kivity
2012-08-16 11:17           ` Peter Zijlstra
2012-08-16 11:25             ` Avi Kivity
2012-08-17  1:40               ` Yan, Zheng
2012-08-17  6:56                 ` Peter Zijlstra
2012-08-19  9:55                   ` Avi Kivity
2012-08-20  4:15                     ` Yan, Zheng
2012-08-20  8:49                       ` Avi Kivity
2012-08-21  1:11                         ` Yan, Zheng
2012-08-21  8:32                           ` Avi Kivity
2012-08-21  9:07                             ` Yan, Zheng
2012-08-20  5:30                     ` Yan, Zheng
2012-08-20  8:48                       ` Avi Kivity
2012-08-21  7:11                     ` Peter Zijlstra
2012-08-21  8:34                       ` Avi Kivity
2012-08-21 10:35                         ` Peter Zijlstra
2012-08-22  8:53                           ` Avi Kivity
2012-08-16 14:28             ` 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=502D0391.2040700@gmail.com \
    --to=dsahern@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=asias.hejun@gmail.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.org \
    --cc=zheng.z.yan@linux.intel.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.