linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Borislav Petkov <bp@suse.de>,
	Andre Przywara <Andre.Przywara@arm.com>,
	Tejun Heo <tj@kernel.org>
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>,
	"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH RFT v2] x86: move cacheinfo sysfs to generic cacheinfo infrastructure
Date: Wed, 04 Mar 2015 09:52:58 +0000	[thread overview]
Message-ID: <54F6D5FA.6000307@arm.com> (raw)
In-Reply-To: <20150303184527.GE3648@pd.tnic>



On 03/03/15 18:45, Borislav Petkov wrote:
[...]

> Now, previously the code did
>
> -			if (!per_cpu(ici_cpuid4_info, i))
> -				continue;
>
>
> and __cache_cpumap_setup() already does:
>
>                          if (i == cpu || !sib_cpu_ci->info_list)
>                                  continue;/* skip if itself or no cacheinfo */
>
> so maybe we should do that too in __cache_amd_cpumap_setup():
>
>                          if (!this_cpu_ci->info_list)
>                                  continue;
>
> for the index == 3 case?
>
> It boots fine here with that change and it is consistent with the
> previous code.
>

Ok, I will add the above check. Sorry for missing that.

> And yes, the x86 cacheinfo code could use a serious rubbing and cleanup.
>
> Btw, this patch introduces a bunch of new sysfs nodes in the caches
> hierarchy:
>
> --- caches-guest-before.txt     2015-03-03 15:11:09.168276423 +0100
> +++ caches-guest-after.txt      2015-03-03 18:19:04.084426130 +0100
> @@ -1,6 +1,22 @@
> +/sys/devices/system/cpu/cpu0/cache/power/control:1:auto
> +/sys/devices/system/cpu/cpu0/cache/power/async:1:disabled
> +/sys/devices/system/cpu/cpu0/cache/power/runtime_enabled:1:disabled
> +/sys/devices/system/cpu/cpu0/cache/power/runtime_active_kids:1:0
> +/sys/devices/system/cpu/cpu0/cache/power/runtime_active_time:1:0
> +/sys/devices/system/cpu/cpu0/cache/power/runtime_status:1:unsupported
> +/sys/devices/system/cpu/cpu0/cache/power/runtime_usage:1:0
> +/sys/devices/system/cpu/cpu0/cache/power/runtime_suspended_time:1:0
>   /sys/devices/system/cpu/cpu0/cache/index0/size:1:64K
>   /sys/devices/system/cpu/cpu0/cache/index0/type:1:Data
>   /sys/devices/system/cpu/cpu0/cache/index0/level:1:1
> +/sys/devices/system/cpu/cpu0/cache/index0/power/control:1:auto
> +/sys/devices/system/cpu/cpu0/cache/index0/power/async:1:disabled
> +/sys/devices/system/cpu/cpu0/cache/index0/power/runtime_enabled:1:disabled
> +/sys/devices/system/cpu/cpu0/cache/index0/power/runtime_active_kids:1:0
> +/sys/devices/system/cpu/cpu0/cache/index0/power/runtime_active_time:1:0
> +/sys/devices/system/cpu/cpu0/cache/index0/power/runtime_status:1:unsupported
> +/sys/devices/system/cpu/cpu0/cache/index0/power/runtime_usage:1:0
> +/sys/devices/system/cpu/cpu0/cache/index0/power/runtime_suspended_time:1:0
>   /sys/devices/system/cpu/cpu0/cache/index0/number_of_sets:1:512
>   /sys/devices/system/cpu/cpu0/cache/index0/shared_cpu_map:1:1
>   /sys/devices/system/cpu/cpu0/cache/index0/shared_cpu_list:1:0
>   ...
>
> What do those things mean? runtime_active_kids ?? Kids are active during
> runtime?! Well, that's a given, no need for a sysfs node for that :-)
>

Those extra sysfs are due to that fact that generic cacheinfo sysfs
is not using raw kobjects directly anymore (which was the case with most
of the old cacheinfo sysfs implementation), but uses device/device
attributes as Greg suggested to simply the code and reuse device model
code.

Regards,
Sudeep


  parent reply	other threads:[~2015-03-04  9:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  7:50 [PATCH RFT] x86: move cacheinfo sysfs to generic cacheinfo infrastructure 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 [this message]
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
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=54F6D5FA.6000307@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=tj@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).