On 7/2/20, 2:08 PM, "Josh Hunt" wrote:
>
> On 7/2/20 2:45 AM, Paolo Abeni wrote:
> > Hi all,
> >
> > On Thu, 2020-07-02 at 08:14 +0200, Jonas Bonn wrote:
> >> Hi Cong,
> >>
> >> On 01/07/2020 21:58, Cong Wang wrote:
> >>> On Wed, Jul 1, 2020 at 9:05 AM Cong Wang wrote:
> On Tue, Jun 30, 202
On 10/18/19, 2:41 PM, "Thomas Gleixner" wrote:
> On Wed, 2 Oct 2019, Michael Zhivich wrote:
> > Introduction of clocksource_tsc_early broke functionality of "tsc=reliable"
> > and "tsc=nowatchdog" boot params, since clocksource_tsc_early is *always*
> > registered with CLOCK_SOURCE_MUST_VERIFY an
On 11/28/18, 10:22 AM, "Thomas Gleixner" wrote:
Michael,
On Fri, 16 Nov 2018, Zhivich, Michael wrote:
> On 11/15/18, 12:17 PM, "John Stultz" wrote:
> Would a more focused fix be to move the clocksource watchdog from a
>
On 11/15/18, 12:17 PM, "John Stultz" wrote:
On Thu, Nov 15, 2018 at 9:07 AM, Michael Zhivich
wrote:
> Require TIMER_SOFTIRQ to be handled immediately instead of delaying until
> ksoftirqd runs, thus preventing problems with reading clocksources that
> wrap often (e.g. acpi_pm).
On 11/12/18, 5:23 PM, "John Stultz" wrote:
On Mon, Nov 12, 2018 at 10:56 AM, Michael Zhivich
wrote:
> Revert commit 1f45f1f33c8c ("clocksource: Make clocksource validation work
> for all clocksources") to restore correct clocksource_delta() computation
> for clocksources that wr
5 matches
Mail list logo