From: Xin Li <xin@zytor.com>
To: Nikolay Borisov <nik.borisov@suse.com>, linux-kernel@vger.kernel.org
Cc: hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
peterz@infradead.org, andrew.cooper3@citrix.com,
houwenlong.hwl@antgroup.com
Subject: Re: [PATCH v1 1/4] x86/fred: Parse cmdline param "fred=" in cpu_parse_early_param()
Date: Sun, 7 Jul 2024 10:42:16 -0700 [thread overview]
Message-ID: <0f8a5e47-58e8-4adb-a796-f31f8d35f487@zytor.com> (raw)
In-Reply-To: <48e5f704-c683-43ca-bb5e-0fb691eab4d5@suse.com>
On 7/4/2024 4:20 AM, Nikolay Borisov wrote:
>
>
> On 3.07.24 г. 11:54 ч., Xin Li (Intel) wrote:
>> Depending on whether FRED will be used, sysvec_install() installs
>> a system interrupt handler into FRED system vector dispatch table
>> or IDT. However FRED can be disabled later in trap_init(), after
>> sysvec_install() is called. E.g., the HYPERVISOR_CALLBACK_VECTOR
>> handler is registered with sysvec_install() in kvm_guest_init(),
>> which is called in setup_arch() but way before trap_init(). IOW,
>> there is a gap between FRED is available and available but disabled.
>> As a result, when FRED is available but disabled, its IDT handler
>> is not installed thus spurious_interrupt() will be invoked.
>>
>> Fix it by parsing cmdline param "fred=" in cpu_parse_early_param()
>> to minimize the gap between FRED is available and available but
>> disabled.
>>
>> Fixes: 3810da12710a ("x86/fred: Add a fred= cmdline param")
>> Reported-by: Hou Wenlong <houwenlong.hwl@antgroup.com>
>> Suggested-by: Thomas Gleixner <tglx@linutronix.de>
>> Signed-off-by: Xin Li (Intel) <xin@zytor.com>
>> ---
>> arch/x86/kernel/cpu/common.c | 5 +++++
>> arch/x86/kernel/traps.c | 26 --------------------------
>> 2 files changed, 5 insertions(+), 26 deletions(-)
>>
>> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
>> index d4e539d4e158..9a904fe7c829 100644
>> --- a/arch/x86/kernel/cpu/common.c
>> +++ b/arch/x86/kernel/cpu/common.c
>> @@ -1510,6 +1510,11 @@ static void __init cpu_parse_early_param(void)
>> if (cmdline_find_option_bool(boot_command_line, "nousershstk"))
>> setup_clear_cpu_cap(X86_FEATURE_USER_SHSTK);
>> + /* Minimize the gap between FRED is available and available but
>> disabled. */
>> + arglen = cmdline_find_option(boot_command_line, "fred", arg,
>> sizeof(arg));
>> + if (arglen != strlen("on") || strcmp(arg, "on"))
>
>
> Just make this check :
>
> ret = cmdline_find_option(...)
> if (ret < 0 || strcmp()))
>
> A lot more straightforward
>
I'd do
if (arglen != 2 || strncmp(arg, "on", 2))
If arglen is 2, strncmp(arg, "on", 2) is essentially strcmp(arg, "on"),
but I should've kept using strncmp.
next prev parent reply other threads:[~2024-07-07 17:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 8:54 [PATCH v1 0/4] Enable FRED earlier Xin Li (Intel)
2024-07-03 8:54 ` [PATCH v1 1/4] x86/fred: Parse cmdline param "fred=" in cpu_parse_early_param() Xin Li (Intel)
2024-07-04 11:20 ` Nikolay Borisov
2024-07-07 17:42 ` Xin Li [this message]
2024-07-03 8:54 ` [PATCH v1 2/4] x86/fred: Write to FRED MSRs with wrmsrns() Xin Li (Intel)
2024-07-03 15:43 ` Dave Hansen
2024-07-03 15:54 ` Borislav Petkov
2024-07-03 16:00 ` Andrew Cooper
2024-07-03 16:06 ` H. Peter Anvin
2024-07-03 16:17 ` Borislav Petkov
2024-07-05 2:45 ` H. Peter Anvin
2024-07-05 9:44 ` Borislav Petkov
2024-07-05 10:30 ` Andrew Cooper
2024-07-05 13:45 ` Borislav Petkov
2024-07-09 13:58 ` Xin Li
2024-07-09 20:51 ` H. Peter Anvin
2024-07-03 16:18 ` Andrew Cooper
2024-07-04 5:57 ` Xin Li
2024-07-04 7:58 ` H. Peter Anvin
2024-07-04 8:23 ` Borislav Petkov
2024-07-04 8:28 ` H. Peter Anvin
2024-07-03 16:43 ` Dave Hansen
2024-07-03 22:48 ` Xin Li
2024-07-05 9:28 ` Peter Zijlstra
2024-07-05 11:33 ` H. Peter Anvin
2024-07-03 8:54 ` [PATCH v1 3/4] x86/fred: Split FRED RSP initialization into a separate function Xin Li (Intel)
2024-07-03 8:54 ` [PATCH v1 4/4] x86/fred: Enable FRED right after init_mem_mapping() Xin Li (Intel)
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=0f8a5e47-58e8-4adb-a796-f31f8d35f487@zytor.com \
--to=xin@zytor.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=houwenlong.hwl@antgroup.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®