xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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 4/4] arm: traps: handle SMC32 in check_conditional_instr()
Date: Wed, 9 Aug 2017 10:47:18 +0100	[thread overview]
Message-ID: <b0c98ba8-5b8a-c9c1-0a3f-00f3cd7fcd39@arm.com> (raw)
In-Reply-To: <e7f71341-391f-aaf8-a1fd-e0a3d8013cdd@epam.com>



On 08/08/17 21:42, Volodymyr Babchuk wrote:
> Hi Julien,

Hi Volodymyr,

> On 28.07.17 23:37, Julien Grall wrote:
>> Hi,
>>
>> On 07/28/2017 08:43 PM, Volodymyr Babchuk wrote:
>>> On ARMv8 architecture SMC instruction in aarch32 state can be
>>> conditional.
>>
>> version + paragraph please.
>>
>> Also, ARMv8 supports both AArch32 and AArch64. As I said in my answer
>> on "arm: smccc: handle SMCs/HVCs according to SMCCC" ([1]), This field
>> exists for both architecture. I really don't want to tie the 32-bit
>> port to ARMv7. We should be able to use ARMv8 too.
> Not sure if I got this.
>
> My ARM 7 ARM (ARM DDI 0406C.c ID051414 page B3-1431) say following:
>
> "SMC instructions cannot be trapped if they fail their condition code
> check.
> Therefore, the syndrome information for this exception does not include
> conditionality information."
>
> ARMv8 ARM (ARM DDI 0487A.k ID092916) says that SMC from aarch32 state can
> be conditional and my patch checks this. But SMC from aarch64 state is
> unconditional, so there are nothing to check. At least, when looking at
> ISS encoding, i see imm16 field and RES0 field. No conditional flags.

ARM 32-bit is not only ARMv7, it could also be ARMv8. If you look at 
Part G describing the AArch32 state, specifically G1-4434, "The ARMv8-A 
architecture permits, but does not require, this trap to apply to 
conditional SMC instructions that fail their Condition code check...".

Xen ARM 32-bits should be able to boot any 32-bit ARM platform (ARMv7, 
ARMv8). But your #ifdef belows prevent that.

Cheers,

-- 
Julien Grall

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

      reply	other threads:[~2017-08-09  9:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 19:43 [PATCH 0/4] arm: allign check_conditional_instr() with ARM64 requirements Volodymyr Babchuk
2017-07-28 19:43 ` [PATCH 1/4] arm: processor: rename iss to res0 in hsr_cond union Volodymyr Babchuk
2017-07-28 20:29   ` Julien Grall
2017-07-28 19:43 ` [PATCH 2/4] arm: processor: add ccknownpass field into " Volodymyr Babchuk
2017-07-28 20:31   ` Julien Grall
2017-07-28 20:40     ` Julien Grall
2017-07-28 19:43 ` [PATCH 3/4] arm: traps: handle unknown exceptions in check_conditional_instr() Volodymyr Babchuk
2017-07-28 20:31   ` Julien Grall
2017-07-28 19:43 ` [PATCH 4/4] arm: traps: handle SMC32 " Volodymyr Babchuk
2017-07-28 20:37   ` Julien Grall
2017-08-08 20:42     ` Volodymyr Babchuk
2017-08-09  9:47       ` Julien Grall [this message]

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=b0c98ba8-5b8a-c9c1-0a3f-00f3cd7fcd39@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 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).