From: Christoph Hellwig <hch@infradead.org>
To: Antony Suter <suterant@users.sourceforge.net>
Cc: Christoph Hellwig <hch@infradead.org>,
List LKML <linux-kernel@vger.kernel.org>,
torvalds@osdl.org
Subject: Re: [PATCH] __VMALLOC_RESERVE export
Date: Mon, 27 Sep 2004 19:43:53 +0100 [thread overview]
Message-ID: <20040927194353.A26669@infradead.org> (raw)
In-Reply-To: <1096309603.9430.17.camel@hikaru.lan>; from suterant@users.sourceforge.net on Tue, Sep 28, 2004 at 04:26:43AM +1000
On Tue, Sep 28, 2004 at 04:26:43AM +1000, Antony Suter wrote:
> On Tue, 2004-09-28 at 03:12, Christoph Hellwig wrote:
> > On Tue, Sep 28, 2004 at 03:03:43AM +1000, Antony Suter wrote:
> > > __VMALLOC_RESERVE itself is not exported but is used by something that
> > > is. This patch is against 2.6.9-rc2-bk11
> > >
> > > This is required by the nvidia binary driver 1.0.6111
> >
> > And the driver does absolutely nasty things it shouldn't do. This is an
> > implementation detail that absolutely should not be exported.
>
> However __VMALLOC_RESERVE, specific to arch-i386 is now used by the
> macro MAXMEM. MAXMEM is _not_ specific to arch-i386. The nvidia driver
> has a kernel module that uses the macro MAXMEM. Is it wrong for a kernel
> module to use MAXMEM?
Yes.
next prev parent reply other threads:[~2004-09-27 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 17:03 [PATCH] __VMALLOC_RESERVE export Antony Suter
2004-09-27 17:12 ` Christoph Hellwig
2004-09-27 18:26 ` Antony Suter
2004-09-27 18:43 ` Christoph Hellwig [this message]
2004-09-27 19:55 ` Tonnerre
2004-09-27 20:15 ` Christoph Hellwig
2004-09-27 19:53 ` Tonnerre
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=20040927194353.A26669@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suterant@users.sourceforge.net \
--cc=torvalds@osdl.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.