From: Julien Grall <julien.grall@arm.com>
To: Volodymyr Babchuk <volodymyr_babchuk@epam.com>, xen-devel@lists.xen.org
Cc: Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH 2/2] arm: traps: handle PSCI calls inside `smccc.c`
Date: Wed, 14 Jun 2017 15:21:23 +0100 [thread overview]
Message-ID: <980dfb6a-2705-cfce-74b5-827dfcb54ee5@arm.com> (raw)
In-Reply-To: <1497449445-23112-3-git-send-email-volodymyr_babchuk@epam.com>
Hi Volodymyr,
On 06/14/2017 03:10 PM, Volodymyr Babchuk wrote:
> PSCI is part of HVC/SMC interface, so it should be handled in
> appropriate place: `smccc.c`. This patch just moves PSCI
> handler calls from `traps.c` to `smccc.c`.
>
> PSCI is considered as two different "services" in terms of SMCCC.
> Older PSCI 1.0 is treated as "architecture service", while never
> PSCI 2.0 is defined as "standard secure service".
>
> Also old accessors PSCI_ARG() and PSCI_RESULT_REG() were replaced
> with generic set_user_reg()/get_user_reg() functions.
This is a call to split the patch in multiple small ones to ease the review.
I like the idea of using SMCC for PSCI, and will review the code when it
will be split.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-14 14:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 14:10 [PATCH 0/2] Handle SMCs and HVCs in conformance with SMCCC Volodymyr Babchuk
2017-06-14 14:10 ` [PATCH 1/2] arm: smccc: handle SMCs/HVCs according to SMCCC Volodymyr Babchuk
2017-06-15 10:48 ` Julien Grall
2017-06-19 21:59 ` Volodymyr Babchuk
2017-06-20 11:55 ` Julien Grall
2017-06-22 16:29 ` Volodymyr Babchuk
2017-06-27 11:08 ` Julien Grall
2017-06-27 14:40 ` Volodymyr Babchuk
2017-06-27 14:54 ` Julien Grall
2017-06-16 21:24 ` Stefano Stabellini
2017-08-01 10:59 ` Julien Grall
2017-08-01 14:25 ` Edgar E. Iglesias
2017-08-01 20:40 ` Stefano Stabellini
2017-08-01 21:02 ` Julien Grall
2017-08-01 21:22 ` Edgar E. Iglesias
2017-08-01 22:07 ` Julien Grall
2017-08-02 18:29 ` Stefano Stabellini
2017-06-14 14:10 ` [PATCH 2/2] arm: traps: handle PSCI calls inside `smccc.c` Volodymyr Babchuk
2017-06-14 14:21 ` Julien Grall [this message]
2017-06-14 14:37 ` Volodymyr Babchuk
2017-06-14 15:27 ` Julien Grall
2017-06-22 16:24 ` [PATCH v2 0/4] Handle SMCs and HVCs in conformance with SMCCC Volodymyr Babchuk
2017-06-22 16:24 ` [PATCH v2 1/4] arm: traps: psci: use generic register accessors Volodymyr Babchuk
2017-06-30 10:37 ` Julien Grall
2017-06-22 16:24 ` [PATCH v2 2/4] arm: smccc: handle SMCs/HVCs according to SMCCC Volodymyr Babchuk
2017-06-30 15:15 ` Julien Grall
2017-07-18 13:21 ` Julien Grall
2017-06-22 16:24 ` [PATCH v2 3/4] arm: traps: handle PSCI calls inside `vsmc.c` Volodymyr Babchuk
2017-06-30 21:13 ` Stefano Stabellini
2017-07-02 19:31 ` Julien Grall
2017-06-22 16:25 ` [PATCH v2 4/4] vsmc: psci: remove 64 bit mode check Volodymyr Babchuk
2017-06-30 21:19 ` Stefano Stabellini
2017-07-02 19:40 ` Julien Grall
2017-07-03 17:29 ` Stefano Stabellini
2017-07-04 11:44 ` Julien Grall
2017-07-02 19:34 ` Julien Grall
2017-07-02 19:34 ` Julien Grall
2017-06-27 12:57 ` [PATCH v2 0/4] Handle SMCs and HVCs in conformance with SMCCC Julien Grall
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=980dfb6a-2705-cfce-74b5-827dfcb54ee5@arm.com \
--to=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=volodymyr_babchuk@epam.com \
--cc=xen-devel@lists.xen.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.