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 v3 1/7] ARM: Align machine_desc.phys_io to a 1MB section
Date: Mon, 21 Jun 2010 11:26:23 +0100	[thread overview]
Message-ID: <20100621102623.GI7702@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1277114749.20758.24.camel@e102109-lin.cambridge.arm.com>

On Mon, Jun 21, 2010 at 11:05:49AM +0100, Catalin Marinas wrote:
> On Mon, 2010-06-21 at 10:35 +0100, Russell King - ARM Linux wrote:
> > On Mon, Jun 21, 2010 at 10:13:31AM +0100, Catalin Marinas wrote:
> > > Platforms like RealView don't pass a section-aligned pointer via the
> > > machine_desc structure. This patch aligns the pointer in the
> > > __create_page_tables function. Reported by Tony Thompson.
> > 
> > I still say this is the wrong way.  As I've said before, please fix it
> > at the machine_desc initialization point.  
> 
> This requirement doesn't seem to be well documented and platforms don't
> follow it (e.g. RealView and VExpress). Since it's the head.S code
> responsible for this temporary mapping, the platform code wouldn't need
> to know whether sections or pages or something else are used to map it.
> But io_pg_offst already makes the assumption about sections.

We're never going to map it using sections - using pages implies a
way to allocate 2nd level page tables, and we don't have any memory
allocators which can work this early.

> > If you want, pass it as the
> > section frame number itself (address >> 20) rather than the address to
> > allow for more addressing space.
> 
> I would rather go for a PFN to allow more addressing space (but doesn't
> solve the section alignment).

PFNs don't solve the problem you've brought up - might as well stick
with what we have in that case.

  reply	other threads:[~2010-06-21 10:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21  9:13 [PATCH v3 0/7] Patches/fixes for 2.6.35 Catalin Marinas
2010-06-21  9:13 ` [PATCH v3 1/7] ARM: Align machine_desc.phys_io to a 1MB section Catalin Marinas
2010-06-21  9:35   ` Russell King - ARM Linux
2010-06-21 10:05     ` Catalin Marinas
2010-06-21 10:26       ` Russell King - ARM Linux [this message]
2010-06-21  9:13 ` [PATCH v3 2/7] ARM: Avoid the CONSISTENT_DMA_SIZE warning on noMMU builds Catalin Marinas
2010-06-21  9:23   ` Russell King - ARM Linux
2010-06-21  9:53     ` Catalin Marinas
2010-06-21  9:13 ` [PATCH v3 3/7] ARM: The v6_dma_inv_range() function must preserve data on SMP Catalin Marinas
2010-06-21  9:13 ` [PATCH v3 4/7] ARM: Add a config option for the ARM11MPCore DMA cache maintenance workaround Catalin Marinas
2010-06-21  9:13 ` [PATCH v3 5/7] ARM: Add support for the MOVW/MOVT relocations in Thumb-2 Catalin Marinas
2010-06-21  9:13 ` [PATCH v3 6/7] ARM: Remove dummy loads from the original relocation address Catalin Marinas
2010-06-21  9:14 ` [PATCH v3 7/7] ARM: Do not compile the Thumb-2 module relocations on an ARM kernel Catalin Marinas
2010-06-21  9:26   ` Russell King - ARM Linux
2010-06-21  9:37     ` [PATCH v3 7/7] ARM: Do not compile the Thumb-2 modulerelocations " Catalin Marinas
2010-06-21  9:39       ` 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=20100621102623.GI7702@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).