From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [RFC] nmi watchdog in kvm Date: Mon, 28 Jan 2008 11:57:46 +0100 Message-ID: <20080128105746.GC32342@elte.hu> References: <200801281348.41010.balajirrao@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Balaji Rao Return-path: Content-Disposition: inline In-Reply-To: <200801281348.41010.balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org * Balaji Rao wrote: > I was trying to enable the use of nmi watchdog within a linux guest > running in kvm. I have done it by allowing direct access to perfmon > msrs using the MSR_BITMAP field in vmcs region. your patch looks pretty clean and simple to me - and it would make quite a bit of sense from the "completeness of architecture" POV to inject NMIs into KVM - even though it's obviously not that hard to interrupt a KVM guest context via other means ;-) at the least this would test the correctness of guest kernel NMI handling. We could even test things by injecting a very large stream of NMIs, which is not that easy on native hardware, etc. ( the emulation of "NMI reason" IO port could be accelerated too perhaps, instead of passing it over to qemu. ) so it's a good idea IMO. Ingo ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/