x86/viridian: make the threshold for HvNotifyLongSpinWait tunable

The current threshold before the guest issues the hypercall is, and always
has been, hard-coded to 2047. It is not clear where this number came
from so, to at least allow for ease of experimentation, this patch makes
the threshold tunable via the Xen command line.

Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
This commit is contained in:
Paul Durrant authored and Jan Beulich committed 2017-03-23 15:51:45 +01:00
1 parent 422db534e8
commit bf13fe76c5
2 files changed
+23 -1

No files matched your search

+8
View File
@@ -1624,6 +1624,14 @@ relinquish control to dom0.
<major>, <minor> and <build> must be integers. The values will be
encoded in guest CPUID 0x40000002 if viridian enlightenments are enabled.
### viridian-spinlock-retry-count
> `= <integer>`
> Default: `2047`
Specify the maximum number of retries before an enlightened Windows
guest will notify Xen that it has failed to acquire a spinlock.
### vpid (Intel)
> `= <boolean>`
+15 -1
View File
@@ -174,6 +174,14 @@ static uint16_t __read_mostly viridian_major = 6;
static uint16_t __read_mostly viridian_minor = 0;
static uint32_t __read_mostly viridian_build = 0x1772;
/*
* Maximum number of retries before the guest will notify of failure
* to acquire a spinlock.
*/
static uint32_t __read_mostly viridian_spinlock_retry_count = 2047;
integer_param("viridian-spinlock-retry-count",
viridian_spinlock_retry_count);
void cpuid_viridian_leaves(const struct vcpu *v, uint32_t leaf,
uint32_t subleaf, struct cpuid_leaf *res)
{
@@ -251,7 +259,13 @@ void cpuid_viridian_leaves(const struct vcpu *v, uint32_t leaf,
res->a |= CPUID4A_HCALL_REMOTE_TLB_FLUSH;
if ( !cpu_has_vmx_apic_reg_virt )
res->a |= CPUID4A_MSR_BASED_APIC;
res->b = 2047; /* long spin count */
/*
* This value is the recommended number of attempts to try to
* acquire a spinlock before notifying the hypervisor via the
* HvNotifyLongSpinWait hypercall.
*/
res->b = viridian_spinlock_retry_count;
break;
case 6:
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.