 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] Paravirt-ops UP bug, status check
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] Paravirt-ops UP bug, status check |
| From: | "steven maresca" <steve.maresca@xxxxxxxxx> |
| Date: | Thu, 18 Sep 2008 12:42:33 -0400 |
| Delivery-date: | Thu, 18 Sep 2008 09:43:12 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=IuXUPJ5xt7Y67Ko0sVA7Od0kaa3pJqFSzDZL1kHnLPs=; b=vXo3kqvG9FfmaL7A96Iv03DeZNk07aZWhTCht+P8x34hs2GlFec5l5lT2l9N118oSk C722+Hfy8ebp397ceaT0dYRog1RJJZ4sEHO6Mx1lLxzo/LUCMVOqsrmpcua9aU8kD282 UsN0W93be2hXy3fNqx9qKB3pPx60vPX/begPo= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=PPnzkF37+FM2Jsp+qm3cn80TAJpSjNG2R8W1sC8j9i5LbYlleKU/xx3pgIB2iRGStg 7fP/8n5tMcr65WvtvE/xeHmu81/D5AmONS9UNzsxQqSTZCDMy/bOSHnJSltNc9XSXXyR 4KG+HPTPvYKCt9WrsDHtxbT6XI8HAznl94Txw= |
| 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 |
|
[my fault - sent again, this time to xen-devel]
Jeremy, In testing the 2.6.27-rc6 kernel, I at one point neglected to enable SMP, and encountered the same issue as described in the following thread http://lkml.org/lkml/2008/8/31/115 (to which you replied with a hint toward a confirmed workaround). I don't have any issues running a SMP kernel; just wondering whether a) it's easily fixed or b) if UP should be avoided? Do you need more debug information? Also, though it may belong in a separate thread, how is the dom0 work coming along? I noticed your initial round of patches - many thanks for your efforts! If you need specific things tested, etc., I'm quite certain that many here would be willing to assist should you have a laundry list of things that need attention. Thanks, Steven Maresca _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] One question on alloc_bitmap, Keir Fraser |
|---|---|
| Next by Date: | Re: [Xen-devel] Paravirt-ops UP bug, status check, Jeremy Fitzhardinge |
| Previous by Thread: | [Xen-devel] One question on alloc_bitmap, Jiang, Yunhong |
| Next by Thread: | Re: [Xen-devel] Paravirt-ops UP bug, status check, Jeremy Fitzhardinge |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
