xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Volodymyr Babchuk <volodymyr_babchuk@epam.com>, xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, andre.przywara@linaro.org
Subject: Re: [PATCH v2 2/3] xen/arm: vsmc: Don't implement function ID that doesn't exist
Date: Tue, 6 Feb 2018 15:29:57 +0000	[thread overview]
Message-ID: <33cfe720-8c2d-4f06-9104-b9ea183e7f08@linaro.org> (raw)
In-Reply-To: <e4a266e3-cb66-b8d9-78a9-56949240a51c@epam.com>

On 02/06/2018 03:15 PM, Volodymyr Babchuk wrote:
> Hi Julien,

Hi,

> On 06.02.18 16:53, Julien Grall wrote:
>> On 02/02/2018 01:46 PM, Volodymyr Babchuk wrote:
>>>
>>>
>>> On 02.02.18 13:41, Julien Grall wrote:
>>>> The current implementation of SMCCC relies on the fact only function
>>>> number (bits [15:0]) is enough to identify what to implement.
>>>>
>>>> However, PSCI call are only available in the range 
>>>> 0x84000000-0x8400001F
>>>> and 0xC4000000-0xC400001F. Furthermore, not all SMC32 functions have
>>>> equivalent in the SMC64. This is the case of:
>>>>      * PSCI_VERSION
>>>>      * CPU_OFF
>>>>      * MIGRATE_INFO_TYPE
>>>>      * SYSTEM_OFF
>>>>      * SYSTEM_RESET
>>>>
>>>> Similarly call count, call uid, revision can only be query using 
>>>> smc32/hvc32
>>>> fast calls (See 6.2 in ARM DEN 0028B).
>>>>
>>>> Xen should only implement identifier existing in the specification in
>>>> order to avoid potential clash with later revision. Therefore rework 
>>>> the
>>>> vsmc code to use the whole function identifier rather than only the
>>>> function number.
>>>>
>>>> At the same time, the new macros for call count, call uid, revision are
>>>> renamed to better suit the spec.
>>>>
>>>> Lastly, update SSSC_SMCCC_FUNCTION_COUNT to match the correct number of
>>>> funtions. Note that version is not updated because the number has 
>>>> always
>>>> been wrong, and nobody could properly use it.
>>>>
>>>> Signed-off-by: Julien Grall <julien.grall@linaro.org>
>>>
>>> `Reviewed-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>`
>>
>> Thank you for the reviewed-by. I noticed that you put ` at the 
>> beginning and end of the line in your reviewed-by tag so far. Is there 
>> any reason for that?
> 
> It is out of habit. You see, this is preferred way to add R-b tag at 
> GitHub (or at least in OP-TEE repos). Github uses Markdown, and text in 
> ` becomes formatted as a code. I do code review mostly at github,
> so it become a habit to add ` around R-b tags. You can ignore this, of 
> course. I'll try to omit ` in the future.

Oh, good to know. I am usually copying the full line and my editor was 
not happy at all with the `. For Xen, we tend to only have the 
Reviewed-by tag on a line.

Anyway, thank you for reviewing the series :). I will resend a version soon.

If you have time, you might want to have a look at "xen/arm: PSCI 1.1 
and SMCCC-1.1 support and XSA-254 variant 2 update" [1].

Cheers,

[1] https://lists.xen.org/archives/html/xen-devel/2018-02/msg00285.html

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-02-06 15:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-02 11:41 [PATCH v2 0/3] xen/arm: SMCCC fixes and PSCI clean-up Julien Grall
2018-02-02 11:41 ` [PATCH v2 1/3] xen/arm: vpsci: Removing dummy MIGRATE and MIGRATE_INFO_UP_CPU Julien Grall
2018-02-02 13:44   ` Volodymyr Babchuk
2018-02-02 11:41 ` [PATCH v2 2/3] xen/arm: vsmc: Don't implement function ID that doesn't exist Julien Grall
2018-02-02 13:46   ` Volodymyr Babchuk
2018-02-06 14:53     ` Julien Grall
2018-02-06 15:15       ` Volodymyr Babchuk
2018-02-06 15:29         ` Julien Grall [this message]
2018-02-02 11:41 ` [PATCH v2 3/3] xen/arm: vpsci: Move PSCI function dispatching from vsmc.c to vpsci.c Julien Grall
2018-02-02 14:23   ` Volodymyr Babchuk
2018-02-02 14:31     ` Julien Grall
2018-02-02 15:40       ` Volodymyr Babchuk
2018-02-06 14:45         ` Julien Grall
2018-02-06 15:28           ` Volodymyr Babchuk
2018-02-06 15:39             ` Julien Grall
2018-02-06 15:50               ` Volodymyr Babchuk

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=33cfe720-8c2d-4f06-9104-b9ea183e7f08@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=andre.przywara@linaro.org \
    --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 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).