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] [PATCH] xm-test enforce_dom0_cpus

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] xm-test enforce_dom0_cpus
From: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>
Date: Wed, 12 Jul 2006 18:24:07 -0400
Delivery-date: Wed, 12 Jul 2006 15:24:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: AcamAePa/nxK0x54TPeXD0/NlE1JAQ==
Thread-topic: [PATCH] xm-test enforce_dom0_cpus
When running xm-test on an ES7000/one with 32 processors, the enforce_dom0_cpus 
test fails because it takes a while for the cpu count to reduce from 32 to 1.  
This patch increases two timeout values from 20 to 30 seconds.  The timeout 
values are used when waiting for the cpu count to reduce and also to reset.  
The associated comments have also been updated to reflect the new value of 30.
Signed-off-by: Susan Krysan
If this patch is acceptable, could you please apply it to both xen-unstable and 
> Thanks,
> Sue Krysan
> Linux Systems Group
> Unisys Corporation

Attachment: enforce_dom0_cpus.patch
Description: enforce_dom0_cpus.patch

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] xm-test enforce_dom0_cpus, Krysan, Susan <=