Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
	andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com,
	shuah@kernel.org, tglx@linutronix.de
Subject: Re: [PATCH bpf] selftests/bpf: Check for PREEMPTION instead of PREEMPT
Date: Tue, 26 Nov 2024 17:10:29 +0000	[thread overview]
Message-ID: <173264102952.477780.5683459007751613946.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241119161819.qvEcs-n_@linutronix.de>

Hello:

This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue, 19 Nov 2024 17:18:19 +0100 you wrote:
> CONFIG_PREEMPT is a preemtion model the so called "Low-Latency Desktop".
> A different preemption model is PREEMPT_RT the so called "Real-Time".
> Both implement preemption in kernel and set CONFIG_PREEMPTION.
> There is also the so called "LAZY PREEMPT" which the "Scheduler
> controlled preemption model". Here we have also preemption in the kernel
> the rules are slightly different.
> 
> [...]

Here is the summary with links:
  - [bpf] selftests/bpf: Check for PREEMPTION instead of PREEMPT
    https://git.kernel.org/bpf/bpf/c/6b64128a74eb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2024-11-26 17:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 16:18 [PATCH bpf] selftests/bpf: Check for PREEMPTION instead of PREEMPT Sebastian Andrzej Siewior
2024-11-26 17:10 ` patchwork-bot+netdevbpf [this message]

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=173264102952.477780.5683459007751613946.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=bpf@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mykolal@fb.com \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    /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