All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gareth Hughes <gareth@valinux.com>
To: Dan Malek <dan@mvista.com>
Cc: michdaen@iiic.ethz.ch, dri-devel@lists.sourceforge.net,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: [Dri-devel] Re: PPC Lockup (ati-pcigart-branch)
Date: Sat, 20 Jan 2001 11:45:59 +1100	[thread overview]
Message-ID: <3A68DFC7.20F2A56D@valinux.com> (raw)
In-Reply-To: 3A687848.B7BE3116@mvista.com


Dan Malek wrote:
>
> Hmmm....vmalloc() definitely works fine, we use it all of the
> time in the kernel.  The only way it would hang is if you call
> it too soon, or if the number of pages was too large.

Yes.

> > .....and we really should be using
> > vmalloc_32(...) instead (which will result in exactly the same code, but
> > it is cleaner).
>
> It's no longer the same.  Linux has the "highmem" configuration now,
> and vmalloc() allows that to be used, while vmalloc32() does not.

If you look, we've just included the vmalloc_32() code inline, using
__vmalloc().  We're not using the regular highmem vmalloc().

-- Gareth

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-01-20  0:45 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
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 [this message]
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=3A68DFC7.20F2A56D@valinux.com \
    --to=gareth@valinux.com \
    --cc=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.