search for: b0c39dc68e3b

Displaying 6 results from an estimated 6 matches for "b0c39dc68e3b".

2018 Oct 03
4
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
...is > it supposed to update the kvmclock structure? Well, this kind of works in the the followin way: L1's clocksource is 'tsc_page' which is, basically, a compliment to TSC: two numbers provided by L0: offset and scale and KVM was tought to treat this clocksource as a good one (see b0c39dc68e3b "x86/kvm: Pass stable clocksource to guests when running nested on Hyper-V"). The notification you're talking about exists, it is called Reenligntenment, see 0092e4346f49 "x86/kvm: Support Hyper-V reenlightenment"). When TSC page changes (and this only happens when L1 is mi...
2018 Oct 03
4
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
...is > it supposed to update the kvmclock structure? Well, this kind of works in the the followin way: L1's clocksource is 'tsc_page' which is, basically, a compliment to TSC: two numbers provided by L0: offset and scale and KVM was tought to treat this clocksource as a good one (see b0c39dc68e3b "x86/kvm: Pass stable clocksource to guests when running nested on Hyper-V"). The notification you're talking about exists, it is called Reenligntenment, see 0092e4346f49 "x86/kvm: Support Hyper-V reenlightenment"). When TSC page changes (and this only happens when L1 is mi...
2018 Oct 03
0
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
...pdate the kvmclock structure? > > Well, this kind of works in the the followin way: > L1's clocksource is 'tsc_page' which is, basically, a compliment to TSC: > two numbers provided by L0: offset and scale and KVM was tought to treat > this clocksource as a good one (see b0c39dc68e3b "x86/kvm: Pass stable > clocksource to guests when running nested on Hyper-V"). > > The notification you're talking about exists, it is called > Reenligntenment, see 0092e4346f49 "x86/kvm: Support Hyper-V > reenlightenment"). When TSC page changes (and this o...
2018 Oct 03
0
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
...pdate the kvmclock structure? > > Well, this kind of works in the the followin way: > L1's clocksource is 'tsc_page' which is, basically, a compliment to TSC: > two numbers provided by L0: offset and scale and KVM was tought to treat > this clocksource as a good one (see b0c39dc68e3b "x86/kvm: Pass stable > clocksource to guests when running nested on Hyper-V"). > > The notification you're talking about exists, it is called > Reenligntenment, see 0092e4346f49 "x86/kvm: Support Hyper-V > reenlightenment"). When TSC page changes (and this o...
2018 Sep 14
24
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
Matt attempted to add CLOCK_TAI support to the VDSO clock_gettime() implementation, which extended the clockid switch case and added yet another slightly different copy of the same code. Especially the extended switch case is problematic as the compiler tends to generate a jump table which then requires to use retpolines. If jump tables are disabled it adds yet another conditional to the existing
2018 Sep 14
24
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
Matt attempted to add CLOCK_TAI support to the VDSO clock_gettime() implementation, which extended the clockid switch case and added yet another slightly different copy of the same code. Especially the extended switch case is problematic as the compiler tends to generate a jump table which then requires to use retpolines. If jump tables are disabled it adds yet another conditional to the existing