From: Paul Burton <paul.burton@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Manuel Lauss <manuel.lauss@gmail.com>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: 4.1: XPA breaks Alchemy
Date: Thu, 7 Apr 2016 07:50:38 +0100 [thread overview]
Message-ID: <20160407065038.GC20863@NP-P-BURTON> (raw)
In-Reply-To: <20160407055813.GD26267@linux-mips.org>
On Thu, Apr 07, 2016 at 07:58:13AM +0200, Ralf Baechle wrote:
> On Thu, Apr 07, 2016 at 01:06:58AM +0100, Paul Burton wrote:
>
> >
> > I don't suppose you'd be able to try this kernel branch?
> >
> > https://git.linux-mips.org/cgit/paul/linux.git/log/?h=v4.6-tlb
> >
> > git://git.linux-mips.org/pub/scm/paul/linux.git -b v4.6-tlb
> >
> > I'm working on fixing up a number of issues with commit c5b367835cfc
> > ("MIPS: Add support for XPA.") but unfortunately don't have access to
> > any Alchemy systems to test it myself.
>
> The unique architecural feature of Alchemy is that it has devices such as
> the PCI bus outside the low 4GB of physical address space. So I'd
> suspect something is wrong there.
>
> Everybody is running Sibyte 64 bit; I wonder if highmem with Sibyte is
> also affected.
>
> Ralf
Hi Ralf,
The problem is anywhere that formerly used 64 bit physical addresses
(CONFIG_PHYS_ADDR_T_64BIT) with a MIPS32 CPU (CONFIG_CPU_MIPS32), since
the XPA support essentially clobbered all that code with the XPA
implementation rather than treating them as the distinct cases that they
are. My fix is over here, and I'll submit it for merging in the v4.7
cycle (I guess I could submit now as it's a fix, but it's built atop
some rework of pgtable-bits.h to make it more readable so would need
that to go in too):
https://git.linux-mips.org/cgit/paul/linux.git/commit/?h=v4.6-tlb&id=3a74e3b7bcb1b392da2400ff27ee4e41989dd54f
Thanks,
Paul
next prev parent reply other threads:[~2016-04-07 6:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 17:34 4.1: XPA breaks Alchemy Manuel Lauss
2015-07-14 6:28 ` Manuel Lauss
2015-11-03 13:12 ` Steven J. Hill
2016-02-10 0:21 ` Paul Burton
2016-04-07 0:06 ` Paul Burton
2016-04-07 5:58 ` Ralf Baechle
2016-04-07 6:50 ` Paul Burton [this message]
2016-04-07 13:43 ` Maciej W. Rozycki
2016-04-07 6:40 ` Manuel Lauss
2016-04-07 6:46 ` Paul Burton
2016-04-07 6:47 ` Manuel Lauss
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=20160407065038.GC20863@NP-P-BURTON \
--to=paul.burton@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=ralf@linux-mips.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