public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Liao, Chang" <liaochang1@huawei.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: <catalin.marinas@arm.com>, <will@kernel.org>, <maz@kernel.org>,
	<oliver.upton@linux.dev>, <james.morse@arm.com>,
	<suzuki.poulose@arm.com>, <yuzenghui@huawei.com>,
	<tglx@linutronix.de>, <ardb@kernel.org>, <broonie@kernel.org>,
	<anshuman.khandual@arm.com>, <miguel.luis@oracle.com>,
	<joey.gouly@arm.com>, <ryan.roberts@arm.com>,
	<jeremy.linton@arm.com>, <ericchancf@google.com>,
	<kristina.martsenko@arm.com>, <robh@kernel.org>,
	<scott@os.amperecomputing.com>, <songshuaishuai@tinylab.org>,
	<shijie@os.amperecomputing.com>, <akpm@linux-foundation.org>,
	<bhe@redhat.com>, <horms@kernel.org>, <mhiramat@kernel.org>,
	<rmk+kernel@armlinux.org.uk>, <shahuang@redhat.com>,
	<takakura@valinux.co.jp>, <dianders@chromium.org>,
	<swboyd@chromium.org>, <sumit.garg@linaro.org>,
	<frederic@kernel.org>, <reijiw@google.com>,
	<akihiko.odaki@daynix.com>, <ruanjinjie@huawei.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <kvmarm@lists.linux.dev>
Subject: Re: [PATCH v3 0/8] Rework the DAIF mask, unmask and track API
Date: Mon, 6 May 2024 20:12:46 +0800	[thread overview]
Message-ID: <f301ebb0-adf2-33c9-d548-7738a010ce92@huawei.com> (raw)
In-Reply-To: <ZjUadl2Kbv-KyveZ@FVFF77S0Q05N>



在 2024/5/4 1:10, Mark Rutland 写道:
> Hi,
> 
> On Mon, Apr 15, 2024 at 06:47:50AM +0000, Liao Chang wrote:
>> This patch series reworks the DAIF mask, unmask, and track API for the
>> upcoming FEAT_NMI extension added in Armv8.8.
>>
>> As platform and virtualization[1] supports for FEAT_NMI is emerging, and
>> Mark Brown's FEAT_NMI patch series[2] highlighted the need for clean up
>> the existing hacking style approach about DAIF management code before
>> adding NMI functionality, furthermore, we discover some subtle bugs
>> during 'perf' and 'ipi_backtrace' transition from PSEUDO_NMI to
>> FEAT_NMI, in summary, all of these emphasize the importance of rework.
>>
>> This series of reworking patches follows the suggestion from Mark
>> Rutland mentioned in Mark Brown's patchset. In summary, he think the
>> better way for DAIF manangement look likes as following:
>>
>> (a) Adding entry-specific helpers to manipulate abstract exception masks
>>     covering DAIF + PMR + ALLINT. Those need unmask-at-entry and
>>     mask-at-exit behaviour, and today only need to manage DAIF + PMR.
>>
>>     It should be possible to do this ahead of ALLINT / NMI support.
>>
>> (b) Adding new "logical exception mask" helpers that treat DAIF + PMR +
>>     ALLINT as separate elements. 
> 
> I've started looking at this in the series. There are some subtleties here, and
> I don't think the helpers in this series are quite right as-is. I will try to
> get back to you next week with a description of those; it'll take a short while
> to write that up correctly and clearly and I don't trust myself to rush that
> last thing on a Friday.
> 
> Thanks,
> Mark.

Hi,Mark

Thanks for your feedback.I apprecaite your interest in this patch series
and look forward to receiving additional comments from you and others in
the community.

I am pleased to inform you that the FEAT_NMI features has been successfully
merged into the upstream QEMU codebase at the "master" branch recently. This
allow for initial testing without requiring hardware support for FEAT_NMI.

To ensure minimal regressions introduced by this patch series, i have done
testing using perf top, hardlokup and ipi nmi for various configurations,
including (1) no NMI (2) use CONFIG_PSEUDO_NMI (3) use CONFIG_ARM64_NMI.

We encourage further discussion and feedback on the patch series. We are
particularly interested in hearing from developers who might have experience
with NMI handling or those using platforms with FEAT_NMI capabilities.

Thank you.

> 
>>
>> This patches cherry-pick a part of Mark Brown' FEAT_NMI series, in order
>> to pass compilation and basic testing, includes perf and ipi_backtrace.
>>
>> [1] https://lore.kernel.org/all/20240407081733.3231820-1-ruanjinjie@huawei.com/
>> [2] https://lore.kernel.org/linux-arm-kernel/Y4sH5qX5bK9xfEBp@lpieralisi/
>>
>> v3->v2:
>> 1. Squash two commits that address two minor issues into Mark Brown's
>>    origin patch for detecting FEAT_NMI.
>> 2. Add one patch resolves the kprobe reenter panic while testing
>>    FEAT_NMI on QEMU.
>>
>> v2->v1:
>> Add SoB tags following the origin author's SoBs.
>>
>> Liao Chang (5):
>>   arm64: daifflags: Add logical exception masks covering DAIF + PMR +
>>     ALLINT
>>   arm64: Unify exception masking at entry and exit of exception
>>   arm64: Deprecate old local_daif_{mask,save,restore}
>>   irqchip/gic-v3: Improve the maintainability of NMI masking in GIC
>>     driver
>>   arm64: kprobe: Keep NMI maskabled while kprobe is stepping xol
>>
>> Mark Brown (3):
>>   arm64/sysreg: Add definitions for immediate versions of MSR ALLINT
>>   arm64/cpufeature: Detect PE support for FEAT_NMI
>>   arm64/nmi: Add Kconfig for NMI
>>
>>  arch/arm64/Kconfig                   |  17 ++
>>  arch/arm64/include/asm/cpufeature.h  |   6 +
>>  arch/arm64/include/asm/daifflags.h   | 298 ++++++++++++++++++++++-----
>>  arch/arm64/include/asm/nmi.h         |  27 +++
>>  arch/arm64/include/asm/sysreg.h      |   2 +
>>  arch/arm64/include/uapi/asm/ptrace.h |   1 +
>>  arch/arm64/kernel/acpi.c             |  10 +-
>>  arch/arm64/kernel/cpufeature.c       |  58 +++++-
>>  arch/arm64/kernel/debug-monitors.c   |   7 +-
>>  arch/arm64/kernel/entry-common.c     |  96 +++++----
>>  arch/arm64/kernel/entry.S            |   2 -
>>  arch/arm64/kernel/hibernate.c        |   6 +-
>>  arch/arm64/kernel/irq.c              |   2 +-
>>  arch/arm64/kernel/machine_kexec.c    |   2 +-
>>  arch/arm64/kernel/probes/kprobes.c   |   4 +-
>>  arch/arm64/kernel/setup.c            |   2 +-
>>  arch/arm64/kernel/smp.c              |   6 +-
>>  arch/arm64/kernel/suspend.c          |   6 +-
>>  arch/arm64/kvm/hyp/vgic-v3-sr.c      |   6 +-
>>  arch/arm64/kvm/hyp/vhe/switch.c      |   4 +-
>>  arch/arm64/mm/mmu.c                  |   6 +-
>>  arch/arm64/tools/cpucaps             |   2 +
>>  drivers/irqchip/irq-gic-v3.c         |   6 +-
>>  23 files changed, 442 insertions(+), 134 deletions(-)
>>  create mode 100644 arch/arm64/include/asm/nmi.h
>>
>> -- 
>> 2.34.1
>>
>>
> 

-- 
BR
Liao, Chang

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2024-05-06 12:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15  6:47 [PATCH v3 0/8] Rework the DAIF mask, unmask and track API Liao Chang
2024-04-15  6:47 ` [PATCH v3 1/8] arm64/sysreg: Add definitions for immediate versions of MSR ALLINT Liao Chang
2024-05-03 16:00   ` Mark Rutland
2024-05-06 12:12     ` Liao, Chang
2024-05-06 15:15     ` Mark Brown
2024-05-07  7:41       ` Liao, Chang
2024-05-07 14:52         ` Mark Brown
2024-06-03  3:26           ` Liao, Chang
2024-06-04 13:29             ` Mark Brown
2024-06-05  9:52               ` Liao, Chang
2024-06-14  4:00                 ` Liao, Chang
2024-04-15  6:47 ` [PATCH v3 2/8] arm64/cpufeature: Detect PE support for FEAT_NMI Liao Chang
2024-04-15  6:47 ` [PATCH v3 3/8] arm64/nmi: Add Kconfig for NMI Liao Chang
2024-04-15  6:47 ` [PATCH v3 4/8] arm64: daifflags: Add logical exception masks covering DAIF + PMR + ALLINT Liao Chang
2024-04-15  6:47 ` [PATCH v3 5/8] arm64: Unify exception masking at entry and exit of exception Liao Chang
2024-04-15  6:47 ` [PATCH v3 6/8] arm64: Deprecate old local_daif_{mask,save,restore} Liao Chang
2024-04-15  6:47 ` [PATCH v3 7/8] irqchip/gic-v3: Improve the maintainability of NMI masking in GIC driver Liao Chang
2024-04-15  6:47 ` [PATCH v3 8/8] arm64: kprobe: Keep NMI maskabled while kprobe is stepping xol Liao Chang
2024-05-03 17:10 ` [PATCH v3 0/8] Rework the DAIF mask, unmask and track API Mark Rutland
2024-05-06 12:12   ` Liao, Chang [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=f301ebb0-adf2-33c9-d548-7738a010ce92@huawei.com \
    --to=liaochang1@huawei.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=bhe@redhat.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=dianders@chromium.org \
    --cc=ericchancf@google.com \
    --cc=frederic@kernel.org \
    --cc=horms@kernel.org \
    --cc=james.morse@arm.com \
    --cc=jeremy.linton@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kristina.martsenko@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=miguel.luis@oracle.com \
    --cc=oliver.upton@linux.dev \
    --cc=reijiw@google.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=robh@kernel.org \
    --cc=ruanjinjie@huawei.com \
    --cc=ryan.roberts@arm.com \
    --cc=scott@os.amperecomputing.com \
    --cc=shahuang@redhat.com \
    --cc=shijie@os.amperecomputing.com \
    --cc=songshuaishuai@tinylab.org \
    --cc=sumit.garg@linaro.org \
    --cc=suzuki.poulose@arm.com \
    --cc=swboyd@chromium.org \
    --cc=takakura@valinux.co.jp \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.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