From: Sohil Mehta <sohil.mehta@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Borislav Petkov <bp@kernel.org>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] x86/microcode: Add microcode loader debugging functionality
Date: Tue, 12 Aug 2025 11:57:50 -0700 [thread overview]
Message-ID: <17938a19-66a6-42e2-bab9-345cfa3cb818@intel.com> (raw)
In-Reply-To: <20250812102645.GBaJsW5cJLYc90Fhhg@fat_crate.local>
On 8/12/2025 3:26 AM, Borislav Petkov wrote:
>> s/dbg/debug/
>> s/MICROCODE_DBG/MICROCODE_DEBUG
>> s/ucode_dbg/ucode_debug
>
> No, because I don't want to type unnecessarily and "dbg" is very clear as it
> is.
>
Yes, in this patch, dbg clearly means debug. But, are some contexts
where dbg is used with other things which might take an extra second to
process. For example,
if (!cpuid_feature() ||
((native_cpuid_ecx(1) & BIT(31)) && !dbg) ||
amd_check_current_patch_level())
dis_ucode_ldr = true;
In the tradeoff between writing and reading, I am more inclined to make
things easier to read. But obviously your preference supersedes mine :)
>
>> Should we also include a dependency on DEBUG_KERNEL?
>
> Because?
>
To ensure people only use it for debugging purposes similar to
X86_DEBUG_FPU or DEBUG_ENTRY.
next prev parent reply other threads:[~2025-08-12 18:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 9:42 [PATCH 0/2] x86/microcode: Add debugging glue Borislav Petkov
2025-08-09 9:42 ` [PATCH 1/2] x86/microcode: Add microcode= cmdline parsing Borislav Petkov
2025-08-12 2:26 ` Sohil Mehta
2025-08-12 10:23 ` Borislav Petkov
2025-08-12 19:14 ` Sohil Mehta
2025-08-12 21:28 ` Borislav Petkov
2025-08-14 23:08 ` Chang S. Bae
2025-08-15 9:20 ` Borislav Petkov
2025-08-15 19:50 ` Chang S. Bae
2025-08-18 16:30 ` Sohil Mehta
2025-08-09 9:42 ` [PATCH 2/2] x86/microcode: Add microcode loader debugging functionality Borislav Petkov
2025-08-12 3:04 ` Sohil Mehta
2025-08-12 10:26 ` Borislav Petkov
2025-08-12 18:57 ` Sohil Mehta [this message]
2025-08-12 19:09 ` Borislav Petkov
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=17938a19-66a6-42e2-bab9-345cfa3cb818@intel.com \
--to=sohil.mehta@intel.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).