public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 6/7] ARM: extend non-secure switch to also go into HYP mode
Date: Thu, 04 Jul 2013 13:29:31 +0200	[thread overview]
Message-ID: <51D55C9B.7000104@linaro.org> (raw)
In-Reply-To: <20130628125133.383C.AA925319@jp.panasonic.com>

On 06/28/2013 05:51 AM, Masahiro Yamada wrote:
> Hi Andre
>
>
> [RFC]
>
> I'd like to suggest to separate HYP-switching code
> from Non-secure switching.

Thanks for stepping up and providing a use-case!
The first version of the patches had those two separate cases, but I
later merged them in favor of readability.
So I actually split those two cases in the code now and am about to fold 
this in the existing patches.

> And define different macros, for example:
>
> CONFIG_ARMV7_NONSECURE : switch to nonsecure
> CONFIG_ARMV7_VIRT      : switch to hypervisor

done.

>
> Of cource, CONFIG_ARMV7_NONSECURE must be defined
> when using CONFIG_ARMV7_VIRT.
>
> (If we introduced Kconfig to U-boot,
> we could handle nicely dependency between CONFIGs.)

I managed to get along without it. By clever use of ifdefs this 
dependency is now implicitly in the code.

I still have to test this, so the new version will be delayed a bit.

Thanks!
Andre.

>
> I know your incentive to switch to non-secure state
> is virtualization.
> But I think this separation would make this code
> useful for other boards and easy to understand.
>
> For example (this situtation might be specific
> to my board), non-secure switching is done
> for the reason to use a hardware debugger,
> because our debugger without security extension
> can work only in non-secure state.
>
>
>
> Best Regards
> Masahiro Yamada
>
>

  reply	other threads:[~2013-07-04 11:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 11:01 [U-Boot] [PATCH v2 0/7] ARMv7: Add HYP mode switching support Andre Przywara
2013-06-13 11:01 ` [U-Boot] [PATCH v2 1/7] ARM: prepare armv7.h to be included from assembly source Andre Przywara
2013-06-28  1:00   ` Masahiro Yamada
2013-07-04  7:38     ` Andre Przywara
2013-06-13 11:01 ` [U-Boot] [PATCH v2 2/7] ARM: add secure monitor handler to switch to non-secure state Andre Przywara
2013-06-28  3:00   ` Masahiro Yamada
2013-06-13 11:01 ` [U-Boot] [PATCH v2 3/7] ARM: add assembly routine " Andre Przywara
2013-06-19 22:27   ` Christoffer Dall
2013-06-28  3:09   ` Masahiro Yamada
2013-06-13 11:01 ` [U-Boot] [PATCH v2 4/7] ARM: switch to non-secure state during bootm execution Andre Przywara
2013-06-19 23:13   ` Christoffer Dall
2013-06-28  3:18   ` Masahiro Yamada
2013-07-04  7:42     ` Andre Przywara
2013-06-13 11:01 ` [U-Boot] [PATCH v2 5/7] ARM: add SMP support for non-secure switch Andre Przywara
2013-06-19 23:27   ` Christoffer Dall
2013-06-28  3:22   ` Masahiro Yamada
2013-06-13 11:01 ` [U-Boot] [PATCH v2 6/7] ARM: extend non-secure switch to also go into HYP mode Andre Przywara
2013-06-19 23:40   ` Christoffer Dall
2013-06-21 14:38   ` Nikolay Nikolaev
2013-06-25  8:27     ` Andre Przywara
2013-06-28  3:51   ` Masahiro Yamada
2013-07-04 11:29     ` Andre Przywara [this message]
2013-06-13 11:01 ` [U-Boot] [PATCH v2 7/7] ARM: VExpress: enable ARMv7 virt support for VExpress A15 Andre Przywara

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=51D55C9B.7000104@linaro.org \
    --to=andre.przywara@linaro.org \
    --cc=u-boot@lists.denx.de \
    /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