All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Alexander Stein <alexander.stein@ew.tq-group.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v4 2/8] timers/migration: Move hierarchy setup into cpuhotplug prepare callback
Date: Mon, 15 Jul 2024 12:44:29 +0200	[thread overview]
Message-ID: <ZpT9jSNcCLnEScWL@localhost.localdomain> (raw)
In-Reply-To: <4f24a2f1-0f6a-4ad4-97e3-398cd9981127@nvidia.com>

Hi,

Le Mon, Jul 15, 2024 at 11:39:40AM +0100, Jon Hunter a écrit :
> 
> On 11/07/2024 09:56, Alexander Stein wrote:
> > Hi,
> > 
> > Am Mittwoch, 3. Juli 2024, 22:28:39 CEST schrieb Anna-Maria Behnsen:
> > > When a CPU comes online the first time, it is possible that a new top level
> > > group will be created. In general all propagation is done from the bottom
> > > to top. This minimizes complexity and prevents possible races. But when a
> > > new top level group is created, the formely top level group needs to be
> > > connected to the new level. This is the only time, when the direction to
> > > propagate changes is changed: the changes are propagated from top (new top
> > > level group) to bottom (formerly top level group).
> > 
> > Now that this commit is integrated in linux-next I'm starting to see the
> > kernel error message:
> > > Timer migration setup failed
> > on my arm64 i.MX8MP platform (imx8mp-tqma8mpql-mba8mpxl.dts).
> 
> 
> I am also seeing the same on our 32-bit and 64-bit ARM Tegra boards.
> 
> Any feedback on this?

The patches have been reverted on -tip (still in -next?) and Anna-Maria is
working on a new version.

Thanks!



> 
> Thanks
> Jon
> 
> -- 
> nvpublic

  reply	other threads:[~2024-07-15 10:44 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 10:18 [PATCH v3 0/8] timers/migration: Fix three possible races and some improvements Anna-Maria Behnsen
2024-07-01 10:18 ` [PATCH v3 1/8] timers/migration: Do not rely always on group->parent Anna-Maria Behnsen
2024-07-04 18:32   ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 10:18 ` [PATCH v3 2/8] timers/migration: Move hierarchy setup into cpuhotplug prepare callback Anna-Maria Behnsen
2024-07-01 21:49   ` Frederic Weisbecker
2024-07-03 20:28   ` [PATCH v4 " Anna-Maria Behnsen
2024-07-03 21:24     ` Frederic Weisbecker
2024-07-04 18:32     ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-11  8:56     ` [PATCH v4 2/8] " Alexander Stein
2024-07-15 10:39       ` Jon Hunter
2024-07-15 10:44         ` Frederic Weisbecker [this message]
2024-07-15 13:25           ` Jon Hunter
2024-07-01 10:18 ` [PATCH v3 3/8] timers/migration: Improve tracing Anna-Maria Behnsen
2024-07-04 18:32   ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 10:18 ` [PATCH v3 4/8] timers/migration: Use a single struct for hierarchy walk data Anna-Maria Behnsen
2024-07-02 11:43   ` Frederic Weisbecker
2024-07-04 18:32   ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 10:18 ` [PATCH v3 5/8] timers/migration: Read childmask and parent pointer in a single place Anna-Maria Behnsen
2024-07-02 12:04   ` Frederic Weisbecker
2024-07-04 18:32   ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-15 19:28   ` [PATCH v3 5/8] " Frederic Weisbecker
2024-07-01 10:18 ` [PATCH v3 6/8] timers/migration: Rename childmask by parentmask to make naming more obvious Anna-Maria Behnsen
2024-07-02 12:45   ` Frederic Weisbecker
2024-07-03 20:31   ` [PATCH v4 6/8] timers/migration: Rename childmask by groupmask " Anna-Maria Behnsen
2024-07-03 21:33     ` Frederic Weisbecker
2024-07-04 18:32     ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 10:18 ` [PATCH v3 7/8] timers/migration: Spare write when nothing changed Anna-Maria Behnsen
2024-07-04 18:32   ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 10:18 ` [PATCH v3 8/8] timers/migration: Fix grammar in comment Anna-Maria Behnsen
2024-07-02 12:51   ` Frederic Weisbecker
2024-07-04 18:32   ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-11 15:44 ` [PATCH v3 0/8] timers/migration: Fix three possible races and some improvements Anna-Maria Behnsen
  -- strict thread matches above, loose matches on Subject: below --
2024-07-16 14:19 [PATCH v4 " Anna-Maria Behnsen
2024-07-16 14:19 ` [PATCH v4 2/8] timers/migration: Move hierarchy setup into cpuhotplug prepare callback Anna-Maria Behnsen
2024-07-16 23:01   ` Frederic Weisbecker

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=ZpT9jSNcCLnEScWL@localhost.localdomain \
    --to=frederic@kernel.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=anna-maria@linutronix.de \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.