public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Keerthy <a0393675@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/2] ARM: Introduce function to switch to hypervisor mode
Date: Fri, 29 Jul 2016 17:32:42 +0530	[thread overview]
Message-ID: <579B45E2.3030605@ti.com> (raw)
In-Reply-To: <1469773745-11888-1-git-send-email-j-keerthy@ti.com>



On Friday 29 July 2016 11:59 AM, Keerthy wrote:
> On SoCs like DRA7, OMAP5 one cannot enable hypervisor mode directly from the
> u-boot because the ROM code puts the chip to supervisor mode after it
> jumps to boot loader.
>
> Patch 1: Introduces a weak function which can be overridden specific to
> SoCs to switch to hypervisor mode.
>
> Patch 2: overrides weak function in patch 1 switch cpu to hypervisor
> mode using the available ROM code hook early in the boot phase before
> the boot loader checks for hypervisor mode on OMAP5 based SoCs.

Hi Tom,

I request you to hold on merge of this series. I am doing some 
performance measurements. I see some drop. So analyzing and root causing.

Thanks,
Keerthy

>
> Changes in v2:
>
>    * Fixed a compile time error on older defconfigs due to #ifdef
>      issue.
>
> Boot tested on DRA7-EVM and DRA72-EVM.
>
> Keerthy (2):
>    ARM: Introduce function to switch to hypervisor mode
>    ARM: OMAP5+: Override switch_to_hypervisor function
>
>   arch/arm/cpu/armv7/omap-common/lowlevel_init.S | 21 +++++++++++++++++++++
>   arch/arm/cpu/armv7/start.S                     | 15 +++++++++++++++
>   arch/arm/include/asm/system.h                  |  1 +
>   3 files changed, 37 insertions(+)
>

      parent reply	other threads:[~2016-07-29 12:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  6:29 [U-Boot] [PATCH v2 0/2] ARM: Introduce function to switch to hypervisor mode Keerthy
2016-07-29  6:29 ` [U-Boot] [PATCH v2 1/2] " Keerthy
2016-07-29  6:29 ` [U-Boot] [PATCH v2 2/2] ARM: OMAP5+: Override switch_to_hypervisor function Keerthy
2016-07-29 12:02 ` Keerthy [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=579B45E2.3030605@ti.com \
    --to=a0393675@ti.com \
    --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