From: Oleg Nesterov <oleg@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, "Eric W. Biederman" <ebiederm@xmission.com>,
Frederic Weisbecker <frederic@kernel.org>,
John Stultz <john.stultz@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [patch V3 0/3] posix-cpu-timers: Move expiry into task work context
Date: Fri, 31 Jul 2020 14:39:13 +0200 [thread overview]
Message-ID: <20200731123912.GA13775@redhat.com> (raw)
In-Reply-To: <20200730101404.956367860@linutronix.de>
On 07/30, Thomas Gleixner wrote:
>
> arch/x86/Kconfig | 1
> include/linux/posix-timers.h | 17 +++
> include/linux/sched.h | 4
> include/linux/seccomp.h | 3
> kernel/entry/common.c | 4
> kernel/time/Kconfig | 9 +
> kernel/time/posix-cpu-timers.c | 216 ++++++++++++++++++++++++++++++++++++-----
> kernel/time/timer.c | 1
> 8 files changed, 227 insertions(+), 28 deletions(-)
FWIW,
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
next prev parent reply other threads:[~2020-07-31 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 10:14 [patch V3 0/3] posix-cpu-timers: Move expiry into task work context Thomas Gleixner
2020-07-30 10:14 ` [patch V3 1/3] posix-cpu-timers: Split run_posix_cpu_timers() Thomas Gleixner
2020-08-06 17:09 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2020-07-30 10:14 ` [patch V3 2/3] posix-cpu-timers: Provide mechanisms to defer timer handling to task_work Thomas Gleixner
2020-08-06 17:09 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2020-07-30 10:14 ` [patch V3 3/3] x86: Select POSIX_CPU_TIMERS_TASK_WORK Thomas Gleixner
2020-08-06 17:09 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2020-07-31 12:39 ` Oleg Nesterov [this message]
2020-08-04 13:20 ` [patch V3 0/3] posix-cpu-timers: Move expiry into task work context peterz
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=20200731123912.GA13775@redhat.com \
--to=oleg@redhat.com \
--cc=ebiederm@xmission.com \
--cc=frederic@kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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