public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Avi Kivity <avi@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	ying.huang@intel.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2/2] KVM: Add VT-x machine check support
Date: Thu, 4 Jun 2009 16:07:27 +0200	[thread overview]
Message-ID: <20090604140727.GD1065@one.firstfloor.org> (raw)
In-Reply-To: <4A27D0FE.5000609@redhat.com>

On Thu, Jun 04, 2009 at 04:49:50PM +0300, Avi Kivity wrote:
> Andi Kleen wrote:
> >>There's no good place as it breaks the nice exit handler table.  You 
> >>could put it in vmx_complete_interrupts() next to NMI handling.
> >>    
> >
> >I think I came up with a easy cheesy but not too bad solution now that 
> >should work. It simply remembers the CPU in the vcpu structure and 
> >schedules back to it. That's fine for this purpose. 
> >  
> 
> We might be able schedule back in a timely manner.  Why not hack 
> vmx_complete_interrupts()?  You're still in the critical section so 
> you're guaranteed no delays or surprises.

Yes, have to do that. My original scheme was too risky because
the Machine checks have synchronization mechanisms now and 
preemption has no time limit.

I'll hack on it later today, hope fully have a patch tomorrow.

-Andi


-- 
ak@linux.intel.com -- Speaking for myself only.

      reply	other threads:[~2009-06-04 14:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 11:12 [PATCH] [1/2] x86: MCE: Define MCE_VECTOR Andi Kleen
2009-06-04 11:12 ` [PATCH] [2/2] KVM: Add VT-x machine check support Andi Kleen
2009-06-04 11:48   ` Avi Kivity
2009-06-04 12:51     ` Andi Kleen
2009-06-04 12:49       ` Avi Kivity
2009-06-04 13:01         ` Andi Kleen
2009-06-04 13:10           ` Avi Kivity
2009-06-04 13:20             ` Andi Kleen
2009-06-04 13:49               ` Avi Kivity
2009-06-04 14:07                 ` Andi Kleen [this message]

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=20090604140727.GD1065@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.huang@intel.com \
    /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