[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86/time: tsc_check_writability() may need to be run a second time

To: Joao Martins <joao.m.martins@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>
From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date: Fri, 10 Feb 2017 11:17:25 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 10 Feb 2017 11:17:34 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 10/02/17 11:11, Joao Martins wrote:
> On 02/10/2017 11:03 AM, Jan Beulich wrote:
>> While we shouldn't remove its current invocation, we need to re-run it
>> for the case that the X86_FEATURE_TSC_RELIABLE feature flag has been
>> cleared, in order to avoid using the TSC rendezvous function in case
>> the TSC can't be written.
>>
>> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
> FWIW,

Independent reviews are always worth it.  Please continue!

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH] x86/time: tsc_check_writability() may need to be run a second time
  - From: Joao Martins

References:
- [Xen-devel] [PATCH] x86/time: tsc_check_writability() may need to be run a second time
  - From: Jan Beulich
- Re: [Xen-devel] [PATCH] x86/time: tsc_check_writability() may need to be run a second time
  - From: Joao Martins

Prev by Date: Re: [Xen-devel] [PATCH] x86/time: tsc_check_writability() may need to be run a second time
Next by Date: [Xen-devel] [qemu-upstream-4.8-testing test] 105678: regressions - trouble: blocked/broken/fail/pass
Previous by thread: Re: [Xen-devel] [PATCH] x86/time: tsc_check_writability() may need to be run a second time
Next by thread: Re: [Xen-devel] [PATCH] x86/time: tsc_check_writability() may need to be run a second time
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.