From: Larry Bassel <lbassel@codeaurora.org>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-arm-msm@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Nicolas Pitre <nico@fluxnic.net>
Subject: Re: how can I cleanly exclude memory from the kernel memory allocator?
Date: Tue, 19 Apr 2011 16:33:36 -0700 [thread overview]
Message-ID: <20110419233336.GF29359@labbmf-linux.qualcomm.com> (raw)
In-Reply-To: <20110325202755.GA13574@n2100.arm.linux.org.uk>
On 25 Mar 11 20:27, Russell King - ARM Linux wrote:
> On Fri, Mar 25, 2011 at 10:39:28AM -0700, Larry Bassel wrote:
> > OK, please ignore my previous mail, I see that .fixup can be
> > used to adjust tags. It appears to me, however, that using a
> > .reserve function calling memblock_reserve will be an
> > easier way of doing what I need.
>
> Absolutely.
Hopefully I'm just missing something obvious, but
when I call memblock_reserve (in .38) to reserve a block
of memory away from the general kernel memory pool,
I find that an ioremap of memory within the reserved block
still fails because pte_valid() is apparently true.
Is this intended behavior? If so, what would the
correct way of separating memory from the system be
so that there is no longer a 1-to-1 1M mapping for
this memory and ioremap (creating the *only* mapping
for this memory) is allowed?
Thanks.
Larry
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: lbassel@codeaurora.org (Larry Bassel)
To: linux-arm-kernel@lists.infradead.org
Subject: how can I cleanly exclude memory from the kernel memory allocator?
Date: Tue, 19 Apr 2011 16:33:36 -0700 [thread overview]
Message-ID: <20110419233336.GF29359@labbmf-linux.qualcomm.com> (raw)
In-Reply-To: <20110325202755.GA13574@n2100.arm.linux.org.uk>
On 25 Mar 11 20:27, Russell King - ARM Linux wrote:
> On Fri, Mar 25, 2011 at 10:39:28AM -0700, Larry Bassel wrote:
> > OK, please ignore my previous mail, I see that .fixup can be
> > used to adjust tags. It appears to me, however, that using a
> > .reserve function calling memblock_reserve will be an
> > easier way of doing what I need.
>
> Absolutely.
Hopefully I'm just missing something obvious, but
when I call memblock_reserve (in .38) to reserve a block
of memory away from the general kernel memory pool,
I find that an ioremap of memory within the reserved block
still fails because pte_valid() is apparently true.
Is this intended behavior? If so, what would the
correct way of separating memory from the system be
so that there is no longer a 1-to-1 1M mapping for
this memory and ioremap (creating the *only* mapping
for this memory) is allowed?
Thanks.
Larry
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-04-19 23:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 22:18 how can I cleanly exclude memory from the kernel memory allocator? Larry Bassel
2011-03-24 22:18 ` Larry Bassel
2011-03-24 23:14 ` Colin Cross
2011-03-24 23:14 ` Colin Cross
2011-03-25 17:37 ` Larry Bassel
2011-03-25 17:37 ` Larry Bassel
2011-03-24 23:27 ` Nicolas Pitre
2011-03-24 23:27 ` Nicolas Pitre
2011-03-25 15:28 ` Larry Bassel
2011-03-25 15:28 ` Larry Bassel
2011-03-25 17:39 ` Larry Bassel
2011-03-25 17:39 ` Larry Bassel
2011-03-25 20:27 ` Russell King - ARM Linux
2011-03-25 20:27 ` Russell King - ARM Linux
2011-04-19 23:33 ` Larry Bassel [this message]
2011-04-19 23:33 ` Larry Bassel
2011-04-19 23:40 ` Larry Bassel
2011-04-19 23:40 ` Larry Bassel
2011-04-20 6:48 ` Colin Cross
2011-04-20 6:48 ` Colin Cross
2011-04-20 19:22 ` Larry Bassel
2011-04-20 19:22 ` Larry Bassel
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=20110419233336.GF29359@labbmf-linux.qualcomm.com \
--to=lbassel@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@fluxnic.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.