Re: [PATCH v2 0/6] arm/arm64: Allow the rescheduling IPI to bypass irq_enter/exit

Hi Marc, Mark > Mark is working on this, I believe. I'll let him comment on the current > state of things. I understand. Mark, Could you tell me current state? Thanks, Yuichi Ito

Re: [PATCH v2 0/6] arm/arm64: Allow the rescheduling IPI to bypass irq_enter/exit

On 2021-03-01 00:39, ito-yui...@fujitsu.com wrote: Hi Marc, I plan to add NMI patches which enables IPI_CPU_CRASH_STOP IPI as pseudo-NMI[1]. But I know need to resolve the instrumentation issues before that. I think need to moving arm64 entry code over to the generic entry

RE: [PATCH v2 0/6] arm/arm64: Allow the rescheduling IPI to bypass irq_enter/exit

Hi Marc, I plan to add NMI patches which enables IPI_CPU_CRASH_STOP IPI as pseudo-NMI[1]. But I know need to resolve the instrumentation issues before that. I think need to moving arm64 entry code over to the generic entry code(kernel/entry/common.c) for that, is this right? Can you tell me

[PATCH v2 0/6] arm/arm64: Allow the rescheduling IPI to bypass irq_enter/exit

This is the second version of my earlier series [1], which aims at fixing (or papering over, depending on how you look at things) a performance regression seen on arm64 for reched IPI heavy workloads (such as "perf bench sched pipe"). As eloquently described by Thomas in his earlier replies [2],