From: Andre Przywara <andre.przywara@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 0/6] ARMv7: Add HYP mode switching support
Date: Fri, 26 Apr 2013 16:14:18 +0200 [thread overview]
Message-ID: <517A8BBA.1030803@linaro.org> (raw)
In-Reply-To: <CAFEAcA881P7Bz-avq=DO5cb=7yzJkXnYTKqosBGFNMQ2ct+iPQ@mail.gmail.com>
On 04/26/2013 03:42 PM, Peter Maydell wrote:
> On 26 April 2013 14:24, Andre Przywara <andre.przywara@linaro.org> wrote:
>> On 04/26/2013 03:18 PM, Peter Maydell wrote:
>>> The obvious question here is "why do we need a new command?".
>>> The kernel booting specification says "boot the kernel in
>>> Hyp mode" so we should just always do that for booting Linux,
>>> surely?
>
>> Because it avoids regressions. I kind of feel uneasy to do a lot of
>> tinkering with secure state and the GIC unconditionally, especially if
>> enabled on many boards with virt-capable CPUs.
>
> There aren't exactly very many of those out there, so if we
> default to "boot in HYP mode" then (a) KVM will just work
> out of the box and (b) people doing u-boot ports to their
> board will find any issues and be able to submit fixes.
> If we don't turn it on by default then we'll end up stuck
> in a world where KVM doesn't work on half the virt capable
> boards out there.
OK, that's a point. I changed the code already and will include it in
the next revision.
Thanks,
Andre.
>
> I have no objection to a "turn this off" escape hatch if
> you think it's useful.
>
> -- PMM
>
next prev parent reply other threads:[~2013-04-26 14:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 13:14 [U-Boot] [RFC PATCH 0/6] ARMv7: Add HYP mode switching support Andre Przywara
2013-04-26 13:14 ` [U-Boot] [RFC PATCH 1/6] ARM: add secure monitor handler to switch to non-secure state Andre Przywara
2013-04-26 22:11 ` Christoffer Dall
2013-04-26 13:14 ` [U-Boot] [RFC PATCH 2/6] ARM: add assembly routine " Andre Przywara
2013-04-26 13:14 ` [U-Boot] [RFC PATCH 3/6] ARM: add U-Boot command "hypmode" " Andre Przywara
2013-04-26 13:14 ` [U-Boot] [RFC PATCH 4/6] ARM: add SMP support for non-secure switch Andre Przywara
2013-04-26 22:13 ` Christoffer Dall
2013-05-06 13:19 ` Andre Przywara
2013-05-10 22:41 ` Christoffer Dall
2013-04-26 13:14 ` [U-Boot] [RFC PATCH 5/6] ARM: extend non-secure switch to also go into HYP mode Andre Przywara
2013-04-26 13:14 ` [U-Boot] [RFC PATCH 6/6] ARM: VExpress: enable ARMv7 virt support for VExpress A15 Andre Przywara
2013-04-26 13:18 ` [U-Boot] [RFC PATCH 0/6] ARMv7: Add HYP mode switching support Peter Maydell
2013-04-26 13:24 ` Andre Przywara
2013-04-26 13:42 ` Peter Maydell
2013-04-26 14:14 ` Andre Przywara [this message]
2013-04-26 18:29 ` Christoffer Dall
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=517A8BBA.1030803@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