* Re: [PATCH] x86/kernel/cpu/amd.c: don't apply the lahf_lm workaround in a hypervisor [not found] ` <alpine.LRH.2.02.1707122220530.9089@file01.intranet.prod.int.rdu2.redhat.com> @ 2017-07-13 6:32 ` Borislav Petkov 2017-07-21 11:34 ` Mikulas Patocka 0 siblings, 1 reply; 3+ messages in thread From: Borislav Petkov @ 2017-07-13 6:32 UTC (permalink / raw) To: Mikulas Patocka Cc: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, x86, linux-kernel, kvm-ML On Wed, Jul 12, 2017 at 10:27:44PM -0400, Mikulas Patocka wrote: > It is not strictly needed, but it is annoying. I work in the console and > it is annoying to see these "unhandled rdmsr" messages printed over the > screen every time I reboot a virtual machine. Those messages are already pr_debug_ratelimited(). Fix your loglevel to not see them. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] x86/kernel/cpu/amd.c: don't apply the lahf_lm workaround in a hypervisor 2017-07-13 6:32 ` [PATCH] x86/kernel/cpu/amd.c: don't apply the lahf_lm workaround in a hypervisor Borislav Petkov @ 2017-07-21 11:34 ` Mikulas Patocka 2017-07-21 12:28 ` Borislav Petkov 0 siblings, 1 reply; 3+ messages in thread From: Mikulas Patocka @ 2017-07-21 11:34 UTC (permalink / raw) To: Borislav Petkov Cc: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, x86, linux-kernel, kvm-ML On Thu, 13 Jul 2017, Borislav Petkov wrote: > On Wed, Jul 12, 2017 at 10:27:44PM -0400, Mikulas Patocka wrote: > > It is not strictly needed, but it is annoying. I work in the console and > > it is annoying to see these "unhandled rdmsr" messages printed over the > > screen every time I reboot a virtual machine. > > Those messages are already pr_debug_ratelimited(). Fix your loglevel to > not see them. The message 'unhandled rdmsr' is printed with "pr_err_ratelimited" in the kernels up to and including 4.9. So it can't be easily silenced, silencing it silences any errors. (and I can't use kernels newer that 4.4 on the host machine because of broken hibernation) Mikulas > -- > Regards/Gruss, > Boris. > > ECO tip #101: Trim your mails when you reply. > -- ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] x86/kernel/cpu/amd.c: don't apply the lahf_lm workaround in a hypervisor 2017-07-21 11:34 ` Mikulas Patocka @ 2017-07-21 12:28 ` Borislav Petkov 0 siblings, 0 replies; 3+ messages in thread From: Borislav Petkov @ 2017-07-21 12:28 UTC (permalink / raw) To: Mikulas Patocka Cc: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, x86, linux-kernel, kvm-ML On Fri, Jul 21, 2017 at 07:34:59AM -0400, Mikulas Patocka wrote: > (and I can't use kernels newer that 4.4 on the host machine because of > broken hibernation) And what do we do with upstream patches which we need in older kernels? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-07-21 12:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <alpine.LRH.2.02.1707120318530.4739@file01.intranet.prod.int.rdu2.redhat.com>
[not found] ` <20170712134706.GA20584@nazgul.tnic>
[not found] ` <alpine.LRH.2.02.1707122220530.9089@file01.intranet.prod.int.rdu2.redhat.com>
2017-07-13 6:32 ` [PATCH] x86/kernel/cpu/amd.c: don't apply the lahf_lm workaround in a hypervisor Borislav Petkov
2017-07-21 11:34 ` Mikulas Patocka
2017-07-21 12:28 ` Borislav Petkov
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox