[GIT pull] irq/urgent for v5.9-rc1

[GIT pull] irq/urgent for v5.9-rc1

[Thomas Gleixner]

Linus,

please pull the latest irq/urgent branch from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-2020-08-14

up to:  f107cee94ba4: genirq: Unlock irq descriptor after errors

Two fixes in the core interrupt code which ensure that all error exits
unlock the descriptor lock.

Thanks,

	tglx

------------------>
Guenter Roeck (2):
      genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq()
      genirq: Unlock irq descriptor after errors

[GIT pull] timers/core for v5.9-rc1

[Thomas Gleixner]

Linus,

please pull the latest timers/core branch from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-core-2020-08-14

up to:  0099808553ad: x86: Select POSIX_CPU_TIMERS_TASK_WORK

A set of posix CPU timer changes which allows to defer the heavy work of
posix CPU timers into task work context. The tick interrupt is reduced to a
quick check which queues the work which is doing the heavy lifting before
returning to user space or going back to guest mode. Moving this out is
deferring the signal delivery slightly but posix CPU timers are inaccurate
by nature as they depend on the tick so there is no real damage. The
relevant test cases all passed.

This lifts the last offender for RT out of the hard interrupt context tick
handler, but it also has the general benefit that the actual heavy work is
accounted to the task/process and not to the tick interrupt itself.

Further optimizations are possible to break long sighand lock hold and
interrupt disabled (on !RT kernels) times when a massive amount of posix
CPU timers (which are unpriviledged) is armed for a task/process.

This is currently only enabled for x86 because the architecture has to
ensure that task work is handled in KVM before entering a guest, which was
just established for x86 with the new common entry/exit code which got
merged post 5.8 and is not the case for other KVM architectures.

Thanks,

	tglx

------------------>
Thomas Gleixner (3):
      posix-cpu-timers: Split run_posix_cpu_timers()
      posix-cpu-timers: Provide mechanisms to defer timer handling to task_work
      x86: Select POSIX_CPU_TIMERS_TASK_WORK

[GIT pull] timers/urgent for v5.9-rc1

[Thomas Gleixner]

Linus,

please pull the latest timers/urgent branch from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-2020-08-14

up to:  b0294f30256b: time: Delete repeated words in comments

A set oftimekeeping/VDSO updates:

 - Preparatory work to allow S390 to switch over to the generic VDSO
   implementation.

   S390 requires that the VDSO data pointer is handed in to the counter
   read function when time namespace support is enabled. Adding the pointer
   is a NOOP for all other architectures because the compiler is supposed
   to optimize that out when it is unused in the architecture specific
   inline. The change also solved a similar problem for MIPS which
   fortunately has time namespaces not yet enabled.

   S390 needs to update clock related VDSO data independent of the
   timekeeping updates. This was solved so far with yet another sequence
   counter in the S390 implementation. A better solution is to utilize the
   already existing VDSO sequence count for this. The core code now exposes
   helper functions which allow to serialize against the timekeeper code
   and against concurrent readers.

   S390 needs extra data for their clock readout function. The initial
   common VDSO data structure did not provide a way to add that. It now has
   an embedded architecture specific struct embedded which defaults to an
   empty struct.

   Doing this now avoids tree dependencies and conflicts post rc1 and
   allows all other architectures which work on generic VDSO support to
   work from a common upstream base.

 - A trivial comment fix.  

Thanks,

	tglx

------------------>
Randy Dunlap (1):
      time: Delete repeated words in comments

Sven Schnelle (1):
      lib/vdso: Allow to add architecture-specific vdso data

Thomas Gleixner (2):
      vdso/treewide: Add vdso_data pointer argument to __arch_get_hw_counter()
      timekeeping/vsyscall: Provide vdso_update_begin/end()

Re: [GIT pull] irq/urgent for v5.9-rc1

[Linus Torvalds]

On Fri, Aug 14, 2020 at 9:00 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> Two fixes in the core interrupt code which ensure that all error exits
> unlock the descriptor lock.

No diffstat?

I've pulled it, but please check what went wrong..

                Linus

Re: [GIT pull] timers/core for v5.9-rc1

[Linus Torvalds]

On Fri, Aug 14, 2020 at 9:00 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> please pull the latest timers/core branch from:

.. again no diffstat. I think you've borked your scripts.

               Linus

Re: [GIT pull] irq/urgent for v5.9-rc1

[pr-tracker-bot]

The pull request you sent on Fri, 14 Aug 2020 15:58:31 -0000:

> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-2020-08-14

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1d229a65b419cf51a9921d73907f1998a0e14daa

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

Re: [GIT pull] timers/core for v5.9-rc1

[pr-tracker-bot]

The pull request you sent on Fri, 14 Aug 2020 15:58:33 -0000:

> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-core-2020-08-14

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b6b178e38f40f34842b719a8786d346d4cfec5dc

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

Re: [GIT pull] timers/urgent for v5.9-rc1

[pr-tracker-bot]

The pull request you sent on Fri, 14 Aug 2020 15:58:34 -0000:

> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-2020-08-14

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b923f1247b72fc100b87792fd2129d026bb10e66

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

Re: [GIT pull] irq/urgent for v5.9-rc1

[Thomas Gleixner]

On Fri, Aug 14 2020 at 14:14, Linus Torvalds wrote:
> On Fri, Aug 14, 2020 at 9:00 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>>
>> Two fixes in the core interrupt code which ensure that all error exits
>> unlock the descriptor lock.
>
> No diffstat?
>
> I've pulled it, but please check what went wrong..

Duh, incomplete restore of environment after replacing the worn out
SSD. Fixed.

Thanks,

        tglx