All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Ene <sebastianene@google.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: catalin.marinas@arm.com, james.morse@arm.com,
	jean-philippe@linaro.org, maz@kernel.org, oliver.upton@linux.dev,
	qperret@google.com, qwandor@google.com, suzuki.poulose@arm.com,
	tabba@google.com, will@kernel.org, yuzenghui@huawei.com,
	lpieralisi@kernel.org, kvmarm@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v2 3/4] KVM: arm64: Fix the identification range for the FF-A smcs
Date: Thu, 13 Jun 2024 12:37:10 +0000	[thread overview]
Message-ID: <Zmrn9u8pJ0nduxfQ@google.com> (raw)
In-Reply-To: <Zmmy4pmgLFZNhXqp@bogus>

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@arm.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

  reply	other threads:[~2024-06-13 12:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 17:22 [PATCH v2 0/4] KVM: arm64: pKVM host proxy FF-A fixes Sebastian Ene
2024-05-15 17:22 ` Sebastian Ene
2024-05-15 17:22 ` [PATCH v2 1/4] KVM: arm64: Trap FFA_VERSION host call in pKVM Sebastian Ene
2024-05-15 17:22   ` Sebastian Ene
2024-06-12 13:58   ` Sudeep Holla
2024-06-13 11:55     ` Sebastian Ene
2024-05-15 17:22 ` [PATCH v2 2/4] KVM: arm64: Add support for FFA_PARTITION_INFO_GET Sebastian Ene
2024-05-15 17:22   ` Sebastian Ene
2024-06-12 14:30   ` Sudeep Holla
2024-06-13 12:29     ` Sebastian Ene
2024-05-15 17:22 ` [PATCH v2 3/4] KVM: arm64: Fix the identification range for the FF-A smcs Sebastian Ene
2024-05-15 17:22   ` Sebastian Ene
2024-06-12 14:38   ` Sudeep Holla
2024-06-13 12:37     ` Sebastian Ene [this message]
2024-05-15 17:22 ` [PATCH v2 4/4] KVM: arm64: Use FF-A 1.1 with pKVM Sebastian Ene
2024-05-15 17:22   ` Sebastian Ene
2024-06-12 14:41   ` Sudeep Holla
2024-06-12 14:46 ` [PATCH v2 0/4] KVM: arm64: pKVM host proxy FF-A fixes Sudeep Holla

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=Zmrn9u8pJ0nduxfQ@google.com \
    --to=sebastianene@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=jean-philippe@linaro.org \
    --cc=kernel-team@android.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=qperret@google.com \
    --cc=qwandor@google.com \
    --cc=sudeep.holla@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.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 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.