mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: Stephen Boyd <sboyd@kernel.org>,
	John Stultz <john.stultz@linaro.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] time: validate watchdog clocksource using second best candidate
Date: Sun, 19 May 2019 17:55:31 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1905191753300.3019@nanos.tec.linutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1905182023520.3019@nanos.tec.linutronix.de>

On Sat, 18 May 2019, Thomas Gleixner wrote:
> On Sat, 18 May 2019, Konstantin Khlebnikov wrote:
> > If there is no second clocksource my patch does noting:
> > watchdog_backup stays NULL and backup_consent always true.
> 
> That still does not justify the extra complexity for a few custom built
> systems.

Aside of that this leaves the HPET in a half broken state. HPET is not only
used as a clock event device it's also exposed by HPET device. So no, if we
figure out that HPET is broken on some platforms we have to blacklist and
disable it completely and not just duct tape the place which exposes the
wreckage.

Thanks,

	tglx

  reply	other threads:[~2019-05-19 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15  7:47 Konstantin Khlebnikov
2019-05-18 15:17 ` Thomas Gleixner
2019-05-18 17:53   ` Konstantin Khlebnikov
2019-05-18 18:26     ` Thomas Gleixner
2019-05-19 15:55       ` Thomas Gleixner [this message]
2019-05-20 15:04       ` Konstantin Khlebnikov
2019-10-23 10:18         ` Konstantin Khlebnikov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1905191753300.3019@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=john.stultz@linaro.org \
    --cc=khlebnikov@yandex-team.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®