[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+khW7h2DWPM4nAOav+t8k+zbnUOkCO9C+47bSVN0UMHRE-v_w@mail.gmail.com>
Date: Thu, 30 Jun 2022 13:43:09 -0700
From: Hao Luo <haoluo@...gle.com>
To: Yafang Shao <laoar.shao@...il.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
kafai@...com, songliubraving@...com, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org,
quentin@...valent.com, netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [PATCH bpf-next 3/4] bpf: Don't do preempt check when migrate is disabled
Hi Yafang,
On Wed, Jun 29, 2022 at 8:49 AM Yafang Shao <laoar.shao@...il.com> wrote:
>
> It doesn't need to do the preempt check when migrate is disabled
> after commit
> 74d862b682f5 ("sched: Make migrate_disable/enable() independent of RT").
>
> Signed-off-by: Yafang Shao <laoar.shao@...il.com>
> ---
In my understanding, migrate_disable() doesn't imply
preempt_disable(), I think this is not safe. Am I missing something?
Hao
Powered by blists - more mailing lists