public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] KVM: x86: Add VCPU substate for NMI states
Date: Tue, 20 Oct 2009 10:56:28 +0200	[thread overview]
Message-ID: <4ADD7B3C.5080607@siemens.com> (raw)
In-Reply-To: <4ADCF771.9070709@redhat.com>

Avi Kivity wrote:
> On 10/20/2009 05:39 AM, Gleb Natapov wrote:
>>> BTW, what happens to exceptions that fail to be delivered? Can't see
>>> where they are saved/restored across migration.
>>>
>>>      
>> The instruction that caused an exception will be re-executed after
>> migration and exception will be regenerated.
> 
> Except for debug exceptions (traps).
> 
>> But I think we should
>> migrate exception anyway for completeness.
>>    
> 
> Yes.

So save/restore kvm_vcpu_arch::exception? As another substate or as part
of a generalized NMI substate?

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-10-20  8:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 17:05 [PATCH v2 0/4] Extensible VCPU state IOCTL Jan Kiszka
2009-10-15 17:05 ` [PATCH v2 1/4] KVM: Reorder IOCTLs in main kvm.h Jan Kiszka
2009-10-15 17:05 ` [PATCH v2 2/4] KVM: Add unified KVM_GET/SET_VCPU_STATE IOCTL Jan Kiszka
2009-10-15 17:05 ` [PATCH v2 3/4] KVM: x86: Add support for KVM_GET/SET_VCPU_STATE Jan Kiszka
2009-10-15 17:05 ` [PATCH v2 4/4] KVM: x86: Add VCPU substate for NMI states Jan Kiszka
2009-10-19 20:32   ` Marcelo Tosatti
2009-10-19 20:39     ` Gleb Natapov
2009-10-19 23:34       ` Avi Kivity
2009-10-20  8:56         ` Jan Kiszka [this message]
2009-10-20  9:06           ` Avi Kivity
2009-10-20  9:08             ` Gleb Natapov
2009-10-20  9:14               ` Avi Kivity
2009-10-20 11:13                 ` Marcelo Tosatti
2009-10-20 12:44                   ` Gleb Natapov
2009-10-20  8:52     ` Jan Kiszka

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=4ADD7B3C.5080607@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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