public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
To: Balaji Rao <balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC] nmi watchdog in kvm
Date: Mon, 28 Jan 2008 11:57:46 +0100	[thread overview]
Message-ID: <20080128105746.GC32342@elte.hu> (raw)
In-Reply-To: <200801281348.41010.balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


* Balaji Rao <balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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/

  parent reply	other threads:[~2008-01-28 10:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28  8:18 [RFC] nmi watchdog in kvm Balaji Rao
     [not found] ` <200801281348.41010.balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-01-28 10:57   ` Ingo Molnar [this message]
2008-01-28 12:29   ` Joerg Roedel
     [not found]     ` <20080128122925.GA11803-5C7GfCeVMHo@public.gmane.org>
2008-01-28 14:42       ` Balaji Rao
     [not found]         ` <200801282012.26225.balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-01-28 15:00           ` Joerg Roedel
     [not found]             ` <20080128150032.GF6960-5C7GfCeVMHo@public.gmane.org>
2008-01-28 16:30               ` Balaji Rao
2008-01-30 10:43   ` Avi Kivity
     [not found]     ` <47A054EE.6010408-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-30 14:22       ` Balaji Rao
     [not found]         ` <200801301952.57604.balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-01-30 14:39           ` Avi Kivity
     [not found]             ` <47A08C24.8040505-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-30 15:02               ` Balaji Rao
     [not found]                 ` <200801302032.01603.balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-01-30 15:13                   ` Avi Kivity

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=20080128105746.GC32342@elte.hu \
    --to=mingo-x9un+bfzkdi@public.gmane.org \
    --cc=balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox