| 2019-04-02 14:51:28 |
Heitor Alves de Siqueira |
bug |
|
|
added bug |
| 2019-04-02 14:51:43 |
Heitor Alves de Siqueira |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-04-02 14:51:43 |
Heitor Alves de Siqueira |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2019-04-02 14:51:43 |
Heitor Alves de Siqueira |
nominated for series |
|
Ubuntu Xenial |
|
| 2019-04-02 14:51:43 |
Heitor Alves de Siqueira |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2019-04-02 14:52:15 |
Heitor Alves de Siqueira |
linux (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2019-04-02 14:52:18 |
Heitor Alves de Siqueira |
linux (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2019-04-02 14:52:22 |
Heitor Alves de Siqueira |
linux (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2019-04-02 14:52:23 |
Heitor Alves de Siqueira |
linux (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-04-02 14:52:32 |
Heitor Alves de Siqueira |
tags |
|
sts |
|
| 2019-04-02 14:53:39 |
Heitor Alves de Siqueira |
description |
[Impact]
* TSC clocksource not available in nested guests
[Test Case]
* Spin up a nested Xenial/Bionic guest and check for 'tsc' at
/sys/devices/system/clocksource/clocksource0/available_clocksource
[Regression Potential]
* The regression potential is low. Upstream code still maintains this
behaviour of skipping calibration on guests, and tsc code verifies if
the frequency is known before registering the clocksource
* Patches were verified against the above test case, and also tested
with stress-ng in both nested and non-nested guest scenarios
[Fix]
* By applying the upstream commits, we skip refined calibration and
register TSC as a clocksource directly if its frequency is known (via
MSR or CPUID) |
[Impact]
* TSC clocksource not available in nested guests
[Test Case]
* Spin up a nested Xenial/Bionic guest and check for 'tsc' at
/sys/devices/system/clocksource/clocksource0/available_clocksource
[Regression Potential]
* The regression potential is low. Upstream code still maintains this
behaviour of skipping calibration on guests, and tsc code verifies if
the frequency is known before registering the clocksource
* Patches were verified against the above test case, and also tested
with stress-ng in both nested and non-nested guest scenarios
[Fix]
* By applying the upstream commits [0] [1], we skip refined calibration and
register TSC as a clocksource directly if its frequency is known (via
MSR or CPUID)
[0] For Xenial only - https://git.kernel.org/linus/47c95a46d0f
[1] https://git.kernel.org/linus/e10f78050323 |
|
| 2019-04-02 15:00:06 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-04-02 15:16:24 |
Heitor Alves de Siqueira |
description |
[Impact]
* TSC clocksource not available in nested guests
[Test Case]
* Spin up a nested Xenial/Bionic guest and check for 'tsc' at
/sys/devices/system/clocksource/clocksource0/available_clocksource
[Regression Potential]
* The regression potential is low. Upstream code still maintains this
behaviour of skipping calibration on guests, and tsc code verifies if
the frequency is known before registering the clocksource
* Patches were verified against the above test case, and also tested
with stress-ng in both nested and non-nested guest scenarios
[Fix]
* By applying the upstream commits [0] [1], we skip refined calibration and
register TSC as a clocksource directly if its frequency is known (via
MSR or CPUID)
[0] For Xenial only - https://git.kernel.org/linus/47c95a46d0f
[1] https://git.kernel.org/linus/e10f78050323 |
[Impact]
* TSC clocksource not available in nested guests
[Test Case]
* Spin up a nested Xenial/Bionic guest and check for 'tsc' at
/sys/devices/system/clocksource/clocksource0/available_clocksource
[Regression Potential]
* The regression potential is low. Upstream code still maintains this
behaviour of skipping calibration on guests, and tsc code verifies if
the frequency is known before registering the clocksource
* Patches were verified against the above test case, and also tested
with stress-ng in both nested and non-nested guest scenarios
[Fix]
* By applying the upstream commits [0] [1], we skip refined calibration and
register TSC as a clocksource directly if its frequency is known (via
MSR or CPUID)
* Cosmic onwards (kernel 4.18+) are already fixed
[0] For Xenial only - https://git.kernel.org/linus/47c95a46d0f
[1] https://git.kernel.org/linus/e10f78050323 |
|
| 2019-04-02 16:52:10 |
Heitor Alves de Siqueira |
linux (Ubuntu): status |
Incomplete |
Fix Released |
|
| 2019-04-02 17:36:53 |
Heitor Alves de Siqueira |
linux (Ubuntu Xenial): assignee |
|
Heitor R. Alves de Siqueira (halves) |
|
| 2019-04-02 17:36:55 |
Heitor Alves de Siqueira |
linux (Ubuntu Bionic): assignee |
|
Heitor R. Alves de Siqueira (halves) |
|
| 2019-04-15 04:11:32 |
Khaled El Mously |
linux (Ubuntu Bionic): status |
Confirmed |
Fix Committed |
|
| 2019-04-15 04:13:09 |
Khaled El Mously |
linux (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2019-04-26 14:31:41 |
Ubuntu Kernel Bot |
tags |
sts |
sts verification-needed-xenial |
|
| 2019-04-29 16:04:18 |
Ubuntu Kernel Bot |
tags |
sts verification-needed-xenial |
sts verification-needed-bionic verification-needed-xenial |
|
| 2019-04-29 19:23:03 |
Heitor Alves de Siqueira |
tags |
sts verification-needed-bionic verification-needed-xenial |
sts verification-done-xenial verification-needed-bionic |
|
| 2019-04-29 19:24:31 |
Heitor Alves de Siqueira |
tags |
sts verification-done-xenial verification-needed-bionic |
sts verification-done-bionic verification-done-xenial |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2017-5715 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2017-5753 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2017-5754 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2018-12126 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2018-12127 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2018-12130 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2018-16884 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2018-3620 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2018-3639 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2018-3646 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2019-3874 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2019-3882 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2019-9500 |
|
| 2019-05-14 19:00:51 |
Launchpad Janitor |
cve linked |
|
2019-9503 |
|
| 2019-05-14 19:08:52 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
