linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Nick Piggin <npiggin@suse.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Hugh Dickins <hugh@veritas.com>,
	Jared Hulbert <jaredeh@gmail.com>,
	Carsten Otte <cotte@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-arch@vger.kernel.org
Subject: Re: [rfc][patch 2/2] mm: introduce optional pte_special pte bit
Date: Wed, 16 Jan 2008 18:18:49 +0000	[thread overview]
Message-ID: <20080116181849.GA23371@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1200480750.19045.33.camel@pc1117.cambridge.arm.com>

On Wed, Jan 16, 2008 at 10:52:29AM +0000, Catalin Marinas wrote:
> If Xscale3 supports TEX remapping (it's an ARMv6, so it should but I'm
> not sure)

For the elimination of doubt, Xscale 3 is ARMv5 with cherry picked ARMv6
features - eg, it's VIVT, no ASID.  I don't believe it has any remapping
ability... but as I've said - when I get around to resolving this shared
mmap issue I'll know more about the way forward.

At the moment, the hold up is this EABI crap - the filesystem I have for
the Xscale 3 platform is EABI only so I can't run any of my existing test
programs, and I don't have a toolchain capable of generating executables
for EABI userspace - and I don't think I can sensibly put the OABI
libraries on the platform either.

So my first problem to resolve is how to run my test programs which show
up the issue on this hardware.

The second problem which is proving difficult is to find out why one of
the patches which enabled proper use of the set_pte_ext() function on
Xscale 3 CPUs resulted in Lennert's IOP board falling over - I've not
heard anything further from Lennert on that issue yet, despite prodding.
So, I might just throw it into the next merge window _anyway_ and then
we'll get more people testing it and hopefully get to the bottom of the
window.  The other alternative is to just let the patch sit around for
ever and nothing will happen - which clearly isn't productive.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2008-01-16 18:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13  3:08 [rfc] changes to user memory mapping scheme Nick Piggin
2008-01-13  3:09 ` [rfc][patch 1/2] mm: introduce VM_MIXEDMAP Nick Piggin
2008-01-13  3:10 ` [rfc][patch 2/2] mm: introduce optional pte_special pte bit Nick Piggin
2008-01-13  3:41   ` Linus Torvalds
2008-01-13  4:39     ` Nick Piggin
2008-01-13  4:45       ` Linus Torvalds
2008-01-13  5:06         ` Nick Piggin
2008-01-13 16:50           ` Linus Torvalds
2008-01-13 20:46             ` Martin Schwidefsky
2008-01-14 21:04             ` Jared Hulbert
2008-01-15  9:18               ` Carsten Otte
2008-01-16  3:38             ` Nick Piggin
2008-01-16  4:04               ` Linus Torvalds
2008-01-16  4:37                 ` Nick Piggin
2008-01-16  4:48                   ` Linus Torvalds
2008-01-16  4:51                     ` David Miller
2008-01-16  5:23                       ` Linus Torvalds
2008-01-16  5:48                         ` Nick Piggin
2008-01-16  9:52                           ` Martin Schwidefsky
2008-01-16  5:17                     ` Nick Piggin
2008-01-16 10:52                       ` Catalin Marinas
2008-01-16 18:18                         ` Russell King [this message]
2008-01-16 17:21                       ` Linus Torvalds
2008-01-16 17:14   ` David Howells

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=20080116181849.GA23371@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=catalin.marinas@arm.com \
    --cc=cotte@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hugh@veritas.com \
    --cc=jaredeh@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=schwidefsky@de.ibm.com \
    --cc=torvalds@linux-foundation.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).