public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>
Subject: Re: [PATCH] kvm: cleanup CR8 handling
Date: Tue, 21 Dec 2010 11:07:50 +0100	[thread overview]
Message-ID: <4D107C76.8000605@amd.com> (raw)
In-Reply-To: <4D060CB4.9000207@redhat.com>

Avi Kivity wrote:
> On 12/08/2010 01:27 PM, Andre Przywara wrote:
>> The handling of CR8 writes in KVM is currently somewhat cumbersome.
>> This patch makes it look like the other CR register handlers
>> and fixes a possible issue in VMX, where the RIP would be incremented
>> despite an injected #GP.
>>
>>   unsigned long kvm_get_cr8(struct kvm_vcpu *vcpu)
>> @@ -4104,7 +4098,7 @@ static int emulator_set_cr(int cr, unsigned long val, struct kvm_vcpu *vcpu)
>>   		res = kvm_set_cr4(vcpu, mk_cr_64(kvm_read_cr4(vcpu), val));
>>   		break;
>>   	case 8:
>> -		res = __kvm_set_cr8(vcpu, val&  0xfUL);
>> +		res = kvm_set_cr8(vcpu, val);
>>   		break;
>>   	default:
>>   		vcpu_printf(vcpu, "%s: unexpected cr %u\n", __func__, cr);
> 
> Why drop the mask?
Because it is checked in kvm_set_cr8 itself. If it is wrong, the caller 
should get a #GP as described in the manual. By masking this out we 
would never deliver the #GP to the guest.

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448-3567-12


  reply	other threads:[~2010-12-21 10:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 11:27 [PATCH] kvm: cleanup CR8 handling Andre Przywara
2010-12-13 12:08 ` Avi Kivity
2010-12-21 10:07   ` Andre Przywara [this message]
2010-12-21 10:56     ` 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=4D107C76.8000605@amd.com \
    --to=andre.przywara@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox