From: Mark Brown <broonie@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] arm64/sme: Fixes for SME only support
Date: Thu, 5 Jan 2023 15:47:07 +0000 [thread overview]
Message-ID: <Y7bw+8ogv2m0pd5a@sirena.org.uk> (raw)
In-Reply-To: <20230105152228.GA3864@willie-the-truck>
[-- Attachment #1.1: Type: text/plain, Size: 947 bytes --]
On Thu, Jan 05, 2023 at 03:22:29PM +0000, Will Deacon wrote:
> On Tue, Dec 27, 2022 at 05:12:04PM +0000, Mark Brown wrote:
> > There is no architectural requirement for systems implementing SME to
> > also implement SVE, though it is expected to be an unusual configuration.
> How unusual? If people aren't practically going to build this, I think
> we'd be better off keeping the code simple and not supporting SME unless
> SVE is also present.
I can't comment on anyone's roadmaps, but this is a configuration I've
been asked about by other people rather than just something I thought of
myself so it has been considered and I can see why someone might think
about implementing such a system. Given that the changes are just
adding system_supports_sme() to existing configuration checks so that we
go through code paths that are already being exercised anyway I think
it's sufficiently non-invasive to justify the cost of handling the case.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2023-01-05 23:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 17:12 [PATCH 0/3] arm64/sme: Fixes for SME only support Mark Brown
2022-12-27 17:12 ` [PATCH 1/3] arm64/sme: Fix context switch for SME only systems Mark Brown
2022-12-27 17:12 ` [PATCH 2/3] arm64/signal: Always accept SVE signal frames on " Mark Brown
2022-12-27 17:12 ` [PATCH 3/3] arm64/signal: Always allocate " Mark Brown
2023-01-05 15:22 ` [PATCH 0/3] arm64/sme: Fixes for SME only support Will Deacon
2023-01-05 15:29 ` Will Deacon
2023-01-05 16:00 ` Mark Brown
2023-01-05 15:47 ` Mark Brown [this message]
2023-01-05 18:03 ` Will Deacon
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=Y7bw+8ogv2m0pd5a@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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.