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] [RFD] OMAP5: Working HYP mode
Date: Wed, 25 Sep 2013 09:57:16 +0200	[thread overview]
Message-ID: <5242975C.40805@linaro.org> (raw)
In-Reply-To: <1379370524-8429-1-git-send-email-alexander.tarasikov@gmail.com>

On 09/17/2013 12:28 AM, Alexander Tarasikov wrote:
> Hello, u-boot developers!
> I am attaching a patch to enable the HYP (hypervisor)
> mode on the OMAP5 CPU. It is based on a previous patch by
> Ian Molton. For some reason, Ian's patch was incorrect
> (loading PC with the wrong address, missing memory barriers,
> and, most importantly, using the wrong SMC call). I think it
> is because Ian was using some early omap5 prototype, and I was
> using the SVT OMAP5432UEVM board which is commercially available.
>
> Since this is a gross hack, I neither expect nor want it to be merged,
> but I think people experimenting with ARM virtualization will find
> it useful.
>
> I have KVM working on OMAP5 as of now (using KVM patches from
> openvirtualization and some linux kernel bugfixes of my own) and
> I plan to write a blog post soon about how to repeat my steps.
> My plan is to publish the patches to fix the bugs I've found.
>
> I would like to receive comments on what is the planned way to implement
> the HYP switching in u-boot and whether it is possible without using the
> TrustZone SMC calls.

Alexander,

have you seen my series?

http://lists.denx.de/pipermail/u-boot/2013-September/163019.html
[U-Boot] [PATCH v5 0/8] ARMv7: Add HYP mode switching support

I am about to support more boards, but OMAP5 seems very different, 
probably because it starts u-boot in non-secure state already, right?
So all the magic is in the firmware, which just needs to be called by 
smc calls, right?
So it looks like one could at least use some infrastructure 
(CONFIG_ARMV7_VIRT and the higher level .c files) to properly merge 
OMAP5 support in. Also needed would be to make most code of my patch 
optional by using the proper defines.
What do you think?

Regards,
Andre.

  parent reply	other threads:[~2013-09-25  7:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 22:28 [U-Boot] [RFD] OMAP5: Working HYP mode Alexander Tarasikov
2013-09-16 22:28 ` [U-Boot] [PATCH] HACK: enable HYP mode on OMAP5 Alexander Tarasikov
2013-09-18  6:35   ` MJ embd
2013-09-25  7:57 ` Andre Przywara [this message]
2013-10-01 22:14   ` [U-Boot] [RFD] OMAP5: Working HYP mode Alexander Tarasikov

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=5242975C.40805@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