[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e98d244f-1257-ed23-26f4-8909900590b4@suse.com>
Date: Thu, 10 Jan 2019 17:14:53 +0100
From: Juergen Gross <jgross@...e.com>
To: Boris Ostrovsky <boris.ostrovsky@...cle.com>,
linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
x86@...nel.org
Cc: sstabellini@...nel.org, hpa@...or.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, hans@...rrie.org,
stable@...r.kernel.org
Subject: Re: [PATCH] xen: Fix x86 sched_clock() interface for xen
On 10/01/2019 16:34, Boris Ostrovsky wrote:
> On 1/10/19 5:07 AM, Juergen Gross wrote:
>>
>> +void xen_clocksource_suspend(void)
>> +{
>> + xen_clock_value_saved = xen_clocksource_read() - xen_sched_clock_offset;
>
>
> xen_clock_value_saved = xen_sched_clock() maybe?
I wanted xen_clocksource_suspend() and xen_clocksource_resume() to
be symmetrical to each other.
In case you are feeling strong about that, I'm not. :-) So in case
you insist on it I can change it. Or you can do so while committing.
Juergen
Powered by blists - more mailing lists