All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, ardb@kernel.org,
	bertrand.marquis@arm.com, boris.ostrovsky@oracle.com,
	broonie@kernel.org, catalin.marinas@arm.com,
	daniel.lezcano@linaro.org, james.morse@arm.com, jgross@suse.com,
	kristina.martsenko@arm.com, maz@kernel.org, pcc@google.com,
	sstabellini@kernel.org, suzuki.poulose@arm.com,
	tglx@linutronix.de, vladimir.murzin@arm.com, will@kernel.org
Subject: Re: [PATCH v3 09/38] arm64: kvm: Use cpus_have_final_cap() explicitly
Date: Mon, 16 Oct 2023 19:29:18 +0000	[thread overview]
Message-ID: <ZS2PDl0j1_4quiFt@linux.dev> (raw)
In-Reply-To: <20231010103139.3113421-10-mark.rutland@arm.com>

nit: '$ARCH: KVM:' is typically used for KVM guest PV changes, I think
you want 'KVM: arm64'.

But who really cares.

On Tue, Oct 10, 2023 at 11:31:10AM +0100, Mark Rutland wrote:
> Much of the arm64 KVM code uses cpus_have_const_cap() to check for
> cpucaps, but this is unnecessary and it would be preferable to use
> cpus_have_final_cap().

[...]

> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> Reviewed-by: Marc Zyngier <maz@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Oliver Upton <oliver.upton@linux.dev>
> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
> Cc: Will Deacon <will@kernel.org>

Reviewed-by: Oliver Upton <oliver.upton@linux.dev>

-- 
Thanks,
Oliver

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

  reply	other threads:[~2023-10-16 19:30 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 10:31 [PATCH v3 00/38] arm64: Remove cpus_have_const_cap() Mark Rutland
2023-10-10 10:31 ` [PATCH v3 01/38] clocksource/drivers/arm_arch_timer: Initialize evtstrm after finalizing cpucaps Mark Rutland
2023-10-10 10:31 ` [PATCH v3 02/38] arm64/arm: xen: enlighten: Fix KPTI checks Mark Rutland
2023-10-10 10:31 ` [PATCH v3 03/38] arm64: Factor out cpucap definitions Mark Rutland
2023-10-10 10:31 ` [PATCH v3 04/38] arm64: Add cpucap_is_possible() Mark Rutland
2023-10-10 10:31 ` [PATCH v3 05/38] arm64: Add cpus_have_final_boot_cap() Mark Rutland
2023-10-10 10:31 ` [PATCH v3 06/38] arm64: Rework setup_cpu_features() Mark Rutland
2023-10-10 10:31 ` [PATCH v3 07/38] arm64: Fixup user features at boot time Mark Rutland
2023-10-10 10:31 ` [PATCH v3 08/38] arm64: Split kpti_install_ng_mappings() Mark Rutland
2023-10-10 10:31 ` [PATCH v3 09/38] arm64: kvm: Use cpus_have_final_cap() explicitly Mark Rutland
2023-10-16 19:29   ` Oliver Upton [this message]
2023-10-10 10:31 ` [PATCH v3 10/38] arm64: Explicitly save/restore CPACR when probing SVE and SME Mark Rutland
2023-10-10 10:31 ` [PATCH v3 11/38] arm64: Use build-time assertions for cpucap ordering Mark Rutland
2023-10-10 10:31 ` [PATCH v3 12/38] arm64: Rename SVE/SME cpu_enable functions Mark Rutland
2023-10-10 10:31 ` [PATCH v3 13/38] arm64: Use a positive cpucap for FP/SIMD Mark Rutland
2023-10-10 10:31 ` [PATCH v3 14/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_{ADDRESS,GENERIC}_AUTH Mark Rutland
2023-10-10 10:31 ` [PATCH v3 15/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_ARMv8_4_TTL Mark Rutland
2023-10-10 10:31 ` [PATCH v3 16/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_BTI Mark Rutland
2023-10-10 10:31 ` [PATCH v3 17/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_CACHE_DIC Mark Rutland
2023-10-10 10:31 ` [PATCH v3 18/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_CNP Mark Rutland
2023-10-10 10:31 ` [PATCH v3 19/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_DIT Mark Rutland
2023-10-10 10:31 ` [PATCH v3 20/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_GIC_PRIO_MASKING Mark Rutland
2023-10-10 10:31 ` [PATCH v3 21/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_PAN Mark Rutland
2023-10-10 10:31 ` [PATCH v3 22/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_EPAN Mark Rutland
2023-10-10 10:31 ` [PATCH v3 23/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_RNG Mark Rutland
2023-10-10 10:31 ` [PATCH v3 24/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_WFXT Mark Rutland
2023-10-10 10:31 ` [PATCH v3 25/38] arm64: Avoid cpus_have_const_cap() for ARM64_HAS_TLB_RANGE Mark Rutland
2023-10-10 10:31 ` [PATCH v3 26/38] arm64: Avoid cpus_have_const_cap() for ARM64_MTE Mark Rutland
2023-10-10 10:31 ` [PATCH v3 27/38] arm64: Avoid cpus_have_const_cap() for ARM64_SSBS Mark Rutland
2023-10-10 10:31 ` [PATCH v3 28/38] arm64: Avoid cpus_have_const_cap() for ARM64_SPECTRE_V2 Mark Rutland
2023-10-10 10:31 ` [PATCH v3 29/38] arm64: Avoid cpus_have_const_cap() for ARM64_{SVE,SME,SME2,FA64} Mark Rutland
2023-10-10 10:31 ` [PATCH v3 30/38] arm64: Avoid cpus_have_const_cap() for ARM64_UNMAP_KERNEL_AT_EL0 Mark Rutland
2023-10-10 10:31 ` [PATCH v3 31/38] arm64: Avoid cpus_have_const_cap() for ARM64_WORKAROUND_843419 Mark Rutland
2023-10-10 10:31 ` [PATCH v3 32/38] arm64: Avoid cpus_have_const_cap() for ARM64_WORKAROUND_1542419 Mark Rutland
2023-10-10 10:31 ` [PATCH v3 33/38] arm64: Avoid cpus_have_const_cap() for ARM64_WORKAROUND_1742098 Mark Rutland
2023-10-13 10:53   ` Mark Rutland
2023-10-13 18:04     ` Catalin Marinas
2023-10-16 10:08       ` Mark Rutland
2023-10-10 10:31 ` [PATCH v3 34/38] arm64: Avoid cpus_have_const_cap() for ARM64_WORKAROUND_2645198 Mark Rutland
2023-10-10 10:31 ` [PATCH v3 35/38] arm64: Avoid cpus_have_const_cap() for ARM64_WORKAROUND_CAVIUM_23154 Mark Rutland
2023-10-10 10:31 ` [PATCH v3 36/38] arm64: Avoid cpus_have_const_cap() for ARM64_WORKAROUND_NVIDIA_CARMEL_CNP Mark Rutland
2023-10-10 10:31 ` [PATCH v3 37/38] arm64: Avoid cpus_have_const_cap() for ARM64_WORKAROUND_REPEAT_TLBI Mark Rutland
2023-10-10 10:31 ` [PATCH v3 38/38] arm64: Remove cpus_have_const_cap() Mark Rutland

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=ZS2PDl0j1_4quiFt@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=ardb@kernel.org \
    --cc=bertrand.marquis@arm.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=james.morse@arm.com \
    --cc=jgross@suse.com \
    --cc=kristina.martsenko@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=pcc@google.com \
    --cc=sstabellini@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=tglx@linutronix.de \
    --cc=vladimir.murzin@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.