> -----Original Message----- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 15 March 2019 09:53 > To: Paul Durrant <paul.durr...@citrix.com> > Cc: Julien Grall <julien.gr...@arm.com>; Andrew Cooper > <andrew.coop...@citrix.com>; Roger Pau Monne > <roger....@citrix.com>; Wei Liu <wei.l...@citrix.com>; George Dunlap > <george.dun...@citrix.com>; Ian > Jackson <ian.jack...@citrix.com>; Stefano Stabellini > <sstabell...@kernel.org>; xen-devel <xen- > de...@lists.xenproject.org>; Konrad Rzeszutek Wilk <konrad.w...@oracle.com>; > Tim (Xen.org) > <t...@xen.org> > Subject: Re: [PATCH v7 10/11] viridian: add implementation of synthetic timers > > >>> On 14.03.19 at 19:11, <paul.durr...@citrix.com> wrote: > > 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.durr...@citrix.com> > > Acked-by: Wei Liu <wei.l...@citrix.com> > > Hypervisor parts > Reviewed-by: Jan Beulich <jbeul...@suse.com> > > I'll get this series in once the tree is fully open again.
Thanks, Paul > > Jan > _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel