On Mon, 26 Aug 2019, Vitaly Kuznetsov wrote:
> Sasha Levin writes:
>
> > On Thu, Aug 22, 2019 at 10:39:46AM +0200, Vitaly Kuznetsov wrote:
> >>lantianyu1...@gmail.com writes:
> >>
> >>> From: Tianyu Lan
> >>>
> >>> Both Hyper-V tsc page and Hyper-V tsc MSR code use variable
> >>>
Sasha Levin writes:
> On Thu, Aug 22, 2019 at 10:39:46AM +0200, Vitaly Kuznetsov wrote:
>>lantianyu1...@gmail.com writes:
>>
>>> From: Tianyu Lan
>>>
>>> Both Hyper-V tsc page and Hyper-V tsc MSR code use variable
>>> hv_sched_clock_offset for their sched clock callback and so
>>> define the
On Sun, Aug 25, 2019 at 1:52 AM Sasha Levin wrote:
>
> On Thu, Aug 22, 2019 at 10:39:46AM +0200, Vitaly Kuznetsov wrote:
> >lantianyu1...@gmail.com writes:
> >
> >> From: Tianyu Lan
> >>
> >> Both Hyper-V tsc page and Hyper-V tsc MSR code use variable
> >> hv_sched_clock_offset for their sched
On Thu, Aug 22, 2019 at 10:39:46AM +0200, Vitaly Kuznetsov wrote:
lantianyu1...@gmail.com writes:
From: Tianyu Lan
Both Hyper-V tsc page and Hyper-V tsc MSR code use variable
hv_sched_clock_offset for their sched clock callback and so
define the variable regardless of CONFIG_HYPERV_TSCPAGE
On Thu, Aug 22, 2019 at 4:39 PM Vitaly Kuznetsov wrote:
>
> lantianyu1...@gmail.com writes:
>
> > From: Tianyu Lan
> >
> > Both Hyper-V tsc page and Hyper-V tsc MSR code use variable
> > hv_sched_clock_offset for their sched clock callback and so
> > define the variable regardless of
lantianyu1...@gmail.com writes:
> From: Tianyu Lan
>
> Both Hyper-V tsc page and Hyper-V tsc MSR code use variable
> hv_sched_clock_offset for their sched clock callback and so
> define the variable regardless of CONFIG_HYPERV_TSCPAGE setting.
CONFIG_HYPERV_TSCPAGE is gone after my
From: Tianyu Lan
Both Hyper-V tsc page and Hyper-V tsc MSR code use variable
hv_sched_clock_offset for their sched clock callback and so
define the variable regardless of CONFIG_HYPERV_TSCPAGE setting.
Signed-off-by: Tianyu Lan
---
This patch is based on the top of
7 matches
Mail list logo