[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Zmrn9u8pJ0nduxfQ@google.com>
Date: Thu, 13 Jun 2024 12:37:10 +0000
From: Sebastian Ene <sebastianene@...gle.com>
To: Sudeep Holla <sudeep.holla@....com>
Cc: catalin.marinas@....com, james.morse@....com, jean-philippe@...aro.org,
maz@...nel.org, oliver.upton@...ux.dev, qperret@...gle.com,
qwandor@...gle.com, suzuki.poulose@....com, tabba@...gle.com,
will@...nel.org, yuzenghui@...wei.com, lpieralisi@...nel.org,
kvmarm@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, kernel-team@...roid.com
Subject: Re: [PATCH v2 3/4] KVM: arm64: Fix the identification range for the
FF-A smcs
On Wed, Jun 12, 2024 at 03:38:26PM +0100, Sudeep Holla wrote:
> On Wed, May 15, 2024 at 05:22:57PM +0000, Sebastian Ene wrote:
> > The FF-A spec 1.2 reserves the following ranges for identifying FF-A
> > calls:
> > 0x84000060-0x840000FF: FF-A 32-bit calls
> > 0xC4000060-0xC40000FF: FF-A 64-bit calls.
> >
> > Use the range identification according to the spec and allow calls that
> > are currently out of the range(eg. FFA_MSG_SEND_DIRECT_REQ2) to be
> > identified correctly.
> >
>
> Reviewed-by: Sudeep Holla <sudeep.holla@....com>
>
> Not sure if this needs to be fixes though. With addition of notifications
> in the FF-A driver(since v6.7), host can send FF-A messages beyond 0x7F.
> But since the pKVM FF-A proxy support is not yet updated to v1.1, so I
> don't think it needs to be tagged as fix. Just thought I will mention it
> here anyways.
Yes, good point. I will rewrite the title of the commit to remove the
fixes tag.
>
> --
> Regards,
> Sudeep
Thanks,
Seb
Powered by blists - more mailing lists