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

[Xen-devel] Xen not running the pmtimer's timer on VCPUs different from

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen not running the pmtimer's timer on VCPUs different from VCPU#0
From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
Date: Thu, 3 Mar 2011 06:45:32 -0500 (EST)
Cc: keir.fraser@xxxxxxxxxx, kouya@xxxxxxxxxxxxxx
Delivery-date: Thu, 03 Mar 2011 03:46:06 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

in order to support kdump/kexec on multiprocessor HVM guests, the patch at
http://xenbits.xensource.com/xen-unstable.hg/rev/19907 was committed.
The patch migrates all timers (via the pt infrastructure) to a VCPU whose
LAPIC is configured to receive the legacy 8259 interrupts.

In doing this, however, the pmtimer is left out.  Its timer won't ever
move away from VCPU#0.  Is there a reason for this, or is it just an
oversight?

Thanks in advance,

Paolo

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

<Prev in Thread] Current Thread [Next in Thread>