From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC PATCH] KVM: Only print vcpu_unimpl when DEBUG is set Date: Wed, 01 Aug 2012 11:41:19 +0300 Message-ID: <5018EBAF.9090404@redhat.com> References: <20120726122248.GA252@x4> <20120801031930.GB31711@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Markus Trippelsdorf , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Gleb Natapov , Joerg Roedel , Jan Kiszka To: Marcelo Tosatti Return-path: In-Reply-To: <20120801031930.GB31711@amt.cnet> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 08/01/2012 06:19 AM, Marcelo Tosatti wrote: > On Thu, Jul 26, 2012 at 02:22:48PM +0200, Markus Trippelsdorf wrote: >> Every time I start qemu-kvm on my system the following line is added to >> the syslog: >> >> vcpu0 unhandled rdmsr: 0xc0010001 >> >> AFAICS all calls to vcpu_unimpl only contain debugging info with little >> or no value for the end user. >> >> Wouldn't something like the following patch make sense? >> >> Signed-off-by: Markus Trippelsdorf > > It could be useful for debugging (but then lots of other things could). > > Anyone has a use for this? The current scenario is: Maintainer asks for dmesg If something shows up, it's something to consider Following this patch, the scenario will be Maintainer: please enable dynamic debug for kvm and reproduce If something shows up, it's something to consider I guess with dynamic debug it's acceptable, we just need to make sure that it doesn't spew tons of other stuff. -- error compiling committee.c: too many arguments to function