| 2020-04-27 18:18:27 |
Joseph Salisbury |
bug |
|
|
added bug |
| 2020-04-30 13:47:38 |
Marcelo Cerri |
bug task added |
|
linux-azure-4.15 (Ubuntu) |
|
| 2020-04-30 13:48:42 |
Marcelo Cerri |
bug task added |
|
linux-azure-5.3 (Ubuntu) |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
nominated for series |
|
Ubuntu Focal |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
bug task added |
|
linux-azure (Ubuntu Focal) |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
bug task added |
|
linux-azure-5.3 (Ubuntu Focal) |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
bug task added |
|
linux-azure-4.15 (Ubuntu Focal) |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
bug task added |
|
linux-azure (Ubuntu Eoan) |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
bug task added |
|
linux-azure-5.3 (Ubuntu Eoan) |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
bug task added |
|
linux-azure-4.15 (Ubuntu Eoan) |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
bug task added |
|
linux-azure (Ubuntu Bionic) |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
bug task added |
|
linux-azure-5.3 (Ubuntu Bionic) |
|
| 2020-04-30 13:48:57 |
Marcelo Cerri |
bug task added |
|
linux-azure-4.15 (Ubuntu Bionic) |
|
| 2020-04-30 13:49:10 |
Marcelo Cerri |
linux-azure (Ubuntu Bionic): status |
New |
Invalid |
|
| 2020-04-30 13:50:46 |
Marcelo Cerri |
linux-azure (Ubuntu Eoan): status |
New |
Confirmed |
|
| 2020-04-30 13:50:57 |
Marcelo Cerri |
linux-azure (Ubuntu Focal): status |
New |
Confirmed |
|
| 2020-04-30 13:51:10 |
Marcelo Cerri |
bug task deleted |
linux-azure-5.3 (Ubuntu) |
|
|
| 2020-04-30 13:51:19 |
Marcelo Cerri |
bug task deleted |
linux-azure-5.3 (Ubuntu Bionic) |
|
|
| 2020-04-30 13:51:27 |
Marcelo Cerri |
bug task deleted |
linux-azure-5.3 (Ubuntu Eoan) |
|
|
| 2020-04-30 13:51:34 |
Marcelo Cerri |
bug task deleted |
linux-azure-5.3 (Ubuntu Focal) |
|
|
| 2020-04-30 13:51:55 |
Marcelo Cerri |
linux-azure-4.15 (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2020-04-30 13:51:59 |
Marcelo Cerri |
linux-azure-4.15 (Ubuntu Eoan): status |
New |
Invalid |
|
| 2020-04-30 13:52:01 |
Marcelo Cerri |
linux-azure-4.15 (Ubuntu Focal): status |
New |
Invalid |
|
| 2020-06-10 08:03:36 |
Stefan Bader |
linux-azure-4.15 (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2020-06-10 08:03:44 |
Stefan Bader |
linux-azure-4.15 (Ubuntu): status |
New |
Invalid |
|
| 2020-06-10 08:03:52 |
Stefan Bader |
linux-azure (Ubuntu): status |
New |
Invalid |
|
| 2020-06-10 08:04:12 |
Stefan Bader |
linux-azure (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2020-06-10 08:04:19 |
Stefan Bader |
linux-azure (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2020-07-03 08:48:47 |
Po-Hsu Lin |
bug |
|
|
added subscriber Po-Hsu Lin |
| 2020-08-12 17:59:01 |
Kelsey Steele |
description |
Microsoft would like to request two commits in all releases supported on Azure. These commits benefit SAP workloads.
These requested commits will enable support for Invariant TSC in Linux guest VMs. The invariant TSC means that the TSC continues at a fixed rate regardless of the C-state or frequency of the processor (as long as the processor remains in the ACPI S0 state).
These patches will allow guests to access the HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic MSR, which then enables the InvariantTSC feature. After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
The following two commits enable support:
9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/ InvariantTSC")
dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC") |
[Impact]
Microsoft would like to request two commits in all releases supported on Azure. These commits benefit SAP workloads.
These requested commits will enable support for Invariant TSC in Linux guest VMs. The invariant TSC means that the TSC continues at a fixed rate regardless of the C-state or frequency of the processor (as long as the processor remains in the ACPI S0 state).
These patches will allow guests to access the HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic MSR, which then enables the InvariantTSC feature. After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
The following two commits enable support:
9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/ InvariantTSC")
dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC")
[Test Case]
If the hardware supports TSC scaling, Hyper-V will set bit 15 of the HV_PARTITION_PRIVILEGE_MASK in guest VMs with a compatible Hyper-V configuration version. Bit 15 corresponds to the AccessTscInvariantControls privilege. If this privilege bit is set, guests can access the HvSyntheticInvariantTscControl MSR: guests can set bit 0 of this synthetic MSR to enable the InvariantTSC feature.
After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
[Regression Potential]
If the patches fail to enable support for Invariant TSC or doesn't set the TSC clocksource as the default when Invariant TSC is available, while this would be an error it wouldn't be a regression. Possibility of finding problems using the TSC clocksource once support has been enabled.
a 4.15 test kernel was sent to Microsoft for testing. Result came back verified to allow enabling support for Invariant TSC and there was no report of known regression.
The 4.15, 5.3, & 5.4 kernels with patches applied were boot tested and verified no changes to dmesg logs relating to clocksource or tsc. tsc autotest ran successfully on the 4.15 before and after applying the requested patches. |
|
| 2020-08-12 17:59:52 |
Kelsey Steele |
linux-azure (Ubuntu Eoan): status |
Confirmed |
Won't Fix |
|
| 2020-08-12 18:39:55 |
Kelsey Steele |
description |
[Impact]
Microsoft would like to request two commits in all releases supported on Azure. These commits benefit SAP workloads.
These requested commits will enable support for Invariant TSC in Linux guest VMs. The invariant TSC means that the TSC continues at a fixed rate regardless of the C-state or frequency of the processor (as long as the processor remains in the ACPI S0 state).
These patches will allow guests to access the HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic MSR, which then enables the InvariantTSC feature. After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
The following two commits enable support:
9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/ InvariantTSC")
dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC")
[Test Case]
If the hardware supports TSC scaling, Hyper-V will set bit 15 of the HV_PARTITION_PRIVILEGE_MASK in guest VMs with a compatible Hyper-V configuration version. Bit 15 corresponds to the AccessTscInvariantControls privilege. If this privilege bit is set, guests can access the HvSyntheticInvariantTscControl MSR: guests can set bit 0 of this synthetic MSR to enable the InvariantTSC feature.
After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
[Regression Potential]
If the patches fail to enable support for Invariant TSC or doesn't set the TSC clocksource as the default when Invariant TSC is available, while this would be an error it wouldn't be a regression. Possibility of finding problems using the TSC clocksource once support has been enabled.
a 4.15 test kernel was sent to Microsoft for testing. Result came back verified to allow enabling support for Invariant TSC and there was no report of known regression.
The 4.15, 5.3, & 5.4 kernels with patches applied were boot tested and verified no changes to dmesg logs relating to clocksource or tsc. tsc autotest ran successfully on the 4.15 before and after applying the requested patches. |
[Impact]
Microsoft would like to request two commits in all releases supported on Azure. These commits benefit SAP workloads.
These requested commits will enable support for Invariant TSC in Linux guest VMs. The invariant TSC means that the TSC continues at a fixed rate regardless of the C-state or frequency of the processor (as long as the processor remains in the ACPI S0 state).
These patches will allow guests to access the HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic MSR, which then enables the InvariantTSC feature. After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
The following two commits enable support:
9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/ InvariantTSC")
dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC")
[Test Case]
If the hardware supports TSC scaling, Hyper-V will set bit 15 of the HV_PARTITION_PRIVILEGE_MASK in guest VMs with a compatible Hyper-V configuration version. Bit 15 corresponds to the AccessTscInvariantControls privilege. If this privilege bit is set, guests can access the HvSyntheticInvariantTscControl MSR: guests can set bit 0 of this synthetic MSR to enable the InvariantTSC feature.
After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
[Regression Potential]
If the patches fail to enable support for Invariant TSC or doesn't set the TSC clocksource as the default when Invariant TSC is available, while this would be an error it wouldn't be a regression. Possibility of finding problems using the TSC clocksource once support has been enabled.
a 4.15 test kernel was sent to Microsoft for testing. Result came back verified to allow enabling support for Invariant TSC and there was no report of known regression.
The 4.15, 5.3, & 5.4 kernels with patches applied were boot tested and verified no changes to dmesg logs relating to clocksource or tsc. tsc autotest ran successfully on the 4.15 before and after applying the requested patches.
We are no longer interested in applying to Eoan/linux-azure (5.3) and
only targeted to apply the patches to bionic/azure-4.15 and focal/azure. |
|
| 2020-08-12 19:16:57 |
Kelsey Steele |
description |
[Impact]
Microsoft would like to request two commits in all releases supported on Azure. These commits benefit SAP workloads.
These requested commits will enable support for Invariant TSC in Linux guest VMs. The invariant TSC means that the TSC continues at a fixed rate regardless of the C-state or frequency of the processor (as long as the processor remains in the ACPI S0 state).
These patches will allow guests to access the HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic MSR, which then enables the InvariantTSC feature. After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
The following two commits enable support:
9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/ InvariantTSC")
dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC")
[Test Case]
If the hardware supports TSC scaling, Hyper-V will set bit 15 of the HV_PARTITION_PRIVILEGE_MASK in guest VMs with a compatible Hyper-V configuration version. Bit 15 corresponds to the AccessTscInvariantControls privilege. If this privilege bit is set, guests can access the HvSyntheticInvariantTscControl MSR: guests can set bit 0 of this synthetic MSR to enable the InvariantTSC feature.
After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
[Regression Potential]
If the patches fail to enable support for Invariant TSC or doesn't set the TSC clocksource as the default when Invariant TSC is available, while this would be an error it wouldn't be a regression. Possibility of finding problems using the TSC clocksource once support has been enabled.
a 4.15 test kernel was sent to Microsoft for testing. Result came back verified to allow enabling support for Invariant TSC and there was no report of known regression.
The 4.15, 5.3, & 5.4 kernels with patches applied were boot tested and verified no changes to dmesg logs relating to clocksource or tsc. tsc autotest ran successfully on the 4.15 before and after applying the requested patches.
We are no longer interested in applying to Eoan/linux-azure (5.3) and
only targeted to apply the patches to bionic/azure-4.15 and focal/azure. |
[Impact]
Microsoft would like to request two commits in all releases supported on Azure. These commits benefit SAP workloads.
These requested commits will enable support for Invariant TSC in Linux guest VMs. The invariant TSC means that the TSC continues at a fixed rate regardless of the C-state or frequency of the processor (as long as the processor remains in the ACPI S0 state).
These patches will allow guests to access the HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic MSR, which then enables the InvariantTSC feature. After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
The following two commits enable support:
9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/ InvariantTSC")
dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC")
[Test Case]
If the hardware supports TSC scaling, Hyper-V will set bit 15 of the HV_PARTITION_PRIVILEGE_MASK in guest VMs with a compatible Hyper-V configuration version. Bit 15 corresponds to the AccessTscInvariantControls privilege. If this privilege bit is set, guests can access the HvSyntheticInvariantTscControl MSR: guests can set bit 0 of this synthetic MSR to enable the InvariantTSC feature.
After setting the synthetic MSR, CPUID will enumerate support for InvariantTSC.
To check available and current clocksource, run the following:
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
cat /sys/devices/system/clocksource/clocksource0/current_clocksource
[Regression Potential]
If the patches fail to enable support for Invariant TSC or doesn't set the TSC clocksource as the default when Invariant TSC is available, while this would be an error it wouldn't be a regression. Possibility of finding problems using the TSC clocksource once support has been enabled.
a 4.15 test kernel was sent to Microsoft for testing. Result came back verified to allow enabling support for Invariant TSC and there was no report of known regression.
The 4.15, 5.3, & 5.4 kernels with patches applied were boot tested and verified no changes to dmesg logs relating to clocksource or tsc. tsc autotest ran successfully on the 4.15 before and after applying the requested patches.
We are no longer interested in applying to Eoan/linux-azure (5.3) and
only targeted to apply the patches to bionic/azure-4.15 and focal/azure. |
|
| 2020-08-28 04:46:19 |
Khaled El Mously |
linux-azure-4.15 (Ubuntu Bionic): status |
Confirmed |
Fix Committed |
|
| 2020-08-28 04:46:20 |
Khaled El Mously |
linux-azure (Ubuntu Focal): status |
Confirmed |
Fix Committed |
|
| 2020-09-21 10:34:03 |
Launchpad Janitor |
linux-azure-4.15 (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-09-21 10:34:03 |
Launchpad Janitor |
cve linked |
|
2020-12888 |
|
| 2020-09-21 10:41:31 |
Launchpad Janitor |
linux-azure (Ubuntu): status |
Invalid |
Fix Released |
|
| 2020-09-21 12:26:57 |
Launchpad Janitor |
linux-azure (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-09-21 12:26:57 |
Launchpad Janitor |
cve linked |
|
2019-19770 |
|
