From: Sudeep Holla <Sudeep.Holla@arm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Sudeep.Holla@arm.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
"linux390@de.ibm.com" <linux390@de.ibm.com>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>
Subject: Re: [PATCH RFC/RFT v2 3/8] s390: move cacheinfo sysfs to generic cacheinfo infrastructure
Date: Mon, 17 Feb 2014 18:36:59 +0000 [thread overview]
Message-ID: <530256CB.6000603@arm.com> (raw)
In-Reply-To: <20140210113019.GC19013@osiris>
Hi Heiko,
On 10/02/14 11:30, Heiko Carstens wrote:
> On Fri, Feb 07, 2014 at 04:49:18PM +0000, Sudeep Holla wrote:
>> From: Sudeep Holla <sudeep.holla@arm.com>
>>
>> This patch removes the redundant sysfs cacheinfo code by making use of
>> the newly introduced generic cacheinfo infrastructure.
>>
>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>
> [...]
>
>> -static ssize_t shared_cpu_map_func(struct kobject *kobj, int type, char *buf)
>> -{
>> - struct cache_index_dir *index;
>> - int len;
>> + this_leaf->level = level + 1;
>> + this_leaf->type = type;
>> + this_leaf->coherency_line_size = ecag(EXTRACT_LINE_SIZE, level, ti);
>> + this_leaf->ways_of_associativity = ecag(EXTRACT_ASSOCIATIVITY,
>> + level, ti);
>> + this_leaf->size = ecag(EXTRACT_SIZE, level, ti);
>> + if (private)
>> + cpumask_set_cpu(cpu, &this_leaf->shared_cpu_map);
>> + else /* System wide */
>> + cpumask_copy(&this_leaf->shared_cpu_map, cpu_online_mask);
>
> FWIW, this also seems to be wrong: on s390 we only expose cpu private
> caches via sysfs. Shared caches are not exposed (and simply saying they are
> system wide would be wrong).
> Please have a look at these two commits which should describe why things
> are as they are on s390:
>
> 881730ad365130f64b5c70c40904b04eb3b79de3
> "s390/cache: expose cpu cache topology via sysfs"
> 6668022c7bde3fdc96d3d257294a7216c7a46829
> "s390/cache: add cpu cache information to /proc/cpuinfo"
>
>
I need your help to get few things clarified.
IIUC, I see that shared caches are not exposed via sysfs but there are exposed
through /proc/cpuinfo, right ? If yes, based on your above statement, shared
cpus are may not be system-wide, then how can /proc/cpuinfo show shared cache info.
Regards,
Sudeep
next prev parent reply other threads:[~2014-02-17 18:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 16:49 [PATCH RFC/RFT v2 0/8] drivers: cacheinfo support Sudeep Holla
2014-02-07 16:49 ` [PATCH RFC/RFT v2 1/8] drivers: base: support cpu cache information interface to userspace via sysfs Sudeep Holla
2014-02-07 19:29 ` Greg Kroah-Hartman
2014-02-10 18:09 ` Sudeep Holla
2014-02-11 0:13 ` Greg Kroah-Hartman
2014-02-13 15:55 ` Sudeep Holla
2014-02-17 18:26 ` Sudeep Holla
2014-02-18 21:53 ` Greg Kroah-Hartman
2014-02-19 16:04 ` Sudeep Holla
2014-02-07 16:49 ` [PATCH RFC/RFT v2 2/8] ia64: move cacheinfo sysfs to generic cacheinfo infrastructure Sudeep Holla
2014-02-07 16:49 ` Sudeep Holla
2014-02-07 16:49 ` [PATCH RFC/RFT v2 3/8] s390: " Sudeep Holla
2014-02-10 9:50 ` Heiko Carstens
2014-02-10 11:34 ` Sudeep Holla
2014-02-10 11:59 ` Heiko Carstens
2014-02-10 11:30 ` Heiko Carstens
2014-02-10 11:36 ` Sudeep Holla
2014-02-17 18:36 ` Sudeep Holla [this message]
2014-02-18 9:45 ` Heiko Carstens
2014-02-07 16:49 ` [PATCH RFC/RFT v2 4/8] x86: " Sudeep Holla
2014-02-07 16:49 ` [PATCH RFC/RFT v2 5/8] powerpc: " Sudeep Holla
2014-02-07 16:49 ` Sudeep Holla
2014-02-07 16:49 ` [PATCH RFC/RFT v2 6/8] ARM64: kernel: add support for cpu cache information Sudeep Holla
2014-02-07 16:49 ` Sudeep Holla
2014-02-07 16:49 ` [PATCH RFC/RFT v2 7/8] ARM: " Sudeep Holla
2014-02-07 16:49 ` Sudeep Holla
2014-02-07 16:49 ` [PATCH RFC/RFT v2 8/8] ARM: kernel: add outer cache support for cacheinfo implementation Sudeep Holla
2014-02-07 16:49 ` 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=530256CB.6000603@arm.com \
--to=sudeep.holla@arm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
/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.