From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Should KVM_GUEST stop depending on PARAVIRT? Date: Wed, 29 Jul 2015 10:27:39 +0200 Message-ID: <55B88E7B.3010102@redhat.com> References: <55B63933.4090702@redhat.com> <55B66F42.3000202@redhat.com> <55B678B5.8040602@redhat.com> <55B75225.8080505@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Peter Zijlstra , KVM list , Arjan van de Ven To: Venkatesh Srinivas , Andy Lutomirski Return-path: Received: from mx1.redhat.com ([209.132.183.28]:36085 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751506AbbG2I1n (ORCPT ); Wed, 29 Jul 2015 04:27:43 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 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