From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Sudeep Holla <Sudeep.Holla@arm.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Ashok Raj <ashok.raj@intel.com>, Rob Herring <robh@kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH RFC 2/3] ARM: kernel: add support for cpu cache information
Date: Thu, 9 Jan 2014 20:08:01 +0000 [thread overview]
Message-ID: <20140109200801.GF27432@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <52CEF9E7.4070706@arm.com>
On Thu, Jan 09, 2014 at 07:35:03PM +0000, Sudeep Holla wrote:
> I assume you referring to some particular CPUs which don't implement this.
> I could not find it as optional or IMPLEMENTATION defined in ARM ARM.
> I might be missing to find it or there may be exceptions.
> Can you please provide more information on that ?
This is where _not_ relying on the most up to date ARM architecture
reference manual, but instead referring back to the ARM architecture
manual revision appropriate to the architecture is a far better plan.
For example, DDI0100E, Part B, 2.3.2:
| 2.3.2 Cache Type register
| If present, the Cache Type register supplies the following details about
| the cache:
Note the "if present" - it's a fact that not all ARMv4 CPUs support this
register. 2.3 also tells you how to detect when these registers are
implemented:
| ID registers other than the main ID register are defined so that when
| implemented, their value cannot be equal to that of the main ID register.
| Software can therefore determine whether they exist by reading both
| the main ID register and the desired register and comparing their values.
| If the two values are not equal, the desired register exists.
I can go back further to one of the initial revisions of the ARM ARM,
but that's a paper copy.
I can also refer you to DDI0087E (ARM720T) section 4.3 - this is an
ARMv4T CPU, and it has no cache type register. StrongARM is another
example where the CTR is not implemented.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 2/3] ARM: kernel: add support for cpu cache information
Date: Thu, 9 Jan 2014 20:08:01 +0000 [thread overview]
Message-ID: <20140109200801.GF27432@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <52CEF9E7.4070706@arm.com>
On Thu, Jan 09, 2014 at 07:35:03PM +0000, Sudeep Holla wrote:
> I assume you referring to some particular CPUs which don't implement this.
> I could not find it as optional or IMPLEMENTATION defined in ARM ARM.
> I might be missing to find it or there may be exceptions.
> Can you please provide more information on that ?
This is where _not_ relying on the most up to date ARM architecture
reference manual, but instead referring back to the ARM architecture
manual revision appropriate to the architecture is a far better plan.
For example, DDI0100E, Part B, 2.3.2:
| 2.3.2 Cache Type register
| If present, the Cache Type register supplies the following details about
| the cache:
Note the "if present" - it's a fact that not all ARMv4 CPUs support this
register. 2.3 also tells you how to detect when these registers are
implemented:
| ID registers other than the main ID register are defined so that when
| implemented, their value cannot be equal to that of the main ID register.
| Software can therefore determine whether they exist by reading both
| the main ID register and the desired register and comparing their values.
| If the two values are not equal, the desired register exists.
I can go back further to one of the initial revisions of the ARM ARM,
but that's a paper copy.
I can also refer you to DDI0087E (ARM720T) section 4.3 - this is an
ARMv4T CPU, and it has no cache type register. StrongARM is another
example where the CTR is not implemented.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Sudeep Holla <Sudeep.Holla@arm.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh@kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH RFC 2/3] ARM: kernel: add support for cpu cache information
Date: Thu, 9 Jan 2014 20:08:01 +0000 [thread overview]
Message-ID: <20140109200801.GF27432@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <52CEF9E7.4070706@arm.com>
On Thu, Jan 09, 2014 at 07:35:03PM +0000, Sudeep Holla wrote:
> I assume you referring to some particular CPUs which don't implement this.
> I could not find it as optional or IMPLEMENTATION defined in ARM ARM.
> I might be missing to find it or there may be exceptions.
> Can you please provide more information on that ?
This is where _not_ relying on the most up to date ARM architecture
reference manual, but instead referring back to the ARM architecture
manual revision appropriate to the architecture is a far better plan.
For example, DDI0100E, Part B, 2.3.2:
| 2.3.2 Cache Type register
| If present, the Cache Type register supplies the following details about
| the cache:
Note the "if present" - it's a fact that not all ARMv4 CPUs support this
register. 2.3 also tells you how to detect when these registers are
implemented:
| ID registers other than the main ID register are defined so that when
| implemented, their value cannot be equal to that of the main ID register.
| Software can therefore determine whether they exist by reading both
| the main ID register and the desired register and comparing their values.
| If the two values are not equal, the desired register exists.
I can go back further to one of the initial revisions of the ARM ARM,
but that's a paper copy.
I can also refer you to DDI0087E (ARM720T) section 4.3 - this is an
ARMv4T CPU, and it has no cache type register. StrongARM is another
example where the CTR is not implemented.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-09 20:08 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 19:26 [PATCH RFC 0/3] drivers: cacheinfo support Sudeep Holla
2014-01-08 19:26 ` Sudeep Holla
2014-01-08 19:26 ` Sudeep Holla
2014-01-08 19:26 ` [PATCH RFC 1/3] drivers: base: support cpu cache information interface to userspace via sysfs Sudeep Holla
2014-01-08 19:26 ` Sudeep Holla
2014-01-08 20:26 ` Greg Kroah-Hartman
2014-01-08 20:26 ` Greg Kroah-Hartman
2014-01-08 20:26 ` Greg Kroah-Hartman
2014-01-08 20:26 ` Greg Kroah-Hartman
2014-01-09 19:07 ` Sudeep Holla
2014-01-09 19:07 ` Sudeep Holla
2014-01-09 19:07 ` Sudeep Holla
2014-01-09 19:07 ` Sudeep Holla
2014-01-08 20:27 ` Greg Kroah-Hartman
2014-01-08 20:27 ` Greg Kroah-Hartman
2014-01-08 20:27 ` Greg Kroah-Hartman
2014-01-09 19:19 ` Sudeep Holla
2014-01-09 19:19 ` Sudeep Holla
2014-01-09 19:19 ` Sudeep Holla
2014-01-09 19:19 ` Sudeep Holla
2014-01-09 19:31 ` Greg Kroah-Hartman
2014-01-09 19:31 ` Greg Kroah-Hartman
2014-01-09 19:31 ` Greg Kroah-Hartman
2014-01-09 19:31 ` Greg Kroah-Hartman
2014-01-09 19:47 ` Sudeep Holla
2014-01-09 19:47 ` Sudeep Holla
2014-01-09 19:47 ` Sudeep Holla
2014-01-09 19:47 ` Sudeep Holla
2014-01-09 20:03 ` Greg Kroah-Hartman
2014-01-09 20:03 ` Greg Kroah-Hartman
2014-01-09 20:03 ` Greg Kroah-Hartman
2014-01-09 20:03 ` Greg Kroah-Hartman
2014-01-08 20:28 ` Greg Kroah-Hartman
2014-01-08 20:28 ` Greg Kroah-Hartman
2014-01-08 20:28 ` Greg Kroah-Hartman
2014-01-08 20:28 ` Greg Kroah-Hartman
2014-01-09 19:07 ` Sudeep Holla
2014-01-09 19:07 ` Sudeep Holla
2014-01-09 19:07 ` Sudeep Holla
2014-01-09 19:07 ` Sudeep Holla
2014-01-08 19:26 ` [PATCH RFC 2/3] ARM: kernel: add support for cpu cache information Sudeep Holla
2014-01-08 19:26 ` Sudeep Holla
2014-01-08 19:26 ` Sudeep Holla
2014-01-08 20:57 ` Russell King - ARM Linux
2014-01-08 20:57 ` Russell King - ARM Linux
2014-01-08 20:57 ` Russell King - ARM Linux
2014-01-08 20:57 ` Russell King - ARM Linux
2014-01-09 19:35 ` Sudeep Holla
2014-01-09 19:35 ` Sudeep Holla
2014-01-09 19:35 ` Sudeep Holla
2014-01-09 19:35 ` Sudeep Holla
2014-01-09 20:08 ` Russell King - ARM Linux [this message]
2014-01-09 20:08 ` Russell King - ARM Linux
2014-01-09 20:08 ` Russell King - ARM Linux
2014-01-08 19:26 ` [PATCH RFC 3/3] ARM: kernel: add outer cache support for cacheinfo implementation Sudeep Holla
2014-01-08 19:26 ` 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=20140109200801.GF27432@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Sudeep.Holla@arm.com \
--cc=ashok.raj@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh@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 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.