From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Jon Dufresne <jon.dufresne@infinitevideocorporation.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
Date: Tue, 12 Jun 2007 11:08:21 -0700 [thread overview]
Message-ID: <466EE115.9030805@zytor.com> (raw)
In-Reply-To: <6278d2220706121001r38a1752axba90de1b4e315f75@mail.gmail.com>
Daniel J Blueman wrote:
> On 12 Jun, 14:30, Jon Dufresne
> <jon.dufresne@infinitevideocorporation.com> wrote:
>> I am writing a linux kernel driver for a custom pci device. I am
>> developing against the stock fedora 6 kernel on an x86. This device has
>> 512 MB of IO memory reserved by BAR 3. Whenever I try to ioremap this
>> space I get the error:
You don't have a prayer mapping 512 MB at once on an x86-32 machine.
The kernel only has 1 GB of address space *total*. You either need to
map it in chunks or restrict yourself to 64-bit machines.
>> allocation failed: out of vmalloc space - use vmalloc=<size> to increase
>> size.
>>
>> I think I understand why this is happening. I obviously don't have
>> enough vmalloc space to map such a large chunk of memory. I have been
>> using Corbet's et el's "Linux Device Drivers", Love's "Linux Kernel
>> Development", and many websites as a guide in this development process
>> but have yet to come across information that will help me.
>>
>> I'm curious if there is a way around this issue. Or a better way of
>> handling it so that I can properly map the entire io memory space.
No chance.
> You can boot with kernel parameter vmalloc=384M or so. I have
> experienced problems with booting with other values, but YMMV.
The vmalloc= option conflicts with the booting protocol, so it's
basically a crapshoot if it's going to work or not, at least if you're
using an initrd, which pretty much everyone does hese days.
-hpa
next prev parent reply other threads:[~2007-06-12 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 17:01 allocation failed: out of vmalloc space - use vmalloc=<size> to increase size Daniel J Blueman
2007-06-12 18:08 ` H. Peter Anvin [this message]
2007-06-12 19:21 ` Jon Dufresne
2007-06-12 20:22 ` H. Peter Anvin
2007-06-18 12:16 ` Jon Dufresne
[not found] <fa.VH1FnGj5K9OwLz/eErQti4itl2k@ifi.uio.no>
2007-06-12 14:40 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2007-06-12 13:22 Jon Dufresne
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=466EE115.9030805@zytor.com \
--to=hpa@zytor.com \
--cc=daniel.blueman@gmail.com \
--cc=jon.dufresne@infinitevideocorporation.com \
--cc=linux-kernel@vger.kernel.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).