All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: M A Young <m.a.young@durham.ac.uk>, Wei Liu <wei.liu2@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Problems using xl migrate
Date: Tue, 25 Nov 2014 22:32:59 +0000	[thread overview]
Message-ID: <5475039B.8010009@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1411252205100.2827@procyon.dur.ac.uk>

On 25/11/2014 22:16, M A Young wrote:
>
>
> On Tue, 25 Nov 2014, Wei Liu wrote:
>
>> On Tue, Nov 25, 2014 at 08:52:00AM +0000, M A Young wrote:
>> [...]
>>>>
>>>> And the said patch has been applied (3460eeb3fc2) so we're fine.
>>>
>>> However that doesn't fix my crash. I tried with it applied and still
>>> saw the
>>> crash. I also tried 4.5-rc1 (without XSM to avoid my other issue)
>>> and that
>>> crashed as well.
>>>
>>
>> And the log is still the same? If the crash happens in different
>> location it might be another bug.
>
> Yes, it is the same crash. Going back to the dprintf command,
>                 DPRINTF("************** pfn=%lx type=%lx gotcs=%08lx "
>                         "actualcs=%08lx\n", pfn, pagebuf->pfn_types[pfn],
>                         csum_page(region_base + i * PAGE_SIZE),
>                         csum_page(buf));
> what does pagebuf->pfn_types[pfn] actually mean and how does it relate
> to the type= it matches. I suspect it should be something else, eg.
> pfn_type[pfn] which would give the page type corresponding to pfn.
>
>     Michael Young

Eugh - this code is horrible.  (The migration v2 code is so much nicer).

"pagebuf->pfn_types[pfn]" is completely bogus in this context, and
should indeed be "pfn_type[pfn]" instead.  The pagebuf->pfn_types[]
array is up to 1024 entries long.

Having said that, it is my firm opinion that verify mode is useless for
anyone who isn't actively developing a migration stream (and even then,
less useful than it would appear to be).  I would skip the "--debug", as
I don't believe it will help you at all in tracking down your issue.

~Andrew

  reply	other threads:[~2014-11-25 22:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 19:24 Problems using xl migrate M A Young
2014-11-24  0:07 ` M A Young
2014-11-24 11:50   ` George Dunlap
2014-11-24 12:06     ` M A Young
2014-11-24 12:21       ` Ian Campbell
2014-11-24 12:29         ` M A Young
2014-11-24 13:13     ` Andrew Cooper
2014-11-24 14:09       ` Wei Liu
2014-11-24 14:13         ` Andrew Cooper
2014-11-25  8:52         ` M A Young
2014-11-25  9:15           ` Wei Liu
2014-11-25 22:16             ` M A Young
2014-11-25 22:32               ` Andrew Cooper [this message]
2014-11-24 12:25 ` George Dunlap
2014-11-24 12:41 ` Wei Liu
2014-11-24 13:15   ` Andrew Cooper
2014-11-24 14:32     ` (4.5-rc1) " M A Young
2014-11-24 14:43       ` Andrew Cooper
2014-11-24 14:55         ` Ian Campbell
2014-11-24 19:28           ` Daniel De Graaf
2014-11-24 20:12         ` M A Young
2014-11-24 22:05           ` Daniel De Graaf
2014-11-25 10:07             ` George Dunlap
2014-11-25 18:03               ` Daniel De Graaf
2014-11-25 18:17                 ` Konrad Rzeszutek Wilk

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=5475039B.8010009@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=m.a.young@durham.ac.uk \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.