From: Dan Malek <dan@mvista.com>
To: michdaen@iiic.ethz.ch
Cc: dri-devel@lists.sourceforge.net, linuxppc-dev@lists.linuxppc.org
Subject: Re: PPC Lockup (ati-pcigart-branch)
Date: Thu, 18 Jan 2001 22:55:47 -0500 [thread overview]
Message-ID: <3A67BAC3.94EFEA3A@mvista.com> (raw)
In-Reply-To: 3A67B401.8282A00F@relog.ch
Michel Dänzer wrote:
>
> [CC'ing linuxppc-dev, hopefully someone there knows what might be up...]
>
> This is where it dies:
>
> /* FIXME: We should really have a kernel call for this...
> */
> entry->virtual = __vmalloc( (pages << PAGE_SHIFT),
> GFP_KERNEL,
> PAGE_KERNEL);
This isn't very much information, but only one thing can really
be wrong........
What is the value of 'pages'? I suspect it is huge (and perhaps
wrong). The GFP_KERNEL flag will cause vmalloc() to wait for pages
to become available (i.e. it will swap other things out). If this
value in incorrect, this call will wait forever for pages that are
never going to arrive. Worse, it is going to keep sucking up pages
and holding them, so nothing else is going to run either. Is "pages"
really the number of pages, or a size that was never converted to pages?
...and for the 'FIXME' comment, you want a function that does
what? vmalloc? Why don't you just call it (or one of the more
appropriate variants if necessary)?
-- Dan
--
I like MMUs because I don't have a real life.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-19 3:55 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 3:26 PPC Lockup (ati-pcigart-branch) Michel Dänzer
2001-01-19 3:55 ` Dan Malek [this message]
2001-01-19 6:53 ` [Dri-devel] " Gareth Hughes
2001-01-19 16:48 ` Jeff Hartmann
2001-01-19 17:24 ` Dan Malek
2001-01-20 0:45 ` Gareth Hughes
2001-01-19 16:40 ` [Dri-devel] " Jeff Hartmann
2001-01-19 17:11 ` Benjamin Herrenschmidt
2001-01-19 22:26 ` Chris Emerson
2001-01-19 22:59 ` Benjamin Herrenschmidt
2001-01-19 23:43 ` Chris Emerson
2001-01-20 1:38 ` Benjamin Herrenschmidt
2001-01-20 13:21 ` Michael Schmitz
2001-01-20 16:00 ` Benjamin Herrenschmidt
2001-01-20 17:03 ` Michael Schmitz
2001-01-20 2:46 ` Michel Dänzer
2001-01-20 4:17 ` Michel Dänzer
2001-01-22 9:44 ` Michel Dänzer
2001-01-22 17:59 ` Roman Zippel
2001-01-22 18:18 ` Michel Dänzer
2001-01-22 18:54 ` Roman Zippel
2001-01-22 19:39 ` Dan Malek
2001-01-22 20:08 ` Michel Dänzer
2001-01-22 20:30 ` Jeff Hartmann
2001-01-22 21:23 ` Roman Zippel
2001-01-22 23:12 ` Frank Rowand
2001-01-22 21:31 ` Dan Malek
2001-01-22 21:48 ` Jeff Hartmann
2001-01-22 22:15 ` Roman Zippel
2001-01-23 16:14 ` Mike Beede
2001-01-22 22:31 ` Roman Zippel
2001-01-23 0:24 ` Dan Malek
2001-01-23 2:28 ` Takashi Oe
2001-01-23 2:40 ` Dan Malek
2001-01-23 4:40 ` Ralph Metzler
2001-01-23 5:48 ` Takashi Oe
2001-01-23 11:24 ` Roman Zippel
2001-01-23 0:34 ` Frank Rowand
2001-01-23 0:43 ` Frank Rowand
2001-01-23 11:32 ` Roman Zippel
2001-01-22 20:43 ` Roman Zippel
2001-01-22 21:07 ` Jeff Hartmann
2001-01-22 17:33 ` Dan Malek
2001-01-22 17:38 ` Jeff Hartmann
2001-01-22 17:38 ` Gareth Hughes
2001-01-22 17:43 ` Michel Dänzer
2001-01-22 18:36 ` Dan Malek
2001-01-22 18:44 ` Jeff Hartmann
2001-01-22 18:47 ` Michel Dänzer
2001-01-22 21:13 ` Dan Malek
2001-01-22 21:58 ` Roman Zippel
2001-01-22 23:48 ` Paul Mackerras
2001-01-23 0:13 ` Dan Malek
2001-01-20 13:15 ` Michael Schmitz
2001-01-19 17:11 ` Wolfgang Denk
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=3A67BAC3.94EFEA3A@mvista.com \
--to=dan@mvista.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michdaen@iiic.ethz.ch \
/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.