Re: [Xen-devel] [xen-unstable bisection] complete test-amd64-i386-xl-qemut-ws16-amd64

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
> Sent: 06 May 2019 10:27
> To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
> Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>; osstest service owner 
> <osstest-admin@xxxxxxxxxxxxxx>
> Subject: Fwd: [xen-unstable bisection] complete 
> test-amd64-i386-xl-qemut-ws16-amd64
> 
> Paul,
> 
> >>> On 05.05.19 at 12:54, <osstest-admin@xxxxxxxxxxxxxx> wrote:
> > branch xen-unstable
> > xenbranch xen-unstable
> > job test-amd64-i386-xl-qemut-ws16-amd64
> > testid windows-install
> >
> > Tree: linux git://xenbits.xen.org/linux-pvops.git
> > Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> > Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.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:  26fba3c85571354ecb1a1a3dde77fb38633515d3
> >   Bug not present: a85089d0ef57a08fe97864579ee055c12fd8a928
> >   Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/135744/
> >
> >
> >   commit 26fba3c85571354ecb1a1a3dde77fb38633515d3
> >   Author: Paul Durrant <paul.durrant@xxxxxxxxxx>
> >   Date:   Tue Mar 19 16:29:00 2019 +0100
> >
> >       viridian: add implementation of synthetic timers
> >
> >       This patch introduces an implementation of the 
> > STIMER0-15_CONFIG/COUNT MSRs
> >       and hence a the first SynIC message source.
> >
> >       The new (and documented) 'stimer' viridian enlightenment group may be
> >       specified to enable this feature.
> >
> >       While in the neighbourhood, this patch adds a missing check for an
> >       attempt to write the time reference count MSR, which should result in 
> > an
> >       exception (but not be reported as an unimplemented MSR).
> >
> >       NOTE: It is necessary for correct operation that timer expiration and
> >             message delivery time-stamping use the same time source as the 
> > guest.
> >             The specification is ambiguous but testing with a Windows 10 
> > 1803
> >             guest has shown that using the partition reference counter as a
> >             source whilst the guest is using RDTSC and the reference tsc 
> > page
> >             does not work correctly. Therefore the time_now() function is 
> > used.
> >             This implements the algorithm for acquiring partition reference 
> > time
> >             that is documented in the specifiction.
> >
> >       Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx>
> >       Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
> >       Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
> 
> Just in case you've not noticed this.

I hadn't notice. Thanks for highlighting. I'm kind of surprised as XenServer 
testing showed no major issues with stimer and indeed it is now on by default 
in the latest release. I'll take a look.

  Paul

> 
> Jan
> 


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