From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Fuad Tabba <tabba@google.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev
Subject: Re: [PATCH v2 1/4] arm64/fpsimd: Introduce __bit_to_vl() helper
Date: Thu, 4 Jul 2024 15:17:39 +0100 [thread overview]
Message-ID: <ZoavA2rMK2P4qTDm@arm.com> (raw)
In-Reply-To: <20240606-kvm-arm64-fix-pkvm-sve-vl-v2-1-c88f4eb4b14b@kernel.org>
On Thu, Jun 06, 2024 at 04:21:43PM +0100, Mark Brown wrote:
> In all cases where we use the existing __bit_to_vq() helper we immediately
> convert the result into a VL. Provide and use __bit_to_vl() doing this
> directly.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2024-07-04 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 15:21 [PATCH v2 0/4] KVM: arm64: Fix underallocation of storage for SVE state Mark Brown
2024-06-06 15:21 ` [PATCH v2 1/4] arm64/fpsimd: Introduce __bit_to_vl() helper Mark Brown
2024-07-04 14:17 ` Catalin Marinas [this message]
2024-06-06 15:21 ` [PATCH v2 2/4] arm64/fpsimd: Discover maximum vector length implemented by any CPU Mark Brown
2024-06-07 7:33 ` Fuad Tabba
2024-07-04 14:18 ` Catalin Marinas
2024-07-04 15:12 ` Mark Brown
2024-06-06 15:21 ` [PATCH v2 3/4] KVM: arm64: Fix FFR offset calculation for pKVM host state save and restore Mark Brown
2024-06-06 15:21 ` [PATCH v2 4/4] KVM: arm64: Avoid underallocating storage for host SVE state Mark Brown
2024-07-04 14:20 ` [PATCH v2 0/4] KVM: arm64: Fix underallocation of storage for " 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=ZoavA2rMK2P4qTDm@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).