public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-omap@vger.kernel.org
Subject: Re: ioremap()/iounmap() problem
Date: Thu, 22 Jan 2009 13:55:13 +0200	[thread overview]
Message-ID: <1232625313.19861.26.camel@tubuntu> (raw)
In-Reply-To: <20090121192332.GA6469@n2100.arm.linux.org.uk>

Hi,

On Wed, 2009-01-21 at 19:23 +0000, ext Russell King - ARM Linux wrote:
> On Mon, Jan 19, 2009 at 03:49:40PM +0200, Tomi Valkeinen wrote:
> > The original problem remains, it looks to me that iounmap() doesn't free
> > the memory, and thus ioremap will fail after couple of loops.
> > 
> > I get the following error on console:
> > 
> > vmap allocation for size 16781312 failed: use vmalloc=<size> to increase
> > size.
> > 
> > I don't know too much about memory management, but I'll try to dig
> > deeper in to this.
> > 
> > What I don't understand is that in __arm_ioremap_pfn() there's
> > get_vm_area(), and later in the function, in case of error, that area is
> > vunmap()ed. But there's no vunmap() done anywhere else in the code for
> > area sections, so who does free it?
> 
> Yes, the error I pointed out is not the only issue with this code.
> 
> You might consider trying my patch which was sent in this thread to Matt
> Gerassimoff.  And if you see anyone whinging that it won't work for
> whatever reason, please ignore them and just test the patch.  You will
> not be disappointed.

Sorry it took so long to test. The patch indeed works fine, thanks! And
the test loop works also fine even without any schedulings, contrary of
what was speculated. (Not that it matters in real usage).

I'll do some more testing and report if I see any oddities.

 Tomi



  reply	other threads:[~2009-01-22 11:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 10:23 ioremap()/iounmap() problem Tomi Valkeinen
2009-01-19 11:01 ` Russell King - ARM Linux
2009-01-19 12:27   ` Tomi Valkeinen
2009-01-19 12:53     ` Russell King - ARM Linux
2009-01-19 13:49       ` Tomi Valkeinen
2009-01-21 19:23         ` Russell King - ARM Linux
2009-01-22 11:55           ` Tomi Valkeinen [this message]
2009-01-22 15:25             ` Matt Gerassimoff
2009-01-19 13:34 ` Woodruff, Richard
2009-01-19 13:43   ` Russell King - ARM Linux
2009-01-19 13:48     ` Woodruff, Richard
2009-01-19 13:56       ` Russell King - ARM Linux
2009-01-19 15:06         ` Matt Gerassimoff
2009-01-19 15:22           ` Russell King - ARM Linux
2009-01-19 15:39             ` Matt Gerassimoff
2009-01-19 15:58               ` Russell King - ARM Linux
2009-01-19 16:13                 ` Russell King - ARM Linux
2009-01-19 17:07                   ` Matt Gerassimoff
2009-01-19 17:14                     ` Russell King - ARM Linux
2009-01-19 17:47                       ` Matt Gerassimoff
2009-01-19 17:07                   ` Woodruff, Richard

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=1232625313.19861.26.camel@tubuntu \
    --to=tomi.valkeinen@nokia.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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