[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160310193419.GA2657@potion.brq.redhat.com>
Date: Thu, 10 Mar 2016 20:34:19 +0100
From: Radim Krčmář <rkrcmar@...hat.com>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>
Cc: pbonzini@...hat.com, joro@...tes.org, bp@...en8.de,
gleb@...nel.org, alex.williamson@...hat.com, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, wei@...hat.com,
sherry.hurwitz@....com
Subject: Re: [PART1 RFC v2 07/10] svm: Add VMEXIT handlers for AVIC
2016-03-09 21:55+0100, Radim Krčmář:
> 2016-03-04 14:46-0600, Suravee Suthikulpanit:
>> +static int avic_noaccel_interception(struct vcpu_svm *svm)
>> +{
>> + int ret = 0;
>> + u32 offset = svm->vmcb->control.exit_info_1 & 0xFF0;
>> + u32 rw = (svm->vmcb->control.exit_info_1 >> 32) & 0x1;
>
> Change "u32 rw" to "bool write"
>
>> + u32 vector = svm->vmcb->control.exit_info_2 & 0xFFFFFFFF;
>
> and please #define those masks.
I reconsidered. Other users are being removed, so these masks will be
used only once and properly named variables are better then.
vector isn't used right now ... is the EOI vector you get by reading the
APIC page equal to it?
(Btw. edge EOI hacks for PIT and RTC won't work because AVIC doesn't
exit when TMR=0, but I'd take it slow and tackle those after v3.)
Powered by blists - more mailing lists