All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: VMX: simplify NMI mask management
Date: Wed, 23 Mar 2011 16:10:09 +0100	[thread overview]
Message-ID: <4D8A0D51.10204@siemens.com> (raw)
In-Reply-To: <4D8A0A92.7030105@redhat.com>

On 2011-03-23 15:58, Avi Kivity wrote:
> On 03/23/2011 04:54 PM, Jan Kiszka wrote:
>>>  @@ -3991,9 +3987,7 @@ static void __vmx_complete_interrupts(struct vcpu_vmx *vmx,
>>>   		* Clear bit "block by NMI" before VM entry if a NMI
>>>   		* delivery faulted.
>>>   		*/
>>>  -		vmcs_clear_bits(GUEST_INTERRUPTIBILITY_INFO,
>>>  -				GUEST_INTR_STATE_NMI);
>>>  -		vmx->nmi_known_unmasked = true;
>>>  +		vmx_set_nmi_mask(&vmx->vcpu, false);
>>>   		break;
>>>   	case INTR_TYPE_SOFT_EXCEPTION:
>>>   		vmx->vcpu.arch.event_exit_inst_len =
>>
>> Looks consistent to me, but maybe you should update the comment above
>> that's now also applied to the emulated mask.
> 
> In what way?
> 
>          /*
>           * SDM 3: 27.7.1.2 (September 2008)
>           * Clear bit "block by NMI" before VM entry if a NMI
>           * delivery faulted.
>           */
> 
> Seems pretty descriptive.

IIRC, the above only applies to CPUs that support VNMI and is
meaningless for older ones. But vmx_set_nmi_mask is not void for those
old CPUs.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-03-23 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 13:12 [PATCH] KVM: VMX: simplify NMI mask management Avi Kivity
2011-03-23 14:54 ` Jan Kiszka
2011-03-23 14:58   ` Avi Kivity
2011-03-23 15:10     ` Jan Kiszka [this message]
2011-03-23 16:28       ` Avi Kivity
2011-03-23 17:14         ` 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=4D8A0D51.10204@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.