Paravirt-ops UP bug, status check

Paravirt-ops UP bug, status check

[steven maresca]

[-- Attachment #1.1: Type: text/plain, Size: 804 bytes --]

[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

[-- Attachment #1.2: Type: text/html, Size: 940 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Paravirt-ops UP bug, status check

[Jeremy Fitzhardinge]

steven maresca wrote:
> 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?

The fix for this should already be in Linus's git tree, or it will be
soon.  There's no big downside to running an SMP kernel anyway though.

    J