From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: David Vernet <void@manifault.com>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
jpoimboe@redhat.com, pmladek@suse.com, jikos@kernel.org,
mbenes@suse.cz, joe.lawrence@redhat.com,
linux-modules@vger.kernel.org, mcgrof@kernel.org,
jeyu@kernel.org, bpf@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] livepatch: Avoid CPU hogging with cond_resched
Date: Sat, 1 Jan 2022 04:35:50 +0530 [thread overview]
Message-ID: <20211231230550.t2wjz5g5ancrqx7d@apollo.legion> (raw)
In-Reply-To: <Yc0yskk0m2bePLu6@dev0025.ash9.facebook.com>
On Thu, Dec 30, 2021 at 09:46:50AM IST, David Vernet wrote:
> Adding modules + BPF list and maintainers to this thread.
>
Thanks for the Cc, but I'm dropping my patch for the next revision, so there
should be no conflicts with this one.
> [...]
--
Kartikeya
next prev parent reply other threads:[~2021-12-31 23:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 4:16 [PATCH] livepatch: Avoid CPU hogging with cond_resched David Vernet
2021-12-31 23:05 ` Kumar Kartikeya Dwivedi [this message]
2022-01-03 16:04 ` Petr Mladek
2022-01-10 14:38 ` David Vernet
-- strict thread matches above, loose matches on Subject: below --
2021-12-29 21:56 David Vernet
2022-01-05 10:17 ` Miroslav Benes
2022-01-07 0:21 ` Song Liu
2022-01-07 8:17 ` Petr Mladek
2022-01-10 14:55 ` David Vernet
2022-01-07 13:03 ` Petr Mladek
2022-01-07 14:13 ` Joe Lawrence
2022-01-07 16:46 ` Song Liu
2022-01-10 16:16 ` Joe Lawrence
2022-01-11 1:49 ` Song Liu
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=20211231230550.t2wjz5g5ancrqx7d@apollo.legion \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=songliubraving@fb.com \
--cc=void@manifault.com \
--cc=yhs@fb.com \
/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).