mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Borislav Petkov <bp@suse.de>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Andre Przywara <Andre.Przywara@arm.com>,
	"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v3] x86: move cacheinfo sysfs to generic cacheinfo infrastructure
Date: Tue, 10 Mar 2015 14:35:12 +0000	[thread overview]
Message-ID: <54FF0120.1070205@arm.com> (raw)
In-Reply-To: <20150310142627.GF3535@pd.tnic>



On 10/03/15 14:26, Borislav Petkov wrote:
> On Tue, Mar 10, 2015 at 02:22:22PM +0000, Sudeep Holla wrote:
>> I was able to reproduce this and now I realise I had CONFIG_AMD_NB
>> disabled in my config earlier which hid this issue previously, sorry
>> for that.
>>
>> The below patch fixed the issue on my Intel i7 box. I can post this
>> separately if required.
>>
>> Regards,
>> Sudeep
>>
>>  From b081cbf26071f4c8ce51f270931387415ab1a06c Mon Sep 17 00:00:00 2001
>> From: Sudeep Holla <sudeep.holla@arm.com>
>> Date: Tue, 10 Mar 2015 13:49:58 +0000
>> Subject: [PATCH] x86: cacheinfo: fix cache_get_priv_group for Intel
>> processors
>>
>> The private pointer provided by the cacheinfo is used to implement
>> the AMD L3 cache specific attributes using the northbridge pointer
>> obtained through cpuid4 registers. However, it's populated even on
>> Intel processors for Level 3 cache. This results in failure of
>
> Do we need it populated on Intel?
>
> Because if not, we can leave it NULL there and do only
>
> 	if (this_leaf->level < 3 || !nb)
> 		return NULL;
>

Yes we can do that. I leave that too you guys. I don't know the exact
reason why cpuid4_cache_lookup_regs is populating
	struct amd_northbridge *nb in struct _cpuid4_info_reg

My initial assumption was that it will be NULL for Intel processors and
hence I assigned cacheinfo->priv to nb pointer unconditionally.
So I don't have any strong opinion here.

Regards,
Sudeep


  reply	other threads:[~2015-03-10 14:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  7:50 [PATCH RFT] " Sudeep Holla
2015-01-23 13:55 ` Thomas Gleixner
2015-01-23 18:15   ` Borislav Petkov
2015-02-23 16:36     ` Sudeep Holla
2015-02-23 18:14 ` [PATCH RFT v2] " Sudeep Holla
2015-02-24  7:58   ` Ingo Molnar
2015-02-24  9:30     ` Sudeep Holla
2015-02-24 17:57   ` Borislav Petkov
2015-02-24 18:09     ` Sudeep Holla
2015-02-24 18:58       ` Borislav Petkov
2015-03-01 22:39     ` Andre Przywara
2015-03-02 10:17       ` Sudeep Holla
2015-03-03 18:45       ` Borislav Petkov
2015-03-03 18:53         ` Tejun Heo
2015-03-03 18:57           ` Borislav Petkov
2015-03-04 11:15             ` Sudeep Holla
2015-03-04 11:27               ` Borislav Petkov
2015-03-04 11:35                 ` Sudeep Holla
2015-03-04  9:52         ` Sudeep Holla
2015-03-04 12:00   ` [PATCH v3] " Sudeep Holla
2015-03-04 12:27     ` Borislav Petkov
2015-03-05  8:16       ` Borislav Petkov
2015-03-05  9:28         ` Sudeep Holla
2015-03-10 11:37           ` Borislav Petkov
2015-03-10 11:53             ` Sudeep Holla
2015-03-10 14:22               ` Sudeep Holla
2015-03-10 14:26                 ` Borislav Petkov
2015-03-10 14:35                   ` Sudeep Holla [this message]
2015-03-11 13:36                     ` Borislav Petkov
2015-03-11 15:44                       ` Sudeep Holla
2015-03-11 20:23                         ` Borislav Petkov
2015-03-09 14:46     ` [tip:x86/cpu] x86/cacheinfo: Move cacheinfo sysfs code to generic infrastructure tip-bot for Sudeep Holla

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=54FF0120.1070205@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=Andre.Przywara@arm.com \
    --cc=bp@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome