qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fedorov Sergey <s.fedorov@samsung.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Johannes Winter <johannes.winter@iaik.tugraz.at>,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	a.basov@samsung.com,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC PATCH 18/21] target-arm: switch banked CP registers
Date: Fri, 20 Dec 2013 20:18:59 +0400	[thread overview]
Message-ID: <52B46DF3.1060303@samsung.com> (raw)
In-Reply-To: <52B4566B.9010608@samsung.com>


On 12/20/2013 06:38 PM, Fedorov Sergey wrote:
> On 12/20/2013 06:33 PM, Peter Maydell wrote:
>> On 20 December 2013 14:12, Fedorov Sergey <s.fedorov@samsung.com> wrote:
>>> I've briefly looked at the v8 ARM ARM. As I can see there is no banked
>>> system control registers in AArch64. Seems the concept is changed to provide
>>> separate registers for each meaningful execution level. Please, correct me
>>> if I am wrong.
>> Yes, I think this is generally correct.
>>
>>> So I think there shouldn't be "active" and "banked" fields for banked
>>> AArch32 CP15 registers as in my patch. Seems it is worth to use AArch64 view
>>> of system control registers as a basis. That means there would be separate S
>>> and NS register fields in CPU state structure that will me mapped to
>>> separate AArch64 registers. ARMCPRegInfo structure would have additional
>>> field holding NS register state filed offset for AArch32 banked registers.
>> This sounds like it could work, though there are some wrinkles for
>> registers with readfns/writefns -- do we have extra s vs ns read/write
>> functions, or just one set of functions which has to look in env->ns to
>> figure out whether to use the S or NS version?
> I think if most read/write functions do the same work for both S/NS
> versions then this code should not be duplicated.

But on the other hand, separate S/NS read/write functions could be
reused for AArch64 register descriptions that is separate for each EL...

>
>>> Which branch in https://git.linaro.org/people/peter.maydell/qemu-arm.git
>>> repository holds the most actual A64 support?
>> It's still a work in progress so it depends what you want.
>> a64-third-fourth-set is the last set of patches that went out for
>> review, and should generally work for integer instructions.
>> a64-working is my work-in-progress branch so it will have the
>> most recent versions of everything, but it rebases frequently
>> and is liable to occasionally be broken...
> Thanks.
>
>> thanks
>> -- PMM
>>

-- 
Best regards,
Sergey Fedorov

  reply	other threads:[~2013-12-20 16:19 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  8:48 [Qemu-devel] [RFC PATCH 00/21] target-arm: add CPU core TrustZone support Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 01/21] target-arm: add TrustZone CPU feature Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 02/21] target-arm: move SCR & VBAR into TrustZone register list Sergey Fedorov
2013-12-19  3:12   ` Peter Crosthwaite
2013-12-19  6:23     ` Fedorov Sergey
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 03/21] target-arm: adjust TTBCR for TrustZone feature Sergey Fedorov
2013-12-03 12:15   ` Peter Crosthwaite
2013-12-04  9:50     ` Fedorov Sergey
2013-12-04 10:52       ` Peter Crosthwaite
2013-12-19  3:18         ` Peter Crosthwaite
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 04/21] target-arm: preserve RAO/WI bits of ARMv7 SCTLR Sergey Fedorov
2013-12-03 12:17   ` Peter Crosthwaite
2013-12-04  9:55     ` Fedorov Sergey
2013-12-19  3:19       ` Peter Crosthwaite
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 05/21] target-arm: add CPU Monitor mode Sergey Fedorov
2013-12-03 12:20   ` Peter Crosthwaite
2013-12-03 12:51     ` Peter Maydell
2013-12-04 10:01       ` Fedorov Sergey
2013-12-04 10:58         ` Peter Crosthwaite
2013-12-04 11:18           ` Peter Maydell
2013-12-04 12:33             ` Fedorov Sergey
2013-12-04 12:35               ` Peter Maydell
2013-12-19  3:26                 ` Peter Crosthwaite
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 06/21] target-arm: add arm_is_secure() helper Sergey Fedorov
2013-12-19  3:31   ` Peter Crosthwaite
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 07/21] target-arm: reject switching to monitor mode from non-secure state Sergey Fedorov
2013-12-19  3:44   ` Peter Crosthwaite
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 08/21] target-arm: adjust arm_current_pl() for TrustZone Sergey Fedorov
2013-12-03 12:23   ` Peter Crosthwaite
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 09/21] target-arm: adjust SCR CP15 register access rights Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 10/21] target-arm: add non-secure Translation Block flag Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 11/21] target-arm: implement CPACR register logic Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 12/21] target-arm: add NSACR support Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 13/21] target-arm: add SDER definition Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 14/21] target-arm: split TLB for secure state Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 15/21] target-arm: add banked coprocessor register type Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 16/21] target-arm: convert appropriate coprocessor registers to banked type Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 17/21] target-arm: use c13_context field for CONTEXTIDR Sergey Fedorov
2013-12-19  4:31   ` Peter Crosthwaite
2013-12-19  6:29     ` Fedorov Sergey
2013-12-19  6:32   ` Peter Crosthwaite
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 18/21] target-arm: switch banked CP registers Sergey Fedorov
2013-12-19  4:37   ` Peter Crosthwaite
2013-12-19  7:27     ` Fedorov Sergey
2013-12-19 11:38       ` Peter Maydell
2013-12-19 12:44         ` Peter Crosthwaite
2013-12-19 13:39           ` Fedorov Sergey
2013-12-19 14:01             ` Peter Crosthwaite
2013-12-19 14:09               ` Peter Maydell
2013-12-20 14:12         ` Fedorov Sergey
2013-12-20 14:33           ` Peter Maydell
2013-12-20 14:38             ` Fedorov Sergey
2013-12-20 16:18               ` Fedorov Sergey [this message]
2013-12-22  1:08             ` Peter Crosthwaite
2013-12-22  7:59               ` Peter Maydell
2013-12-23  7:28               ` Fedorov Sergey
2013-12-23  7:43             ` Fedorov Sergey
2013-12-23  9:05               ` Peter Maydell
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 19/21] target-arm: add MVBAR support Sergey Fedorov
2013-12-19  4:41   ` Peter Crosthwaite
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 20/21] target-arm: implement SMC instruction Sergey Fedorov
2013-12-03  8:48 ` [Qemu-devel] [RFC PATCH 21/21] target-arm: implement IRQ/FIQ routing to Monitor mode Sergey Fedorov
2013-12-04 10:08 ` [Qemu-devel] [RFC PATCH 00/21] target-arm: add CPU core TrustZone support Fedorov Sergey
2013-12-04 11:10   ` Peter Crosthwaite
2013-12-04 11:13   ` Peter Maydell
2013-12-04 12:48     ` Fedorov Sergey
2013-12-19  4:56       ` Peter Crosthwaite

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=52B46DF3.1060303@samsung.com \
    --to=s.fedorov@samsung.com \
    --cc=a.basov@samsung.com \
    --cc=johannes.winter@iaik.tugraz.at \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.maydell@linaro.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).