On Wed, May 24, 2017 at 3:03 PM, Vitaly Kuznetsov wrote:
> Max virtual processor will be needed for 'extended' hypercalls supporting
> more than 64 vCPUs. While on it, unify on 'Hyper-V' in mshyperv.c as we
> currently have a mix, report acquired misc features as well.
>
> Signed-off-by: Vitaly Ku
On Wed, May 24, 2017 at 3:03 PM, Vitaly Kuznetsov wrote:
> We have only three call sites for hv_do_hypercall() and we're going to
> change HVCALL_SIGNAL_EVENT to doing fast hypercall so we can inline this
> function for optimization.
>
> Hyper-V top level functional specification states that r9-r1
On Wed, May 24, 2017 at 3:03 PM, Vitaly Kuznetsov wrote:
> Hyper-V supports 'fast' hypercalls when all parameters are passed through
> registers. Implement an inline version of a simpliest of these calls:
> hypercall with one 8-byte input and no output.
>
> Proper hypercall input interface (struct
On Wed, May 24, 2017 at 3:04 PM, Vitaly Kuznetsov wrote:
> We need to pass only 8 bytes of input for HvSignalEvent which makes it a
> perfect fit for fast hypercall. hv_input_signal_event_buffer is not needed
> any more and hv_input_signal_event is converted to union for convenience.
> +union hv_
On Wed, May 24, 2017 at 3:04 PM, Vitaly Kuznetsov wrote:
> Hyper-V hosts may support more than 64 vCPUs, we need to use
> HVCALL_FLUSH_VIRTUAL_ADDRESS_SPACE_EX/LIST_EX hypercalls in this
> case.
> +{
> + /*
> +* We can't be sure that translated vcpu numbers will always be
> +
On Tue, May 23, 2017 at 10:38 PM, Greg Kroah-Hartman
wrote:
> On Tue, May 23, 2017 at 09:32:13PM +0200, Raphaël Beamonte wrote:
>> drivers/staging/lustre/lustre/llite/xattr.c:89:62: warning: Variable
>> length array is used.
>> drivers/staging/lustre/lustre/llite/xattr.c:366:62: warning: Variable
