WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] please revert c/s 17686

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] please revert c/s 17686
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 12 Jun 2008 14:56:08 +0100
Cc: Gang Wei <gang.wei@xxxxxxxxx>, ke.yu@xxxxxxxxx
Delivery-date: Thu, 12 Jun 2008 06:56:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <485140B1.76E4.0078.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjMlBBBTrS+uTiHEd2vlgAX8io7RQ==
Thread-topic: [Xen-devel] please revert c/s 17686
User-agent: Microsoft-Entourage/11.4.0.080122
Probably best to just disable hpet_broadcast_init() for now, as this could
be fixed e.g., by using FSB delivery on some systems. Also the C-state
support looks buggy right now because we shouldn't use C3 (or deeper) unless
hpet_broadcast mechanism is available to us. Otherwise we can sleep forever.

 -- Keir

On 12/6/08 14:28, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> Switching HPET into legacy mode is not acceptable, as this doesn't only
> cut off the PIT channel 0 interrupt, but also the RTC one. The former is
> acceptable as no domain will ever gain control over it, but the latter isn't
> as Dom0 may validly make use of it. I'm observing a failure of setting the
> system clock correctly due to this issue (hwclock checks whether the RTC
> update interrupt is occurring as expected), and I suppose other uses of
> /dev/rtc would also suffer.
> 
> It is my understanding that using the HPET to overcome the APIC timer
> stop issue is therefore impossible at present - you cannot use legacy
> mode, and you also cannot use the individual routing mode as whatever
> IRQ is chosen may turn out being in use by one or more other devices
> (and hence would require sharing the IRQ between Xen and one or more
> guests).
> 
> Thanks, Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel