[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5018EBAF.9090404@redhat.com>
Date:	Wed, 01 Aug 2012 11:41:19 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Marcelo Tosatti <mtosatti@...hat.com>
CC:	Markus Trippelsdorf <markus@...ppelsdorf.de>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org, Gleb Natapov <gleb@...hat.com>,
	Joerg Roedel <joerg.roedel@....com>,
	Jan Kiszka <jan.kiszka@...mens.com>
Subject: Re: [RFC PATCH] KVM: Only print vcpu_unimpl when DEBUG is set
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 <markus@...ppelsdorf.de>
> 
> It could be useful for debugging (but then lots of other things could).
> 
> Anyone has a use for this?
The current scenario is:
<guest breaks>
Maintainer asks for dmesg
If something shows up, it's something to consider
Following this patch, the scenario will be
<guest breaks>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
