All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Qian Cai <cai@lca.pw>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/cacheinfo: fix a -Wtype-limits warning
Date: Wed, 5 Jun 2019 13:07:04 -0700	[thread overview]
Message-ID: <20190605200703.GD26328@linux.intel.com> (raw)
In-Reply-To: <1559763654-5155-1-git-send-email-cai@lca.pw>

On Wed, Jun 05, 2019 at 03:40:54PM -0400, Qian Cai wrote:
> cpuinfo_x86.x86_model is an unsigned type, so compares it against zero
> will generate a compilation warning,
> 
> arch/x86/kernel/cpu/cacheinfo.c: In function
> 'cacheinfo_amd_init_llc_id':
> arch/x86/kernel/cpu/cacheinfo.c:662:19: warning: comparison is always
> true due to limited range of data type [-Wtype-limits]
> 
> Signed-off-by: Qian Cai <cai@lca.pw>
> ---
>  arch/x86/kernel/cpu/cacheinfo.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/arch/x86/kernel/cpu/cacheinfo.c b/arch/x86/kernel/cpu/cacheinfo.c
> index 395d46f78582..c7503be92f35 100644
> --- a/arch/x86/kernel/cpu/cacheinfo.c
> +++ b/arch/x86/kernel/cpu/cacheinfo.c
> @@ -658,8 +658,7 @@ void cacheinfo_amd_init_llc_id(struct cpuinfo_x86 *c, int cpu, u8 node_id)
>  	if (c->x86 < 0x17) {
>  		/* LLC is at the node level. */
>  		per_cpu(cpu_llc_id, cpu) = node_id;
> -	} else if (c->x86 == 0x17 &&
> -		   c->x86_model >= 0 && c->x86_model <= 0x1F) {
> +	} else if (c->x86 == 0x17 && c->x86_model <= 0x1F) {

Might be worth calling out in the changelog that 'c->x86 == 0x17' is true
if and only if c->x86_model was explicitly set by cpu_detect(), i.e. the
patch is correct even if the original intent was a misguided attempt to
check that x86_model has been set.

Fixes: 68091ee7ac3c ("x86/CPU/AMD: Calculate last level cache ID from number of sharing threads")
Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>

>  		/*
>  		 * LLC is at the core complex level.
>  		 * Core complex ID is ApicId[3] for these processors.
> -- 
> 1.8.3.1
> 

  reply	other threads:[~2019-06-05 20:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 19:40 [PATCH] x86/cacheinfo: fix a -Wtype-limits warning Qian Cai
2019-06-05 20:07 ` Sean Christopherson [this message]
2019-06-19 17:01   ` Borislav Petkov
2019-06-19 17:12     ` Sean Christopherson
2019-06-19 17:18       ` 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=20190605200703.GD26328@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=bp@alien8.de \
    --cc=cai@lca.pw \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.