linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: James Morse <james.morse@arm.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>
Cc: Marc Zyngier <maz@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	yuzenghui <yuzenghui@huawei.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Jing Zhang <jingzhangos@google.com>,
	"Wangzhou (B)" <wangzhou1@hisilicon.com>
Subject: RE: [PATCH v3 4/6] KVM: arm64: Disable MPAM visibility by default and ignore VMM writes
Date: Tue, 27 Aug 2024 08:58:43 +0000	[thread overview]
Message-ID: <82695efb73ca463b904aa49a595be06c@huawei.com> (raw)
In-Reply-To: <e22f30c045b64f3da68fb0aa6c0b4e2c@huawei.com>

Hi James,

> -----Original Message-----
> From: Shameerali Kolothum Thodi
> Sent: Friday, June 28, 2024 9:11 AM
> To: 'James Morse' <james.morse@arm.com>; linux-arm-
> kernel@lists.infradead.org; kvmarm@lists.linux.dev
> Cc: Marc Zyngier <maz@kernel.org>; Oliver Upton <oliver.upton@linux.dev>;
> Suzuki K Poulose <suzuki.poulose@arm.com>; yuzenghui
> <yuzenghui@huawei.com>; Catalin Marinas <catalin.marinas@arm.com>;
> Will Deacon <will@kernel.org>; Jing Zhang <jingzhangos@google.com>;
> Wangzhou (B) <wangzhou1@hisilicon.com>
> Subject: RE: [PATCH v3 4/6] KVM: arm64: Disable MPAM visibility by default
> and ignore VMM writes
 (vcpu, rd, user_val);
> > +}
> 
> Commit 14e270fa5c4c(arm64/cpufeature: Add remaining feature bits in
> ID_AA64PFR1 register")
> exposes the MPAMFRAC filed in in AA64PFR1_EL1. Don't we need a similar
> handling for that
> as well to handle the FEAT_MPAMv0p1 case?
> 
> Also any chance you plan to respin this series soon? We do have hardware
> that benefits from this
> series.

Just a gentle ping to see if you have plans to respin this series soon or not. 
Please let me know, if I can be of any help. We do have platforms that
differ in their MPAM features and that breaks migration. 

Thanks,
Shameer


  reply	other threads:[~2024-08-27  9:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 16:57 [PATCH v3 0/6] KVM: arm64: Hide unsupported MPAM from the guest James Morse
2024-03-21 16:57 ` [PATCH v3 1/6] arm64: head.S: Initialise MPAM EL2 registers and disable traps James Morse
2024-03-21 16:57 ` [PATCH v3 2/6] arm64: cpufeature: discover CPU support for MPAM James Morse
2024-04-12 14:41   ` Will Deacon
2024-06-28  8:23   ` Shameerali Kolothum Thodi
2024-03-21 16:57 ` [PATCH v3 3/6] KVM: arm64: Fix missing traps of guest accesses to the MPAM registers James Morse
2024-03-21 16:57 ` [PATCH v3 4/6] KVM: arm64: Disable MPAM visibility by default and ignore VMM writes James Morse
2024-06-28  8:10   ` Shameerali Kolothum Thodi
2024-08-27  8:58     ` Shameerali Kolothum Thodi [this message]
2024-03-21 16:57 ` [PATCH v3 5/6] KVM: arm64: selftests: Move the bulky macro invocation to a helper James Morse
2024-03-21 16:57 ` [PATCH v3 6/6] KVM: arm64: selftests: Test ID_AA64PFR0.MPAM isn't completely ignored James Morse

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=82695efb73ca463b904aa49a595be06c@huawei.com \
    --to=shameerali.kolothum.thodi@huawei.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=jingzhangos@google.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=suzuki.poulose@arm.com \
    --cc=wangzhou1@hisilicon.com \
    --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;
as well as URLs for NNTP newsgroup(s).