[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v4 3/3] x86/monitor: don't use hvm_funcs directly





On Thu, Jul 9, 2015 at 4:15 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>> On 09.07.15 at 08:15, <rcojocaru@xxxxxxxxxxxxxxx> wrote:
> On 07/09/2015 01:52 AM, Tamas K Lengyel wrote:
>> --- a/xen/include/asm-x86/hvm/hvm.h
>> +++ b/xen/include/asm-x86/hvm/hvm.h
>> @@ -514,6 +514,17 @@ static inline enum hvm_intblk nhvm_interrupt_blocked(struct vcpu *v)
>>      return hvm_funcs.nhvm_intr_blocked(v);
>>  }
>>
>> +static inline int hvm_enable_msr_exit_interception(struct domain *d)
>> +{
>> +    if ( hvm_funcs.enable_msr_exit_interception )
>> +    {
>> +        hvm_funcs.enable_msr_exit_interception(d);
>> +        return 0;
>> +    }
>> +
>> +    return -ENOSYS;
>> +}
>> +

FWIW I agree that this would better return bool_t.

Jan

Sure, that's fine by me.

Thanks,
Tamas

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.