[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <21fbef84-e84c-cdd0-ae1a-856c38a39cf3@suse.com>
Date: Mon, 14 Jan 2019 13:43:00 +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 v2] xen: Fix x86 sched_clock() interface for xen
On 11/01/2019 21:35, Boris Ostrovsky wrote:
> On 1/11/19 7:08 AM, Juergen Gross wrote:
>> @@ -421,6 +424,11 @@ void xen_restore_time_memory_area(void)
>> if (ret != 0)
>> pr_notice("Cannot restore secondary vcpu_time_info (err %d)",
>> ret);
>> +
>> +out:
>> + /* Need pvclock_resume() before using xen_clocksource_read(). */
>> + pvclock_resume();
>
> Do we want to drop it from xen_timer_resume then?
Yes. V3 on its way...
Juergen
Powered by blists - more mailing lists