From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] kvm_pagefault01: Do not write into tdp_mmu sysfile
Date: Tue, 28 May 2024 00:35:51 +0200 [thread overview]
Message-ID: <20240527223551.GA374567@pevik> (raw)
In-Reply-To: <20240527135718.29451-1-mdoucha@suse.cz>
Hi Martin,
> The tdp_mmu sysfile was made read-only in kernel v6.3. Do not modify
> it but only reload vendor KVM modules if needed. Some kernel versions
> before v6.3 have writable tdp_mmu sysfile which appears to be
> independent from vendor KVM module settings. Print a warning about
> false negatives if tdp_mmu appears enabled after reloading KVM
> modules. It is unclear if that state may impact bug reproducibility.
Good catch.
...
> static void disable_tdp(void)
> {
> - if (!access(TDP_MMU_SYSFILE, F_OK)) {
> - /* FIXME: Is setting tdp_mmu=0 sufficient to disable TDP? */
> - return;
> - }
> -
> if (read_bool_sys_param(TDP_AMD_SYSFILE) > 0)
> reload_module("kvm_amd", "npt=0");
> if (read_bool_sys_param(TDP_INTEL_SYSFILE) > 0)
> reload_module("kvm_intel", "ept=0");
> +
> + if (read_bool_sys_param(TDP_MMU_SYSFILE) > 0)
> + tst_res(TINFO, "tdp_mmu is enabled, beware of false negatives");
Wouldn't it be better to add "WARNING:" to make it more visible?
tst_res(TINFO, "WARNING: tdp_mmu is enabled, beware of false negatives");
(if you agree, I can change it before merge)
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-05-27 22:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 13:57 [LTP] [PATCH] kvm_pagefault01: Do not write into tdp_mmu sysfile Martin Doucha
2024-05-27 22:35 ` Petr Vorel [this message]
2024-05-28 8:33 ` Martin Doucha
2024-05-28 9:37 ` Petr Vorel
2024-05-28 9:42 ` Martin Doucha
2024-05-28 9:56 ` Jan Stancek
2024-05-28 12:25 ` Petr Vorel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240527223551.GA374567@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox