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/
Home Products Support Community News


[Xen-devel] x86 HPET MSI IRQs vs resume from S3

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] x86 HPET MSI IRQs vs resume from S3
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Fri, 28 Jan 2011 09:23:42 +0000
Delivery-date: Fri, 28 Jan 2011 01:24:18 -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
Going through hpet_broadcast_init(), I see that hpet_setup_msi_irq()
gets called during resume, thus causing setup_irq() to be called. I'm
failing to spot the corresponding release_irq(), and hence I can't see
how this whole code path is supposed to work during resume (other
than always falling back to using legacy_hpet_event). Instead I'm
wondering whether in the resume case only msi_compose_msg()/
hpet_msi_write() should be called for each IRQ used rather than the
whole hpet_broadcast_init().

Thanks for any hints or pointers,

Xen-devel mailing list

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