From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] RealView: Add sparsemem support for the RealView PBX platform
Date: Mon, 09 Nov 2009 10:53:56 +0000 [thread overview]
Message-ID: <1257764036.21820.29.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20091109103957.GB15646@n2100.arm.linux.org.uk>
On Mon, 2009-11-09 at 10:39 +0000, Russell King - ARM Linux wrote:
> On Mon, Nov 09, 2009 at 10:34:06AM +0000, Catalin Marinas wrote:
> > I don't think it's worth the hassle anyway. If you have
> > REALVIEW_HIGH_PHYS_OFFSET disabled and FLATMEM, you end up with only
> > 256MB of RAM available, I don't really see a point in this
> > configuration. With the new patch, if you don't like SPARSEMEM (maybe
> > for benchmarking reasons), just enable REALVIEW_HIGH_PHYS_OFFSET.
> >
> > So, are you OK with the latest patch?
>
> In that case, yes.
OK, I updated the for-rmk branch.
Thanks.
--
Catalin
prev parent reply other threads:[~2009-11-09 10:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 12:21 [PATCH 0/4] RealView patches for 2.6.33 Catalin Marinas
2009-10-15 12:21 ` [PATCH 1/4] RealView: Add default memory configuration Catalin Marinas
2009-10-15 12:21 ` [PATCH 2/4] RealView: Remove duplicated #define REALVIEW_SYS_FLAGS* statements Catalin Marinas
2009-10-15 12:22 ` [PATCH 3/4] Revert 75f4aa1 (unconditionally define __virt_to_phys and __phys_to_virt) Catalin Marinas
2009-10-19 15:34 ` Russell King - ARM Linux
2009-10-19 15:46 ` Catalin Marinas
2009-10-19 15:54 ` Russell King - ARM Linux
2009-10-15 12:22 ` [PATCH 4/4] RealView: Add sparsemem support for the RealView PBX platform Catalin Marinas
2009-10-19 15:46 ` Russell King - ARM Linux
2009-10-19 16:03 ` Catalin Marinas
2009-11-08 17:45 ` Russell King - ARM Linux
2009-11-09 9:51 ` Catalin Marinas
2009-11-09 10:18 ` Russell King - ARM Linux
2009-11-09 10:34 ` Catalin Marinas
2009-11-09 10:39 ` Russell King - ARM Linux
2009-11-09 10:53 ` Catalin Marinas [this message]
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=1257764036.21820.29.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--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