From: Catalin Marinas <catalin.marinas@arm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Peter Collingbourne <pcc@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Will Deacon <will@kernel.org>,
Evgenii Stepanov <eugenis@google.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Tejas Belagod <Tejas.Belagod@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v11 5/5] Documentation: document the preferred tag checking mode feature
Date: Wed, 28 Jul 2021 18:38:46 +0100 [thread overview]
Message-ID: <20210728173845.GE7408@arm.com> (raw)
In-Reply-To: <YQD09Oqbn7D1MniP@kroah.com>
On Wed, Jul 28, 2021 at 08:11:00AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Jul 27, 2021 at 01:52:59PM -0700, Peter Collingbourne wrote:
> > diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
> > index 160b10c029c0..5f87b146deb9 100644
> > --- a/Documentation/ABI/testing/sysfs-devices-system-cpu
> > +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
> > @@ -640,3 +640,21 @@ Description: SPURR ticks for cpuX when it was idle.
> >
> > This sysfs interface exposes the number of SPURR ticks
> > for cpuX when it was idle.
> > +
> > +What: /sys/devices/system/cpu/cpuX/mte_tcf_preferred
> > +Date: July 2021
> > +Contact: Linux ARM Kernel Mailing list <linux-arm-kernel@lists.infradead.org>
> > +Description: Preferred MTE tag checking mode
> > +
> > + When a user program specifies more than one MTE tag checking
> > + mode, this sysfs node is used to specify which mode should
> > + be preferred when running on that CPU. Possible values:
> > +
> > + ================ ==============================================
> > + "sync" Prefer synchronous mode
> > + "async" Prefer asynchronous mode
> > + ================ ==============================================
> > +
> > + Changes to this sysfs node may not take effect immediately.
>
> Ok, so when do they take effect? A hint would be nice :)
I'll go with Will suggestion below and remove this line altogether (it
takes effect when scheduling a task on a CPU):
https://lore.kernel.org/r/20210714115018.GE31686@willie-the-truck
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-28 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 20:52 [PATCH v11 0/5] arm64: mte: allow async MTE to be upgraded to sync on a per-CPU basis Peter Collingbourne
2021-07-27 20:52 ` [PATCH v11 1/5] arm64: mte: rename gcr_user_excl to mte_ctrl Peter Collingbourne
2021-07-27 20:52 ` [PATCH v11 2/5] arm64: mte: change ASYNC and SYNC TCF settings into bitfields Peter Collingbourne
2021-07-27 20:52 ` [PATCH v11 3/5] arm64: move preemption disablement to prctl handlers Peter Collingbourne
2021-07-27 20:52 ` [PATCH v11 4/5] arm64: mte: introduce a per-CPU tag checking mode preference Peter Collingbourne
2021-07-27 20:52 ` [PATCH v11 5/5] Documentation: document the preferred tag checking mode feature Peter Collingbourne
2021-07-28 6:11 ` Greg Kroah-Hartman
2021-07-28 17:38 ` Catalin Marinas [this message]
2021-07-28 17:46 ` [PATCH v11 0/5] arm64: mte: allow async MTE to be upgraded to sync on a per-CPU basis Catalin Marinas
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=20210728173845.GE7408@arm.com \
--to=catalin.marinas@arm.com \
--cc=Tejas.Belagod@arm.com \
--cc=eugenis@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=pcc@google.com \
--cc=szabolcs.nagy@arm.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.