Re: [PATCH v3 07/10] clocksource/drivers/hyper-v: Handle vDSO differences inline

On 08/03/2021 14:49, Michael Kelley wrote: > From: Michael Kelley Sent: Tuesday, March 2, 2021 > 3:07 PM >> >> From: Daniel Lezcano Sent: Tuesday, March 2, >> 2021 2:14 PM >>> >>> On 02/03/2021 22:38, Michael Kelley wrote: While the driver for the Hyper-V Reference TSC and STIMERs is archi

RE: [PATCH v3 07/10] clocksource/drivers/hyper-v: Handle vDSO differences inline

From: Michael Kelley Sent: Tuesday, March 2, 2021 3:07 PM > > From: Daniel Lezcano Sent: Tuesday, March 2, 2021 > 2:14 PM > > > > On 02/03/2021 22:38, Michael Kelley wrote: > > > While the driver for the Hyper-V Reference TSC and STIMERs is architecture > > > neutral, vDSO is implemented for x

RE: [PATCH v3 07/10] clocksource/drivers/hyper-v: Handle vDSO differences inline

From: Daniel Lezcano Sent: Tuesday, March 2, 2021 2:14 PM > > On 02/03/2021 22:38, Michael Kelley wrote: > > While the driver for the Hyper-V Reference TSC and STIMERs is architecture > > neutral, vDSO is implemented for x86/x64, but not for ARM64. Current code > > calls into utility functions

Re: [PATCH v3 07/10] clocksource/drivers/hyper-v: Handle vDSO differences inline

On 02/03/2021 22:38, Michael Kelley wrote: > While the driver for the Hyper-V Reference TSC and STIMERs is architecture > neutral, vDSO is implemented for x86/x64, but not for ARM64. Current code > calls into utility functions under arch/x86 (and coming, under arch/arm64) > to handle the differenc

[PATCH v3 07/10] clocksource/drivers/hyper-v: Handle vDSO differences inline

While the driver for the Hyper-V Reference TSC and STIMERs is architecture neutral, vDSO is implemented for x86/x64, but not for ARM64. Current code calls into utility functions under arch/x86 (and coming, under arch/arm64) to handle the difference. Change this approach to handle the difference i