linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: get rid of a few StrongARM cache-related build time constants
Date: Thu, 7 Jul 2011 21:53:04 +0100	[thread overview]
Message-ID: <20110707205304.GF20403@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1107071438200.14596@xanadu.home>

On Thu, Jul 07, 2011 at 02:43:15PM -0400, Nicolas Pitre wrote:
> On Thu, 7 Jul 2011, Russell King - ARM Linux wrote:
> 
> > On Wed, Jul 06, 2011 at 09:21:33AM -0400, Nicolas Pitre wrote:
> > > Could you test this patch as well?  You're the only one I know who might 
> > > still have access to the affected hardware.
> > 
> > Tested on Assabet, and unfortunately, this doesn't work on its own because
> > we don't permit iotable_init() to create pages with MT_CACHECLEAN and
> > MT_MINICLEAN.
> > 
> > <4>BUG: map for 0xe0000000 at 0xfffe0000 can not be mapped using pages, ignoring.
> > <4>BUG: map for 0xe0004000 at 0xfffe4000 can not be mapped using pages, ignoring.
> > <4>BUG: map for 0xe0008000 at 0xfffe8000 can not be mapped using pages, ignoring.
> > <4>BUG: map for 0xe000c000 at 0xfffec000 can not be mapped using pages, ignoring.
> > 
> > The fix is below (probably with offsets):
> 
> Great. Are you providing an ACK or tested-by with this patch folded in?
> 
> > @@ -506,16 +488,8 @@ static void __init build_mem_type_table(void)
> >  	mem_types[MT_MEMORY].prot_pte |= kern_pgprot;
> >  	mem_types[MT_MEMORY_NONCACHED].prot_sect |= ecc_mask;
> >  	mem_types[MT_ROM].prot_sect |= cp->pmd;
> > +	mem_types[MT_CACHECLEAN].prot_pte |= kern_pgprot;
> >  
> Doesn't MT_MINICLEAN require kern_pgprot as well?

Only if you think the result of orring:

#define L_PTE_MT_WRITEBACK      (_AT(pteval_t, 0x03) << 2)      /* 0011 */
#define L_PTE_MT_MINICACHE      (_AT(pteval_t, 0x06) << 2)      /* 0110 (sa1100, xscale) */

together would make sense... it'd make it:

#define L_PTE_MT_WRITEALLOC     (_AT(pteval_t, 0x07) << 2)      /* 0111 */

though, so I don't think so.

  reply	other threads:[~2011-07-07 20:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06  2:33 [PATCH] ARM: get rid of a few StrongARM cache-related build time constants Nicolas Pitre
2011-07-06  7:55 ` Russell King - ARM Linux
2011-07-06 13:21   ` Nicolas Pitre
2011-07-06 13:41     ` Russell King - ARM Linux
2011-07-06 13:51       ` Nicolas Pitre
2011-07-06 14:24       ` Dmitry Eremin-Solenikov
2011-07-07 17:06     ` Russell King - ARM Linux
2011-07-07 18:43       ` Nicolas Pitre
2011-07-07 20:53         ` Russell King - ARM Linux [this message]
2011-07-07 23:28           ` Nicolas Pitre
2011-07-11 14:38       ` Nicolas Pitre
2011-07-11 21:10         ` Russell King - ARM Linux
2011-07-19 10:53           ` Russell King - ARM Linux

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=20110707205304.GF20403@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).