From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Guest handling of IA32_DEBUGCTL MSR
Date: Tue, 28 Apr 2015 13:43:29 +0200
Message-ID: <553F7261.40500@redhat.com>
References: <07377BC4-FD59-4A2E-9FA8-28ABE1B7F6D2@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
To: Nadav Amit <nadav.amit@gmail.com>, kvm list <kvm@vger.kernel.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:56215 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S964975AbbD1Lni (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 28 Apr 2015 07:43:38 -0400
In-Reply-To: <07377BC4-FD59-4A2E-9FA8-28ABE1B7F6D2@gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>



On 28/04/2015 13:42, Nadav Amit wrote:
> It seems strange that the guest is allowed to set IA32_DEBUGCTL MSR for the
> nested VM and get this value to the physical IA32_DEBUGCTL (see
> prepare_vmcs02), while it cannot set IA32_DEBUGCTL for itself (see
> kvm_set_msr_common).
> 
> Am I missing something?

No, it makes no sense.

Paolo