All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jed Smith <jsmith@linode.com>
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: Thu, 20 Aug 2009 17:38:52 -0700	[thread overview]
Message-ID: <4A8DEC9C.50207@goop.org> (raw)
In-Reply-To: <4A8DE6B7.7060001@linode.com>

On 08/20/09 17:13, Jed Smith wrote:
> Jeremy Fitzhardinge wrote:
>   
>> I see your bisect tested c47c1b1f3a9 as OK, so try e4d0407185.
>>     
> jsmith@lindev7:~/linux-2.6$ git reset --hard e4d0407185
> HEAD is now at e4d0407 xen: use direct ops on 64-bit
>
> http://lateralus.jedsmith.org/Jeremy1/
>
> Fails as before there.  I bisected using that commit as the right side
> before, but most of the kernels I built failed to boot before the first
> printk(); I wasn't sure if there was something environmental going on.
>   

Yes, there's a lot of stuff on that line which will not bisect well;
there were substantial changes to percpu data handling, and a change to
some of the core pvops calling conventions.  It will take care to choose
good bisection points to narrow things down.

But it also sounds like it could be on the Xen side.  Would it be
possible to try and narrow down where Xen stops breaking?

    J

  reply	other threads:[~2009-08-21  0:38 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 [this message]
2009-08-21 14:57               ` Jed Smith
2009-08-21 16:20                 ` Jeremy Fitzhardinge
2009-08-21 16:30                   ` Jed Smith
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=4A8DEC9C.50207@goop.org \
    --to=jeremy@goop.org \
    --cc=jsmith@linode.com \
    --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.