[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] why are deep cstates disabled?

  • To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Mon, 19 Oct 2009 18:26:36 +0100
  • Cc:
  • Delivery-date: Mon, 19 Oct 2009 10:27:05 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcpQ3irtI5gfcuxqSRuEGQHOEUsxtAAAyREC
  • Thread-topic: [Xen-devel] why are deep cstates disabled?

On 19/10/2009 18:03, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> My D630 has no HPET... or at least there is no indication
> in the BIOS menu that there is an HPET.

I think you do, since cpuidle_disable_deep_cstate() is called from
handle_rtc_once(), which gets set up as a hook by hpet_broadcast_init(),
which only gets that far If it has managed to initialise an HPET.

> I tried setting "hpetbroadcast" and dom0 boot fails.

Err.. What happens?

> Is there any way to get C3 working on my box or am
> I out of luck?

You could try commenting out function disable_pit_irq() and its __initcall()
invocation. This should cause fallback to pit_broadcast mode. It's a
completely different non-HPET-related approach that you could try.

 -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.