From: Jed Smith <jsmith@linode.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Re: [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update
Date: Fri, 21 Aug 2009 12:30:40 -0400 [thread overview]
Message-ID: <4A8ECBB0.2050007@linode.com> (raw)
In-Reply-To: <4A8EC964.3020605@goop.org>
Jeremy Fitzhardinge wrote:
> Well, to be honest, I can't say I can get very excited about tracking
> down where a bug *disappeared*. Do you have a strong need to support
> current kernels on old versions of Xen, or would it be simpler to update
> Xen?
We understand! You have a lot on your plate. We had reached that
conclusion already, and we just wondered if there was an easy fix.
Soaking dev time into a bug that has disappeared is never appealing.
We'll queue upgrades for our affected machines.
> (Though I suspect that PARAVIRT_SPINLOCKS may be the explanation in this
> case, assuming you have them enabled.)
Don't have *PARAVIRT_SPINLOCK* in .config for my kernels...hm. Just
stuff for debugging spinlocks and the usual PARAVIRT options.
Jed
>
> J
>
next prev parent reply other threads:[~2009-08-21 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 0:26 [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update Christopher S. Aker
2009-08-18 4:30 ` Jeremy Fitzhardinge
2009-08-18 14:16 ` Christopher S. Aker
2009-08-18 20:15 ` Jeremy Fitzhardinge
2009-08-18 20:56 ` Jeremy Fitzhardinge
2009-08-20 19:11 ` Jed Smith
2009-08-20 23:31 ` Jeremy Fitzhardinge
2009-08-21 0:13 ` Jed Smith
2009-08-21 0:38 ` Jeremy Fitzhardinge
2009-08-21 14:57 ` Jed Smith
2009-08-21 16:20 ` Jeremy Fitzhardinge
2009-08-21 16:30 ` Jed Smith [this message]
2009-08-21 16:16 ` Jeremy Fitzhardinge
2009-08-21 17:02 ` Jed Smith
2009-08-21 17:44 ` Jeremy Fitzhardinge
2009-08-21 16:16 ` Jeremy Fitzhardinge
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=4A8ECBB0.2050007@linode.com \
--to=jsmith@linode.com \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.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.