linux-kernel - timer_create affinity

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKP5S=3NMzfEDdLsd6_FCNTH6o7_Qz2D6qFwx1WOdc-x2Xi0rA@mail.gmail.com>
Date:   Thu, 25 May 2017 17:57:03 +0300
From:   Nicolae Rosia <nicolae.rosia.oss@...il.com>
To:     linux-rt-users@...r.kernel.org
Cc:     linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: timer_create affinity

Hello,

I'm working on a real-time application using POSIX timers running on a
QorIQ PowerPC platform with a 4.1 PREEMPT RT kernel and I'm trying to
understand whether the following can happen:
1. A thread with a core affinity #0 creates a timer which will invoke
a callback.
2. The kernel will setup the timer using a local timer running on a
different core, core #1
3. The ISR will fire, and could be dispatched by core #2
4. The scheduler will run the callback on core #3.

Is there a way to make sure this whole chain will be executed on a
single core, the core of the caller?

Best regards,
Nicolae Rosia