From: Jeremy Fitzhardinge <jeremy@goop.org>
To: steven maresca <steve.maresca@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Paravirt-ops UP bug, status check
Date: Thu, 18 Sep 2008 11:02:22 -0700 [thread overview]
Message-ID: <48D297AE.80902@goop.org> (raw)
In-Reply-To: <af7d04000809180942g65edb896pbc3a1363ea79bbd8@mail.gmail.com>
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
prev parent reply other threads:[~2008-09-18 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 16:42 Paravirt-ops UP bug, status check steven maresca
2008-09-18 18:02 ` Jeremy Fitzhardinge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48D297AE.80902@goop.org \
--to=jeremy@goop.org \
--cc=steve.maresca@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.