How do I know if the STIBP slow patches were backported to my ubuntu kernel?
up vote
1
down vote
favorite
This article https://www.phoronix.com/scan.php?page=article&item=linux-420wip-stibp&num=1 discusses the performance impact of recent STIBP patches were released in kernel 4.19 and backported to LTS kernels.
The result was apparently to basically turn off hyperthreading, bad for Intel CPUs.
Then, changes were made in the last few days so that the performance impact is much lower by only applying this mitigation when it is most likely to reduce an actual security threat.
How can I tell if recent ubuntu kernels have the 4.19 STIBP patch backported (bad performance) or if they have also had the recent improvements backported, or if the 4.19 changes never made it to the ubuntu kernels at all?
I use 18.04.1 mainly, but I have the 4.18 generic-hwe prerelease kernel.
kernel
asked Nov 30 at 4:33
Tim Richardson
626415
add a comment |
up vote
1
down vote
favorite
This article https://www.phoronix.com/scan.php?page=article&item=linux-420wip-stibp&num=1 discusses the performance impact of recent STIBP patches were released in kernel 4.19 and backported to LTS kernels.
The result was apparently to basically turn off hyperthreading, bad for Intel CPUs.
Then, changes were made in the last few days so that the performance impact is much lower by only applying this mitigation when it is most likely to reduce an actual security threat.
How can I tell if recent ubuntu kernels have the 4.19 STIBP patch backported (bad performance) or if they have also had the recent improvements backported, or if the 4.19 changes never made it to the ubuntu kernels at all?
I use 18.04.1 mainly, but I have the 4.18 generic-hwe prerelease kernel.
kernel
asked Nov 30 at 4:33
Tim Richardson
626415
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
This article https://www.phoronix.com/scan.php?page=article&item=linux-420wip-stibp&num=1 discusses the performance impact of recent STIBP patches were released in kernel 4.19 and backported to LTS kernels.
The result was apparently to basically turn off hyperthreading, bad for Intel CPUs.
Then, changes were made in the last few days so that the performance impact is much lower by only applying this mitigation when it is most likely to reduce an actual security threat.
How can I tell if recent ubuntu kernels have the 4.19 STIBP patch backported (bad performance) or if they have also had the recent improvements backported, or if the 4.19 changes never made it to the ubuntu kernels at all?
I use 18.04.1 mainly, but I have the 4.18 generic-hwe prerelease kernel.
kernel
asked Nov 30 at 4:33
Tim Richardson
626415
This article https://www.phoronix.com/scan.php?page=article&item=linux-420wip-stibp&num=1 discusses the performance impact of recent STIBP patches were released in kernel 4.19 and backported to LTS kernels.
The result was apparently to basically turn off hyperthreading, bad for Intel CPUs.
Then, changes were made in the last few days so that the performance impact is much lower by only applying this mitigation when it is most likely to reduce an actual security threat.
How can I tell if recent ubuntu kernels have the 4.19 STIBP patch backported (bad performance) or if they have also had the recent improvements backported, or if the 4.19 changes never made it to the ubuntu kernels at all?
I use 18.04.1 mainly, but I have the 4.18 generic-hwe prerelease kernel.
kernel
kernel
asked Nov 30 at 4:33
Tim Richardson
626415
asked Nov 30 at 4:33
Tim Richardson
626415
asked Nov 30 at 4:33
Tim Richardson
626415
asked Nov 30 at 4:33
Tim Richardson
626415
asked Nov 30 at 4:33
Tim Richardson
626415
626415
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1097332%2fhow-do-i-know-if-the-stibp-slow-patches-were-backported-to-my-ubuntu-kernel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
