All of lore.kernel.org
 help / color / mirror / Atom feed
From: Calum Mackay <calum.mackay@sun.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Calum Mackay <calum.mackay@cdmnet.org>,
	marcelo@conectiva.com.br, mitch.dsouza@sun.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH]  2.4: export the symbol "mmu_cr4_features" for XFree86 DRM kernel drivers
Date: Sat, 02 Aug 2003 12:54:25 +0100	[thread overview]
Message-ID: <3F2BA671.4070800@sun.com> (raw)
In-Reply-To: <20030801141445.A8186@infradead.org>

Christoph Hellwig wrote:
> Can you explain why they need it and why they magically need it
> because of vmap() ?

Sorry, of course.

[as Mitch has already pointed out privately] e.g the XFree86 DRM radeon 
Makefile includes this:

[xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/Makefile.linux]

	# Check for 4-argument vmap() in some 2.5.x and 2.4.x kernels
	VMAP := $(shell grep -A1 'vmap.*count,$$' 
$(LINUXDIR)/include/linux/vmalloc.h | grep -c prot)

	ifneq ($(VMAP),0)
	EXTRA_CFLAGS += -DVMAP_4_ARGS
	endif

Christoph's vmap() backport introduced this reference in 
linux/vmalloc.h, so the DRM module is now compiled with VMAP_4_ARGS defined.

The radeon kernel driver source includes (via drm_memory.h) 
linux/vmalloc.h, iff VMAP_4_ARGS is defined. The latter includes (on 
i386) asm/asm-i386/pgtable.h, which includes asm/asm-i386/processor.h.

processor.h defines some inline functions [set_in_cr4() & 
clear_in_cr4()] which reference mmu_cr4_features.

mmu_cr4_features is currently declared in arch/i386/kernel/setup.c [and 
also arch/x86_64/kernel/setup.c] but not currently exported.

[The problem is not restricted to the radeon kernel driver; I've just 
used it as an example]

cheers,
Calum.


  reply	other threads:[~2003-08-02 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 12:52 [PATCH] 2.4: export the symbol "mmu_cr4_features" for XFree86 DRM kernel drivers Calum Mackay
2003-08-01 13:14 ` Christoph Hellwig
2003-08-02 11:54   ` Calum Mackay [this message]
2003-08-02 12:34     ` Calum Mackay

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=3F2BA671.4070800@sun.com \
    --to=calum.mackay@sun.com \
    --cc=calum.mackay@cdmnet.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mitch.dsouza@sun.com \
    /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.