Hi Paolo, Marc > -----Original Message----- > From: Paolo Bonzini <pbonz...@redhat.com> > Sent: Thursday, September 19, 2019 7:07 PM > To: Jianyong Wu (Arm Technology China) <jianyong...@arm.com>; > net...@vger.kernel.org; yangbo...@nxp.com; john.stu...@linaro.org; > t...@linutronix.de; sean.j.christopher...@intel.com; m...@kernel.org; > richardcoch...@gmail.com; Mark Rutland <mark.rutl...@arm.com>; Will > Deacon <will.dea...@arm.com>; Suzuki Poulose > <suzuki.poul...@arm.com> > Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org; Steve Capper > <steve.cap...@arm.com>; Kaly Xin (Arm Technology China) > <kaly....@arm.com>; Justin He (Arm Technology China) > <justin...@arm.com>; nd <n...@arm.com>; linux-arm- > ker...@lists.infradead.org > Subject: Re: [RFC PATCH v3 4/6] psci: Add hvc call service for ptp_kvm. > > On 19/09/19 11:46, Jianyong Wu (Arm Technology China) wrote: > >> On 18/09/19 11:57, Jianyong Wu (Arm Technology China) wrote: > >>> Paolo Bonzini wrote: > >>>> This is not Y2038-safe. Please use ktime_get_real_ts64 instead, > >>>> and split the 64-bit seconds value between val[0] and val[1]. > > > > Val[] should be long not u32 I think, so in arm64 I can avoid that > > Y2038_safe, but also need rewrite for arm32. > > I don't think there's anything inherently wrong with u32 val[], and as you > notice it lets you reuse code between arm and arm64. It's up to you and > Marc to decide. > To compatible 32-bit, Integrates second value and nanosecond value as a nanosecond value then split it into val[0] and val[1] and split cycle value into val[2] and val[3], In this way, time will overflow at Y2262. WDYT?
Thanks Jianyong Wu
