xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Jan Beulich <JBeulich@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Fwd: [xen-4.10-testing bisection] complete test-armhf-armhf-xl-arndale
Date: Wed, 19 Jun 2019 10:02:56 +0100	[thread overview]
Message-ID: <60ff0360-50be-8545-45d8-799ef9fcb95b@arm.com> (raw)
In-Reply-To: <5D09E4310200007800239852@prv1-mh.provo.novell.com>

Hi,

On 6/19/19 8:28 AM, Jan Beulich wrote:
>>>> On 19.06.19 at 09:06, <osstest-admin@xenproject.org> wrote:
>> branch xen-4.10-testing
>> xenbranch xen-4.10-testing
>> job test-armhf-armhf-xl-arndale
>> testid debian-install
>>
>> Tree: linux git://xenbits.xen.org/linux-pvops.git
>> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
>> Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
>> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
>> Tree: xen git://xenbits.xen.org/xen.git
>>
>> *** Found and reproduced problem changeset ***
>>
>>    Bug is in tree:  xen git://xenbits.xen.org/xen.git
>>    Bug introduced:  702c9146c00d65d1e9c5955335ba002505e97e09
>>    Bug not present: 52220b5f437a8d03ba108e127e7d717657edf99c
>>    Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/138005/
>>
>>
>>    commit 702c9146c00d65d1e9c5955335ba002505e97e09
>>    Author: Julien Grall <julien.grall@arm.com>
>>    Date:   Mon Apr 29 15:05:16 2019 +0100
>>    
>>        xen/arm: Add an isb() before reading CNTPCT_EL0 to prevent re-ordering
>>        
>>        Per D8.2.1 in ARM DDI 0487C.a, "a read to CNTPCT_EL0 can occur
>>        speculatively and out of order relative to other instructions executed
>>        on the same PE."
>>        
>>        Add an instruction barrier to get accurate number of cycles when
>>        requested in get_cycles(). For the other users of CNPCT_EL0, replace by
>>        a call to get_cycles().
>>        
>>        This is part of XSA-295.
>>        
>>        Signed-off-by: Julien Grall <julien.grall@arm.com>
>>        Acked-by: Stefano Stabellini <sstabellini@kernel.org>
> 
> Just in case you didn't notice this coming in.

I saw it this morning. But I fail to understand how the instruction 
barrier will result in a timeout during the guest installation...

The more this only doesn't seem to appear on staging-4.12.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-06-19  9:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2B31D2BD02000066A2327079@prv1-mh.provo.novell.com>
2019-06-19  7:28 ` [Xen-devel] Fwd: [xen-4.10-testing bisection] complete test-armhf-armhf-xl-arndale Jan Beulich
2019-06-19  9:02   ` Julien Grall [this message]
2019-06-19 15:59     ` Julien Grall
2019-06-19 16:56       ` Stefano Stabellini
2019-06-20 17:24         ` Julien Grall
2019-06-20 23:55           ` Stefano Stabellini
2019-06-21  8:58           ` Jan Beulich
2019-06-21  9:14             ` Julien Grall

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=60ff0360-50be-8545-45d8-799ef9fcb95b@arm.com \
    --to=julien.grall@arm.com \
    --cc=JBeulich@suse.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).