All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Mark Brown <broonie@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Josh Snyder <josh@code406.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the tip-fixes tree
Date: Wed, 08 Apr 2026 17:21:29 +0200	[thread overview]
Message-ID: <87wlyh32bq.ffs@tglx> (raw)
In-Reply-To: <adZNmIpSOkd6P5c7@sirena.org.uk>

On Wed, Apr 08 2026 at 13:44, Mark Brown wrote:

It's a boot not a build fail, right?

> After merging the tip-fixes tree, today's linux-next build (arm64 kunit)
> failed like this:
> which isn't super helpful.  I haven't isolated which commit but it'll be
> one of the three:
>
>   b81207470caf ("clockevents: Prevent timer interrupt starvation")
>   82b915051d32 ("tick/nohz: Fix inverted return value in check_tick_dependency() fast path")
>   105c42566a55 ("ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585")

Found it with qemu and pushed out an updated version. Delta patch
below. It restores the behaviour for !force and delta <= 0 which is
required under certain circumstances to get through the tick_periodic()
boot stage.

Thanks,

        tglx
---
--- a/kernel/time/clockevents.c
+++ b/kernel/time/clockevents.c
@@ -324,6 +324,8 @@ int clockevents_program_event(struct clo
 		return dev->set_next_ktime(expires, dev);
 
 	delta = ktime_to_ns(ktime_sub(expires, ktime_get()));
+	if (delta <= 0 && !force)
+		return -ETIME;
 
 	if (delta > (int64_t)dev->min_delta_ns) {
 		delta = min(delta, (int64_t) dev->max_delta_ns);

  parent reply	other threads:[~2026-04-08 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 12:44 linux-next: build failure after merge of the tip-fixes tree Mark Brown
2026-04-08 14:50 ` Mark Brown
2026-04-08 14:54   ` Thomas Weißschuh
2026-04-08 15:21 ` Thomas Gleixner [this message]
2026-04-08 15:45   ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2025-03-25 23:38 Stephen Rothwell
2025-03-26  1:12 ` Josh Poimboeuf

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=87wlyh32bq.ffs@tglx \
    --to=tglx@kernel.org \
    --cc=broonie@kernel.org \
    --cc=hpa@zytor.com \
    --cc=josh@code406.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.