mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	hpa@zytor.com
Subject: Re: [X86] Move the AMD64 specific parts out of setup_64.c
Date: Fri, 23 May 2008 15:16:36 +0200	[thread overview]
Message-ID: <20080523131636.GH9245@ucw.cz> (raw)
In-Reply-To: <200805221944.m4MJiAC6029820@gelk.kernelslacker.org>

Hi!

> Create a separate amd_64.c file in the cpu/ dir for
> the useful parts to live in.
> 

> +#define ENABLE_C1E_MASK		0x18000000
> +#define CPUID_PROCESSOR_SIGNATURE	1
> +#define CPUID_XFAM		0x0ff00000
> +#define CPUID_XFAM_K8		0x00000000
> +#define CPUID_XFAM_10H		0x00100000
> +#define CPUID_XFAM_11H		0x00200000
> +#define CPUID_XMOD		0x000f0000
> +#define CPUID_XMOD_REV_F	0x00040000
> +
> +/* AMD systems with C1E don't have a working lAPIC timer. Check for that. */
> +static __cpuinit int amd_apic_timer_broken(void)
> +{
> +	u32 lo, hi, eax = cpuid_eax(CPUID_PROCESSOR_SIGNATURE);
> +
> +	switch (eax & CPUID_XFAM) {
> +	case CPUID_XFAM_K8:
> +		if ((eax & CPUID_XMOD) < CPUID_XMOD_REV_F)
> +			break;
> +	case CPUID_XFAM_10H:
> +	case CPUID_XFAM_11H:
> +		rdmsr(MSR_K8_ENABLE_C1E, lo, hi);
> +		if (lo & ENABLE_C1E_MASK)
> +			return 1;
> +		break;
> +	default:
> +		/* err on the side of caution */
> +		return 1;
> +	}
> +	return 0;
> +}

This needs to be done in 32-bit kernel, too, right?

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2008-05-23 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 19:44 Dave Jones
2008-05-23 13:16 ` Pavel Machek [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=20080523131636.GH9245@ucw.cz \
    --to=pavel@suse.cz \
    --cc=davej@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.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

all inboxes | Powered by JetHome®