The Impact of Kernel Updates on Hyper-Threading Behavior

[vzvva]

Hi,

I chose to enable hyper-threading for better performance, according to this text [1]. However, every time the dom0 kernel is updated, a line is appended to the last line of this file [2]. The user expects the configuration to remain unchanged, but each time this line [3] is appended to the grub file, the "smt=" line repeats three times, and the last line disables hyper-threading.

[1] https://www.qubes-os.org/news/2018/09/02/qsb-43/ [2] /etc/default/grub [3] GRUB_CMDLINE_XEN_DEFAULT="$GRUB_CMDLINE_XEN_DEFAULT smt=off"

[marmarek]

To avoid re-disabling hyperthreading, you can comment out the existing smt=off line instead of changing it. Anyway, we do not guarantee system security if you decide to do so (as explained in that QSB doc).

[vzvva]

Thanks, I will try it. My laptop is slow and i need to enable it.

[github-actions[bot]]

This issue has been closed as "not applicable." Here are some common examples of cases in which issues are closed as not applicable:

• Help and support requests (please see Help, support, mailing lists, and forum)
• Questions (please see Help, support, mailing lists, and forum)
• Discussion issues (please see Help, support, mailing lists, and forum)
• Bug reports for behavior that is already working as intended
• Enhancement requests to improve things that are already working as intended
• Issues that rest on mistaken assumptions or misunderstandings
• Issues that do not provide enough information
• Issues that are not actionable

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

Regarding help and support requests, please note that this issue tracker (qubes-issues) is not intended to serve as a help desk or tech support center. Instead, we've set up other venues where you can ask for help and support, ask questions, and have discussions. By contrast, the issue tracker is more of a technical tool intended to support our developers in their work. We thank you for your understanding.

If anyone reading this believes that this issue was closed in error or that the resolution of "not applicable" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.