All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] xen: correctly rebuild mfn list list after migration.
Date: Thu, 21 Oct 2010 18:28:51 +0100	[thread overview]
Message-ID: <1287682131.29224.629.camel@localhost.localdomain> (raw)
In-Reply-To: <4CC073F6.4070900@goop.org>

On Thu, 2010-10-21 at 18:10 +0100, Jeremy Fitzhardinge wrote: 
> On 10/21/2010 03:10 AM, Ian Campbell wrote:
> > On Thu, 2010-10-14 at 19:27 +0100, Jeremy Fitzhardinge wrote:
> >> On 10/14/2010 01:51 AM, Ian Campbell wrote:
> >>> On Thu, 2010-10-14 at 07:49 +0100, Ian Campbell wrote:
> >>>> On Thu, 2010-10-14 at 01:37 +0100, Jeremy Fitzhardinge wrote:
> >>>>> I'm getting this triggering at boot:
> >>>>>
> >>>>> PM: Adding info for No Bus:xen!gntdev
> >>>>> ------------[ cut here ]------------
> >>>>> kernel BUG at /home/jeremy/git/linux/arch/x86/xen/mmu.c:480! 
> >>>> Probably a consequence of the bogus attempt to skip over completely
> >>>> empty mid levels which you pointed out in your next mail.
> >>>>
> >>>> I guess I should test 64 bit guests and not just PAE ones and I guess
> >>>> pre-ballooning is likely to interact as well.
> >>> I'm only able to reproduce this by booting ballooned and then ballooning
> >>> up, are you doing that or were you seeing it just by booting?
> >>>
> >>> What are your memory and maxmem settings?
> >> memory=512, no maxmem.
> > The BUG_ON I added to alloc_p2m was wrong (converted an mfn to an
> > address in the direct map and then compared it with a virtual address in
> > kernel map, IIRC). Here's an update patch which fixes all your previous
> > comments, this issue and a few other bits and bobs
> >
> > * s/p2m_mid_mfn_p/p2m_top_mfn_p/g
> > * Fix BUG_ON in alloc_p2m
> > * Skip correct number of pfns when mid == p2m_mid_missing
> > * Use correct value p2m_top_mfn[topidx] when mid == p2m_mid_missing
> 
> OK, it passed my sniff test - it boots and save/restored a few times.

Great. 

> (I added a S-O-B for you.)

Oops, thanks.

Ian.

  reply	other threads:[~2010-10-21 17:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 10:14 [PATCH] xen: correctly rebuild mfn list list after migration Ian Campbell
2010-10-14  0:37 ` Jeremy Fitzhardinge
2010-10-14  6:49   ` Ian Campbell
2010-10-14  8:51     ` Ian Campbell
2010-10-14 18:27       ` Jeremy Fitzhardinge
2010-10-21 10:10         ` Ian Campbell
2010-10-21 17:10           ` Jeremy Fitzhardinge
2010-10-21 17:28             ` Ian Campbell [this message]
2010-10-14  1:43 ` Jeremy Fitzhardinge
2010-10-14  6:55   ` Ian Campbell

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=1287682131.29224.629.camel@localhost.localdomain \
    --to=ian.campbell@eu.citrix.com \
    --cc=jeremy@goop.org \
    --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.