public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Valentin R Sitsikov <valentin.sitdikov@siemens.com>
To: linux-sh@vger.kernel.org
Subject: sh7785 cache question
Date: Thu, 06 Aug 2009 09:03:47 +0000	[thread overview]
Message-ID: <4A7A9C73.1070000@siemens.com> (raw)

Hello All!

Sh-7785 hw manual section 5 (Caches), chapter 5.3 (Operation of 
Instructions for Operand Cache Manipulation.) says:
OCBI
OCBWB
OCBP

Formerly, this instruction was treated as an NOP if Rn indicated an 
address in a non-cacheable
area. In the case of the LSI with the SH-4A extended functions, the 
operand cache line indicated
by way = Rn[14:13] and entry = Rn[12:5] is affected.
This operation is only valid in privileged mode, and the instruction 
generates an
address error exception in user mode. In addition, TLB-related 
exceptions do not occur.
Do not execute this instruction with Rn[31:24] containing a value other 
than H'F4, i.e. a value that
indicates the memory-mapped array area, control register area, or a 
reserved area (H'F0 to H'F3,
H'F5 to H'FF).

So my question is why still all cache related code for the sh-7785 in 
these instructions have effective address
as operand instead of 0xF4XXXXXX ?

Also It is interesting if there any plans for remove associative write 
operation to memory mapped OC address array?
The manual says:
5.4       Memory-Mapped Associative Write Operation
Associative writing to the IC and OC address arrays may not be supported 
in future SuperH-
family products. The use of instructions ICBI, OCBI, OCBP, and OCBWB is 
recommended.
These instructions handle ITLB misses, and notify instruction TLB miss 
exceptions and data TLB
miss exceptions, thus providing a sure way of controlling the IC and OC. 
As a transitional
measure, the SH-4A generates address errors when this function is used. 
If compatibility with
previous products is a crucial consideration, on the other hand, the 
MMCAW bit in EXPMASK
(H'FF2F 0004) can be set to 1 to enable this function. However, 
instructions ICBI, OCBI, OCBP,
and OCBWB should be used to guarantee compatibility with future 
SuperH-family products.


Thanks in advance.


             reply	other threads:[~2009-08-06  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06  9:03 Valentin R Sitsikov [this message]
2009-08-13  3:17 ` sh7785 cache question Paul Mundt
2009-08-31  7:56 ` Valentin R Sitsikov
2009-09-01  2:19 ` yoshii.takashi
2009-09-01  3:05 ` Paul Mundt

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=4A7A9C73.1070000@siemens.com \
    --to=valentin.sitdikov@siemens.com \
    --cc=linux-sh@vger.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