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


Re: [Xen-devel] Debugging a weird hardware fault.

To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Debugging a weird hardware fault.
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Thu, 28 Jul 2011 21:42:55 +0100
Delivery-date: Thu, 28 Jul 2011 13:43:45 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=nI3uccHH0pDF5uFLxjtV/PfOnICZch9YIVtqZneWh3U=; b=wIl3eUNbjAkkZIkhZ64Wd3re+TIXQSQNiq7CkQklmK77a8HRwUXBCHOKslfFQdDCRc bK1sHwsOf9742zoF6hGtDU3T4mUpwzGT/hYMnon38Hvg6fjEgcHpYeG1Ugyz8E00BjpX aiCQEJPxxf30BIXMRH/XDV5sFzvbcxCoKWfMg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E31BE38.3020106@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/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
Thread-index: AcxNZu1KSOfHQqC8kEeWRl0hBxZ7qQ==
Thread-topic: [Xen-devel] Debugging a weird hardware fault.
User-agent: Microsoft-Entourage/
On 28/07/2011 20:53, "Andrew Cooper" <andrew.cooper3@xxxxxxxxxx> wrote:

> My questions to the Xen community are:
> what (if any) new tasks get scheduled when a XENPF_enter_acpi_sleep is
> in action, and more generally, how can I go about debugging which tasks
> are being run.

By the time you get to time_suspend(), you are running on CPU0, all other
CPUs are offline, all domUs are suspended, and IRQs are disabled. There's
not much scope for unexpected interruptions unless it's an NMI or SMI.

By that point the serial subsystem is in synchronous mode, rather than
interrupt-driven, so it's no wonder it continues to work.

 -- Keir

Xen-devel mailing list