Re: [PATCH v4 4/4] x86/time: use fake read_tsc()

2022-04-05 Thread Roger Pau Monné
On Mon, Apr 04, 2022 at 05:33:04PM +0200, Jan Beulich wrote: > On 04.04.2022 15:22, Roger Pau Monné wrote: > > On Thu, Mar 31, 2022 at 11:31:38AM +0200, Jan Beulich wrote: > >> Go a step further than bed9ae54df44 ("x86/time: switch platform timer > >> hooks to altcall") did and eliminate the "real"

Re: [PATCH v4 4/4] x86/time: use fake read_tsc()

2022-04-04 Thread Jan Beulich
On 04.04.2022 15:22, Roger Pau Monné wrote: > On Thu, Mar 31, 2022 at 11:31:38AM +0200, Jan Beulich wrote: >> Go a step further than bed9ae54df44 ("x86/time: switch platform timer >> hooks to altcall") did and eliminate the "real" read_tsc() altogether: >> It's not used except in pointer comparison

Re: [PATCH v4 4/4] x86/time: use fake read_tsc()

2022-04-04 Thread Roger Pau Monné
On Thu, Mar 31, 2022 at 11:31:38AM +0200, Jan Beulich wrote: > Go a step further than bed9ae54df44 ("x86/time: switch platform timer > hooks to altcall") did and eliminate the "real" read_tsc() altogether: > It's not used except in pointer comparisons, and hence it looks overall > more safe to simp

[PATCH v4 4/4] x86/time: use fake read_tsc()

2022-03-31 Thread Jan Beulich
Go a step further than bed9ae54df44 ("x86/time: switch platform timer hooks to altcall") did and eliminate the "real" read_tsc() altogether: It's not used except in pointer comparisons, and hence it looks overall more safe to simply poison plt_tsc's read_counter hook. Signed-off-by: Jan Beulich -