mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: x86_64 and AMD with C1E
Date: Thu, 25 Oct 2007 00:12:42 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0710250007230.3186@localhost.localdomain> (raw)
In-Reply-To: <471FBC09.8050201@redhat.com>

On Wed, 24 Oct 2007, Chuck Ebbert wrote:
> On 10/24/2007 05:26 PM, Mikhail Kshevetskiy wrote:
> >>>
> >>> I fill something wrong here.
> >>> Is it possible to reduce the amount of timer interrupts?
> >>> Is it possible to force enable C1,C2 and C3 states when c1e disabled?
> >>>
> >> How are you disabling C1E?
> >>
> >>
> > dirty hack, i just follow the FreeBSD way and clear C1e bit in lapic
> > initialization code. I make it for test purpose only, so i do not produce a
> > patch.
> > 
> 
> Why does disabling C1E disable C1, C2 and C3?
> 
> Thomas, in the case of the machines where C1E is disabled on CPU 0 but
> enabled on CPU 1, could we just disable it? Maybe it's a BIOS bug and the
> vendor just forgot to disable CPU 1...

It's definitely a BIOS bug and I doubt that disabling the bit works on
every BIOS. I have a system here on my desk, where neither of the CPUs
has the bit set, but the lapic timer stops wreckage is there once both
CPUs go into idle. 

The mindless creativity of BIOS writers seems to exceed the ability of
hardware designers to produce strange chips by orders of magnitude.

   tglx


  reply	other threads:[~2007-10-24 22:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01  6:15 Mikhail Kshevetskiy
2007-10-01  9:33 ` Andi Kleen
     [not found]   ` <b70f2f960710010546k4658aa1ay466f243ac707c989@mail.gmail.com>
2007-10-01 12:50     ` Fwd: " Mikhail Kshevetskiy
2007-10-01 14:14       ` Thomas Gleixner
2007-10-01 14:32         ` Andi Kleen
2007-10-01 14:59           ` Thomas Gleixner
2007-10-01 15:21             ` Andi Kleen
2007-10-01 16:44               ` Thomas Gleixner
2007-10-01 17:56               ` Chuck Ebbert
2007-10-01 14:33         ` Mikhail Kshevetskiy
2007-10-01 13:09     ` Andi Kleen
2007-10-01 14:06       ` Arjan van de Ven
2007-10-01 14:40       ` Mikhail Kshevetskiy
2007-10-19 16:39 ` Chuck Ebbert
2007-10-24 21:26   ` Mikhail Kshevetskiy
2007-10-24 21:41     ` Chuck Ebbert
2007-10-24 22:12       ` Thomas Gleixner [this message]
2007-10-24 22:42       ` Mikhail Kshevetskiy
2007-12-15 11:06       ` Thomas Gleixner

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=alpine.LFD.0.9999.0710250007230.3186@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikhail.kshevetskiy@gmail.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 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®