All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "xen.org" <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [linux-linus test] 17926: regressions - FAIL
Date: Mon, 13 May 2013 16:24:33 -0400	[thread overview]
Message-ID: <20130513202433.GG15684@phenom.dumpdata.com> (raw)
In-Reply-To: <osstest-17926-mainreport@xen.org>

On Thu, May 09, 2013 at 03:52:47PM +0100, xen.org wrote:
> flight 17926 linux-linus real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/17926/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-xl-credit2   10 guest-saverestore         fail REGR. vs. 12557
>  test-amd64-i386-xl           10 guest-saverestore         fail REGR. vs. 12557
>  test-amd64-i386-rhel6hvm-amd  7 redhat-install            fail REGR. vs. 12557
>  test-amd64-i386-pair   17 guest-migrate/src_host/dst_host fail REGR. vs. 12557

So this is interesting. I noticed that even a local save/restore of any
guest when the host is 32-bit is taking forever. While with a 64-bit host
is done much much faster. (Tens of minutes vs minutes)

Just running 'perf record xm save' showed me that it spends the majority
of time doing the xen_version hypercall (so yield to hypervisor). Hadn't really
dug deeper in this to see if there are some other operations (so block I/Os)
that are just soo much slower on i386 than 64-bit.

      reply	other threads:[~2013-05-13 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09 14:52 [linux-linus test] 17926: regressions - FAIL xen.org
2013-05-13 20:24 ` Konrad Rzeszutek Wilk [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=20130513202433.GG15684@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ian.jackson@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.