[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cfa31e7c-83c4-0e16-ff7d-c6d6f0160e98@redhat.com>
Date: Wed, 16 Oct 2019 00:35:20 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Thomas Gleixner <tglx@...utronix.de>,
Jianyong Wu <jianyong.wu@....com>
Cc: netdev@...r.kernel.org, yangbo.lu@....com, john.stultz@...aro.org,
sean.j.christopherson@...el.com, maz@...nel.org,
richardcochran@...il.com, Mark.Rutland@....com, will@...nel.org,
suzuki.poulose@....com, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu,
kvm@...r.kernel.org, Steve.Capper@....com, Kaly.Xin@....com,
justin.he@....com, nd@....com
Subject: Re: [PATCH v5 3/6] timekeeping: Add clocksource to
system_time_snapshot
On 15/10/19 22:12, Thomas Gleixner wrote:
> @@ -91,6 +96,7 @@ struct clocksource {
> const char *name;
> struct list_head list;
> int rating;
> + enum clocksource_ids id;
Why add a global id? ARM can add it to archdata similar to how x86 has
vclock_mode. But I still think the right thing to do is to include the
full system_counterval_t in the result of ktime_get_snapshot. (More in
a second, feel free to reply to the other email only).
Paolo
Powered by blists - more mailing lists