[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e5fb440-156d-2b18-b3cd-89b1a09b0239@huawei.com>
Date: Sat, 17 Apr 2021 17:27:11 +0800
From: Zenghui Yu <yuzenghui@...wei.com>
To: Marc Zyngier <maz@...nel.org>
CC: <netdev@...r.kernel.org>, <yangbo.lu@....com>,
<john.stultz@...aro.org>, <tglx@...utronix.de>,
<pbonzini@...hat.com>, <seanjc@...gle.com>,
<richardcochran@...il.com>, <Mark.Rutland@....com>,
<will@...nel.org>, <suzuki.poulose@....com>,
<Andre.Przywara@....com>, <steven.price@....com>,
<lorenzo.pieralisi@....com>, <sudeep.holla@....com>,
<justin.he@....com>, <kvm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <kernel-team@...roid.com>,
<kvmarm@...ts.cs.columbia.edu>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v19 4/7] time: Add mechanism to recognize clocksource in
time_get_snapshot
On 2021/3/30 22:54, Marc Zyngier wrote:
> - u64 cycles;
> - ktime_t real;
> - ktime_t raw;
> - unsigned int clock_was_set_seq;
> - u8 cs_was_changed_seq;
> + u64 cycles;
> + ktime_t real;
> + ktime_t raw;
> + enum clocksource_ids cs_id;
nit: worth adding a description for it (on top of the structure)?
> + unsigned int clock_was_set_seq;
> + u8 cs_was_changed_seq;
Powered by blists - more mailing lists