Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: James Hogan <james.hogan@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Burton <paul.burton@imgtec.com>, <linux-mips@linux-mips.org>
Subject: Re: [PATCH 0/2] MIPS: Memory setup tweaks
Date: Tue, 16 Aug 2016 16:39:52 +0100	[thread overview]
Message-ID: <20160816153952.GZ19514@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <20160816153606.GF3894@linux-mips.org>

[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]

On Tue, Aug 16, 2016 at 05:36:07PM +0200, Ralf Baechle wrote:
> On Tue, Aug 09, 2016 at 01:21:47PM +0100, James Hogan wrote:
> 
> > Here are a couple of tweaks for MIPS memory setup, primarily in order to
> > handle memory which extends right up to the end of physical memory on
> > 32-bit systems with 32-bit phys_addr_t. More specifically we omit the
> > final page of physical memory to avoid the overflow (see patch 1 for
> > details).
> > 
> > Patch 2 improves the rounding in the MAAR setup, so as to include the
> > first full page of an already aligned region, and to avoid a BUG_ON for
> > regions with non 64-KByte aligned end addresses (which I happened to hit
> > while working on a different version of patch 1 which wasn't correctly
> > merging the kernel data section into the main RAM region).
> 
> There's a DMA issue with one of the system controllers on Malta which
> afair only affects one endianess and can be worked around by not using
> the last bit of memory. That isn't the only platform having such issues
> I've seen and debugging has always been very painful so I'm wondering
> if as a general precaution we should just leave the last page of memory
> unused.

If I understand you right, I think thats pretty much what patch 1 does,
or rather it allows such a region to be created but reduces the length
so it doesn't quite reach the end, I suppose assuming it will get
rounded down to a page boundary.

Cheers
James

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Burton <paul.burton@imgtec.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH 0/2] MIPS: Memory setup tweaks
Date: Tue, 16 Aug 2016 16:39:52 +0100	[thread overview]
Message-ID: <20160816153952.GZ19514@jhogan-linux.le.imgtec.org> (raw)
Message-ID: <20160816153952.od656hBXXAGBxAN2eiA0ovSnkET5zpVWer0ehVx_rpk@z> (raw)
In-Reply-To: <20160816153606.GF3894@linux-mips.org>

[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]

On Tue, Aug 16, 2016 at 05:36:07PM +0200, Ralf Baechle wrote:
> On Tue, Aug 09, 2016 at 01:21:47PM +0100, James Hogan wrote:
> 
> > Here are a couple of tweaks for MIPS memory setup, primarily in order to
> > handle memory which extends right up to the end of physical memory on
> > 32-bit systems with 32-bit phys_addr_t. More specifically we omit the
> > final page of physical memory to avoid the overflow (see patch 1 for
> > details).
> > 
> > Patch 2 improves the rounding in the MAAR setup, so as to include the
> > first full page of an already aligned region, and to avoid a BUG_ON for
> > regions with non 64-KByte aligned end addresses (which I happened to hit
> > while working on a different version of patch 1 which wasn't correctly
> > merging the kernel data section into the main RAM region).
> 
> There's a DMA issue with one of the system controllers on Malta which
> afair only affects one endianess and can be worked around by not using
> the last bit of memory. That isn't the only platform having such issues
> I've seen and debugging has always been very painful so I'm wondering
> if as a general precaution we should just leave the last page of memory
> unused.

If I understand you right, I think thats pretty much what patch 1 does,
or rather it allows such a region to be created but reduces the length
so it doesn't quite reach the end, I suppose assuming it will get
rounded down to a page boundary.

Cheers
James

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-08-16 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 12:21 [PATCH 0/2] MIPS: Memory setup tweaks James Hogan
2016-08-09 12:21 ` James Hogan
2016-08-09 12:21 ` [PATCH 1/2] MIPS: Allow memory reaching top of physical James Hogan
2016-08-09 12:21   ` James Hogan
2016-08-09 12:21 ` [PATCH 2/2] MIPS: MAAR: Fix address alignment James Hogan
2016-08-09 12:21   ` James Hogan
2016-08-16 15:36 ` [PATCH 0/2] MIPS: Memory setup tweaks Ralf Baechle
2016-08-16 15:39   ` James Hogan [this message]
2016-08-16 15:39     ` James Hogan

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=20160816153952.GZ19514@jhogan-linux.le.imgtec.org \
    --to=james.hogan@imgtec.com \
    --cc=linux-mips@linux-mips.org \
    --cc=paul.burton@imgtec.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