public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Sohil Mehta <sohil.mehta@intel.com>
To: Suchit Karunakaran <suchitkarunakaran@gmail.com>
Cc: <skhan@linuxfoundation.org>,
	<linux-kernel-mentees@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
	<tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
	<dave.hansen@linux.intel.com>, <hpa@zytor.com>,
	<darwi@linutronix.de>, <peterz@infradead.org>,
	<ravi.bangoria@amd.com>
Subject: Re: [PATCH v4] x86/cpu/intel: Fix the constant_tsc model check for Pentium 4
Date: Mon, 4 Aug 2025 13:37:00 -0700	[thread overview]
Message-ID: <e72b9895-c143-4818-901b-7d8ab26b8e91@intel.com> (raw)
In-Reply-To: <20250804175901.13561-1-suchitkarunakaran@gmail.com>

Hi Suchit

I would strongly suggest spending more time understanding reviewer
feedback and incorporating it before sending another version. Most of
the comments below are a repeat from previous reviews by multiple folks.


On 8/4/2025 10:59 AM, Suchit Karunakaran wrote:
> Pentium 4's which are INTEL_P4_PRESCOTT (model 0x03) and later have
> a constant TSC. This was correctly captured until commit fadb6f569b10
> ("x86/cpu/intel: Limit the non-architectural constant_tsc model checks").
> In that commit, an error was introduced while selecting the last P4
> model (0x06) as the upper bound. Model 0x06 was transposed to
> INTEL_P4_WILLAMETTE, which is just plain wrong. That was presumably a
> simple typo, probably just copying and pasting the wrong P4 model.
> Fix the constant TSC logic to cover all later P4 models. End at
> INTEL_P4_CEDARMILL which accurately corresponds to the last P4 model.


Please use proper spacing and line breaks. Posting this as a single
chunk makes it very hard to read.

> Fixes: fadb6f569b10 ("x86/cpu/intel: Limit the non-architectural constant_tsc model checks")
> 
> Cc: <stable@vger.kernel.org> # v6.15
> 
> Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com>
> 

No blank lines between these 3 statements.

Please take all review comments seriously, even if they are nits.

https://lore.kernel.org/lkml/2025073013-stimulus-snowdrift-d28c@gregkh/

> Changes since v3:
> - Refined changelog
> 
> Changes since v2:
> - Improve commit message
> 
> Changes since v1:
> - Fix incorrect logic
> 

Patch-to-patch changes go below the --- line.

You have been provided the same feedback by other folks as well.

https://lore.kernel.org/lkml/61958a3cca40fc9a42b951c68c75f138cab9212e.camel@perches.com/

https://lore.kernel.org/lkml/2d30ee37-8069-4443-8a80-5233b3b23f66@intel.com/

If you are not sure, please look at other submissions to the mailing
list that do this.

> ---
>  arch/x86/kernel/cpu/intel.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
> index 076eaa41b8c8..6f5bd5dbc249 100644
> --- a/arch/x86/kernel/cpu/intel.c
> +++ b/arch/x86/kernel/cpu/intel.c
> @@ -262,7 +262,7 @@ static void early_init_intel(struct cpuinfo_x86 *c)
>  	if (c->x86_power & (1 << 8)) {
>  		set_cpu_cap(c, X86_FEATURE_CONSTANT_TSC);
>  		set_cpu_cap(c, X86_FEATURE_NONSTOP_TSC);
> -	} else if ((c->x86_vfm >= INTEL_P4_PRESCOTT && c->x86_vfm <= INTEL_P4_WILLAMETTE) ||
> +	} else if ((c->x86_vfm >=  INTEL_P4_PRESCOTT && c->x86_vfm <= INTEL_P4_CEDARMILL) ||
>  		   (c->x86_vfm >= INTEL_CORE_YONAH  && c->x86_vfm <= INTEL_IVYBRIDGE)) {

Again, this changes the previous alignment. You do not need the extra
space before INTEL_P4_PRESCOTT. Avoiding that would keep both the lines
aligned.

https://lore.kernel.org/lkml/30f01900-e79f-4947-b0b4-c4ba29d18084@intel.com/

It's acceptable to ask clarifying questions, but disregarding review
comments frustrates reviewers and inclined to ignore future submissions.


>  		set_cpu_cap(c, X86_FEATURE_CONSTANT_TSC);
>  	}


  reply	other threads:[~2025-08-04 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 17:59 [PATCH v4] x86/cpu/intel: Fix the constant_tsc model check for Pentium 4 Suchit Karunakaran
2025-08-04 20:37 ` Sohil Mehta [this message]
2025-08-05  4:28   ` Suchit Karunakaran

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=e72b9895-c143-4818-901b-7d8ab26b8e91@intel.com \
    --to=sohil.mehta@intel.com \
    --cc=bp@alien8.de \
    --cc=darwi@linutronix.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@amd.com \
    --cc=skhan@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=suchitkarunakaran@gmail.com \
    --cc=tglx@linutronix.de \
    /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