From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Junio C Hamano <junkio@cox.net>
Cc: sithglan@stud.uni-erlangen.de, git@vger.kernel.org
Subject: Re: Using pickaxe to track changed symbol CR4_FEATURES_ADDR
Date: Mon, 5 Jun 2006 13:11:51 -0700 [thread overview]
Message-ID: <20060605131151.b8878c7c.rdunlap@xenotime.net> (raw)
In-Reply-To: <7v8xob4bft.fsf@assigned-by-dhcp.cox.net>
On Mon, 05 Jun 2006 13:03:34 -0700 Junio C Hamano wrote:
> Thomas Glanzmann <sithglan@stud.uni-erlangen.de> writes:
>
> > I am looking for the symbol CR4_FEATURES_ADDR which must be gone in one
> > of the last kernel revision. Now how I do use pickaxe to track any
> > changes that involve my missing symbol? Or is there a better way to
> > track that change down?
>
> None of the major recent versions seem to have the symbol.
>
> : gitster; git grep -e CR4_FEATURES_ADDR \
> v2.6.12-rc2 v2.6.12 v2.6.13 v2.6.14 v2.6.15 \
> v2.6.16
>
> and I did not get any google hits for "CR4_FEATURES_ADDR". Are
> you spelling it right?
include/asm-i386/processor.h has names like:
/*
* Intel CPU features in CR4
*/
#define X86_CR4_VME 0x0001 /* enable vm86 extensions */
#define X86_CR4_PVI 0x0002 /* virtual interrupts flag enable */
#define X86_CR4_TSD 0x0004 /* disable time stamp at ipl 3 */
#define X86_CR4_DE 0x0008 /* enable debugging extensions */
#define X86_CR4_PSE 0x0010 /* enable page size extensions */
#define X86_CR4_PAE 0x0020 /* enable physical address extensions */
#define X86_CR4_MCE 0x0040 /* Machine check enable */
#define X86_CR4_PGE 0x0080 /* enable global pages */
#define X86_CR4_PCE 0x0100 /* enable performance counters at ipl 3 */
#define X86_CR4_OSFXSR 0x0200 /* enable fast FPU save and restore */
#define X86_CR4_OSXMMEXCPT 0x0400 /* enable unmasked SSE exceptions */
extern unsigned long mmu_cr4_features;
static inline void set_in_cr4 (unsigned long mask)
{
unsigned cr4;
mmu_cr4_features |= mask;
cr4 = read_cr4();
cr4 |= mask;
write_cr4(cr4);
}
static inline void clear_in_cr4 (unsigned long mask)
{
unsigned cr4;
mmu_cr4_features &= ~mask;
cr4 = read_cr4();
cr4 &= ~mask;
write_cr4(cr4);
}
but nothing exactly like you asked about.
---
~Randy
next prev parent reply other threads:[~2006-06-05 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 10:26 Using pickaxe to track changed symbol CR4_FEATURES_ADDR Thomas Glanzmann
2006-06-05 12:43 ` Andreas Ericsson
2006-06-05 20:03 ` Junio C Hamano
2006-06-05 20:11 ` Randy.Dunlap [this message]
2006-06-05 20:16 ` Thomas Glanzmann
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=20060605131151.b8878c7c.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=sithglan@stud.uni-erlangen.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).