lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18875bd7-bf01-4ba8-b38a-4c0767e3130e@linux.alibaba.com>
Date: Fri, 11 Apr 2025 11:32:45 +0800
From: Shuai Xue <xueshuai@...ux.alibaba.com>
To: Ankur Arora <ankur.a.arora@...cle.com>, linux-pm@...r.kernel.org,
 kvm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Cc: catalin.marinas@....com, will@...nel.org, x86@...nel.org,
 pbonzini@...hat.com, vkuznets@...hat.com, rafael@...nel.org,
 daniel.lezcano@...aro.org, peterz@...radead.org, arnd@...db.de,
 lenb@...nel.org, mark.rutland@....com, harisokn@...zon.com,
 mtosatti@...hat.com, sudeep.holla@....com, cl@...two.org, maz@...nel.org,
 misono.tomohiro@...itsu.com, maobibo@...ngson.cn, zhenglifeng1@...wei.com,
 joao.m.martins@...cle.com, boris.ostrovsky@...cle.com, konrad.wilk@...cle.com
Subject: Re: [PATCH v10 10/11] arm64: idle: export arch_cpu_idle()



在 2025/2/19 05:33, Ankur Arora 写道:
> Needed for cpuidle-haltpoll.
> 
> Acked-by: Will Deacon <will@...nel.org>
> Signed-off-by: Ankur Arora <ankur.a.arora@...cle.com>
> ---
>   arch/arm64/kernel/idle.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/kernel/idle.c b/arch/arm64/kernel/idle.c
> index 05cfb347ec26..b85ba0df9b02 100644
> --- a/arch/arm64/kernel/idle.c
> +++ b/arch/arm64/kernel/idle.c
> @@ -43,3 +43,4 @@ void __cpuidle arch_cpu_idle(void)
>   	 */
>   	cpu_do_idle();

Hi, Ankur,

With haltpoll_driver registered, arch_cpu_idle() on x86 can select
mwait_idle() in idle threads.

It use MONITOR sets up an effective address range that is monitored
for write-to-memory activities; MWAIT places the processor in
an optimized state (this may vary between different implementations)
until a write to the monitored address range occurs.

Should arch_cpu_idle() on arm64 also use the LDXR/WFE
to avoid wakeup IPI like x86 monitor/mwait?

Thanks.
Shuai



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ