From: Andi Kleen <ak@suse.de>
To: Andi Kleen <ak@suse.de>, linux-arch@vger.kernel.org
Subject: Re: You might need vmalloc_sync_all()
Date: Tue, 1 May 2007 13:37:33 +0200 [thread overview]
Message-ID: <20070501113733.GW25929@bingen.suse.de> (raw)
In-Reply-To: <20070501074419.GA8120@flint.arm.linux.org.uk>
> What's this?
Hmm, when I look now at your source I don't see one either. Maybe
the reporter had a strangely patched kernel.
Anyways, point stands -- for on demand module mappings you likely
want vmalloc_sync_all to avoid nested faults. If you think you
can handle the nested faults safely then ignore it @)
>
> > Apparently at least ARM has this problem.
>
> Is there a bug report?
Forwarded it.
-Andi
next prev parent reply other threads:[~2007-05-01 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 4:26 You might need vmalloc_sync_all() Andi Kleen
2007-05-01 7:44 ` Russell King
2007-05-01 11:37 ` Andi Kleen [this message]
2007-05-01 19:20 ` Russell King
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=20070501113733.GW25929@bingen.suse.de \
--to=ak@suse.de \
--cc=linux-arch@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 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.