From: Peter Zijlstra <peterz@infradead.org>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Seth Forshee <sforshee@digitalocean.com>,
Song Liu <song@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Miroslav Benes <mbenes@suse.cz>, Jiri Kosina <jikos@kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH 0/3] livepatch,sched: Add livepatch task switching to cond_resched()
Date: Tue, 14 Feb 2023 13:08:22 +0100 [thread overview]
Message-ID: <Y+t5tmbmKaUwNzdJ@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <cover.1675969869.git.jpoimboe@kernel.org>
On Thu, Feb 09, 2023 at 11:17:46AM -0800, Josh Poimboeuf wrote:
> Fix patching stalls caused by busy kthreads.
>
> Josh Poimboeuf (3):
> livepatch: Skip task_call_func() for current task
> livepatch,sched: Add livepatch task switching to cond_resched()
> vhost: Fix livepatch timeouts in vhost_worker()
Seems reasonable, you want me to take them through the sched tree?
next prev parent reply other threads:[~2023-02-14 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 19:17 [PATCH 0/3] livepatch,sched: Add livepatch task switching to cond_resched() Josh Poimboeuf
2023-02-09 19:17 ` [PATCH 1/3] livepatch: Skip task_call_func() for current task Josh Poimboeuf
2023-02-15 9:56 ` Petr Mladek
2023-02-09 19:17 ` [PATCH 2/3] livepatch,sched: Add livepatch task switching to cond_resched() Josh Poimboeuf
2023-02-15 13:30 ` Petr Mladek
2023-02-16 2:26 ` Josh Poimboeuf
2023-02-17 9:14 ` Petr Mladek
2023-02-09 19:17 ` [PATCH 3/3] vhost: Fix livepatch timeouts in vhost_worker() Josh Poimboeuf
2023-02-15 13:31 ` Petr Mladek
2023-02-10 21:08 ` [PATCH 0/3] livepatch,sched: Add livepatch task switching to cond_resched() Seth Forshee
2023-02-14 12:08 ` Peter Zijlstra [this message]
2023-02-14 19:05 ` 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=Y+t5tmbmKaUwNzdJ@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=pmladek@suse.com \
--cc=sforshee@digitalocean.com \
--cc=song@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;
as well as URLs for NNTP newsgroup(s).