All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [xen-unstable test] 17613: regressions - FAIL
Date: Thu, 11 Apr 2013 09:03:03 +0100	[thread overview]
Message-ID: <CD8C2CC7.20926%keir.xen@gmail.com> (raw)
In-Reply-To: <5166885302000078000CC570@nat28.tlf.novell.com>

On 11/04/2013 08:54, "Jan Beulich" <JBeulich@suse.com> wrote:

>>>> On 11.04.13 at 01:41, xen.org <ian.jackson@eu.citrix.com> wrote:
>> flight 17613 xen-unstable real [real]
>> http://www.chiark.greenend.org.uk/~xensrcts/logs/17613/
>> 
>> Regressions :-(
>> 
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>>  test-amd64-i386-qemut-rhel6hvm-intel  9 guest-start.2     fail REGR. vs.
>> 17610
> 
> So this is one of the BUG_ON()s added by bd9be94 triggering,
> and this is not a false positive. scale_delta() is simply not suitable
> for negative inputs, and the main question is why gtime_to_gtsc()
> caps its input to 0 only for PV domains, or whether (considering
> that this parameter is u64) __update_vcpu_system_time() should
> already cap it to zero. Not to speak of the question how the
> calculation there could end up negative in the first place.

Yes, I think it should be capped where guest time gets set/updated. The time
input to gtime_to_gtsc() should always be non-negative.

 -- Keir

> Stefano, Keir (21445:c1ed00d49534)?
> 
> Jan
> 

      reply	other threads:[~2013-04-11  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 23:41 [xen-unstable test] 17613: regressions - FAIL xen.org
2013-04-11  7:54 ` Jan Beulich
2013-04-11  8:03   ` Keir Fraser [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=CD8C2CC7.20926%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=stefano.stabellini@eu.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.