From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alexander Graf <agraf@csgraf.de>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH v2] target/arm: Support PSCI 1.1 and SMCCC 1.0
Date: Fri, 25 Feb 2022 12:36:40 +0900 [thread overview]
Message-ID: <9223d640-3f50-1258-1bdb-e3ca5d635981@gmail.com> (raw)
In-Reply-To: <CAFEAcA9eXpxC7R_qcDsBh4C9Aur5417kTzAhs4c7p2YRCFQUKQ@mail.gmail.com>
On 2022/02/24 21:53, Peter Maydell wrote:
> On Sun, 13 Feb 2022 at 03:58, Akihiko Odaki <akihiko.odaki@gmail.com> wrote:
>>
>> Support the latest PSCI on TCG and HVF. A 64-bit function called from
>> AArch32 now returns NOT_SUPPORTED, which is necessary to adhere to SMC
>> Calling Convention 1.0. It is still not compliant with SMCCC 1.3 since
>> they do not implement mandatory functions.
>>
>> Signed-off-by: Akihiko Odaki <akihiko.odaki@gmail.com>
>> ---
>
> Applied, thanks.
>
> Please update the changelog at https://wiki.qemu.org/ChangeLog/7.0
> for any user-visible changes.
>
> (I noticed while reviewing this that we report KVM's PSCI via
> the DTB as only 0.2 even if KVM's actually implementing better
> than that; I'll write a patch to clean that up.)
>
> -- PMM
I don't have an account on https://wiki.qemu.org/ so can you create one?
I'll update the changelog once I get access to the account.
Regards,
Akihiko Odaki
next prev parent reply other threads:[~2022-02-25 3:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 3:57 [PATCH v2] target/arm: Support PSCI 1.1 and SMCCC 1.0 Akihiko Odaki
2022-02-24 12:53 ` Peter Maydell
2022-02-25 3:36 ` Akihiko Odaki [this message]
2022-02-25 10:32 ` Peter Maydell
2022-02-24 13:25 ` Peter Maydell
2022-02-24 13:32 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2022-02-24 14:37 Akihiko Odaki
2022-02-24 14:41 ` Peter Maydell
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=9223d640-3f50-1258-1bdb-e3ca5d635981@gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=agraf@csgraf.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).