All of lore.kernel.org
 help / color / mirror / Atom feed
From: Calum Mackay <calum.mackay@sun.com>
To: Calum Mackay <calum.mackay@sun.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	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 13:34:48 +0100	[thread overview]
Message-ID: <3F2BAFE8.3090001@sun.com> (raw)
In-Reply-To: <3F2BA671.4070800@sun.com>

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

Calum Mackay wrote:
> 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.

Sadly, this isn't the full story, since the radeon code doesn't 
reference *_in_cr4.

The radeon code calls io/agp remap functions - again only ifdef 
VMAP_4_ARGS - which do however call __flush_tlb_all(). This manipulates 
the PGE bit via mmu_cr4_features.

apols for the spam...

cheers,
Calum.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3427 bytes --]

      reply	other threads:[~2003-08-02 12:35 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
2003-08-02 12:34     ` Calum Mackay [this message]

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=3F2BAFE8.3090001@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.