From: Paolo Bonzini <pbonzini@redhat.com>
To: Venkatesh Srinivas <venkateshs@google.com>,
Andy Lutomirski <luto@amacapital.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
KVM list <kvm@vger.kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: Should KVM_GUEST stop depending on PARAVIRT?
Date: Wed, 29 Jul 2015 10:27:39 +0200 [thread overview]
Message-ID: <55B88E7B.3010102@redhat.com> (raw)
In-Reply-To: <CAHdzE-_W=_h=rdjN0wPircqj_mjPgDRnV=E1BuCPBbLo9s3w-g@mail.gmail.com>
On 29/07/2015 06:49, Venkatesh Srinivas wrote:
>>> You can call it even feature^Wbug, I won't take it personal. :) It does
>>> not prevent scary messages (such as "intel_rapl: no valid rapl domains
>>> found in package 0") in the logs for example. See
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1178491 for a discussion
>>> about such scary messages.
>
> This bug is not openly readable.
Oops, opened now.
> Which MSR accesses (in perf/etc) don't use safe {RD,WR}MSR accesses currently?
For example see boost_state in acpi-cpufreq.c and KVM commit
22d48b2d2aa0 ("KVM: svm: writes to MSR_K7_HWCR generates GPE in guest",
2014-06-26).
See also commit dc9b2d933a1d5782b70977024f862759c8ebb2f7 in KVM.
Paolo
next prev parent reply other threads:[~2015-07-29 8:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 17:33 Should KVM_GUEST stop depending on PARAVIRT? Andy Lutomirski
2015-07-27 13:59 ` Paolo Bonzini
2015-07-27 15:56 ` Andy Lutomirski
2015-07-27 17:49 ` Paolo Bonzini
2015-07-27 17:51 ` Andy Lutomirski
2015-07-27 18:30 ` Paolo Bonzini
2015-07-27 18:45 ` Andy Lutomirski
2015-07-27 19:04 ` Arjan van de Ven
2015-07-28 9:57 ` Paolo Bonzini
2015-07-29 0:23 ` Andy Lutomirski
2015-07-29 4:49 ` Venkatesh Srinivas
2015-07-29 8:27 ` Paolo Bonzini [this message]
2015-07-29 9:19 ` Peter Zijlstra
2015-07-29 9:24 ` Paolo Bonzini
2015-07-29 9:40 ` Peter Zijlstra
2015-07-29 9:41 ` Paolo Bonzini
2015-07-30 0:14 ` Andy Lutomirski
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=55B88E7B.3010102@redhat.com \
--to=pbonzini@redhat.com \
--cc=arjan@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=venkateshs@google.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.