All of lore.kernel.org
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Update: ARM Sub-Architecture Maintainers workshop at Kernel Summit 2011
Date: Mon, 17 Oct 2011 12:56:00 +0200	[thread overview]
Message-ID: <201110171256.00909.marek.vasut@gmail.com> (raw)
In-Reply-To: <20111017085429.GC3279@arm.com>

On Monday, October 17, 2011 10:54:29 AM Catalin Marinas wrote:
> On Tue, Aug 30, 2011 at 07:00:16AM +0100, Grant Likely wrote:
> > Agenda proposals (Thanks to Nicolas and Olof):
> ...
> 
> > - boot architecture status
> 
> If there is still room on the agenda, I would like to get an agreement
> on the best way to deal with the Hypervisor mode - (1) start the kernel
> in Hyp mode or (2) have a standard HVC API in the board firmware to
> allow Linux (KVM, Xen) to take control of the Hyp mode. This could fit
> under the boot architecture discussion.
> 
> For (1), it could be problematic as the boot loader (e.g. U-Boot) needs
> to be aware of the Hyp mode. The 2nd variant may be better but the API
> needs to be kept very simple.

Hi Catalin,

talking about U-Boot, I might pull out the u-boot driver model initiative and 
talk about it for a bit. It's still in design phase so it'd be awesome to get 
some comments on it.

Cheers

> 
> I know that neither KVM nor Xen for ARM are supported in the mainline
> kernel but silicon vendors are already working on Cortex-A15 platforms
> and it would be good if their firmware supports Linux virtualisation.
> 
> Thanks.

  reply	other threads:[~2011-10-17 10:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30  6:00 Update: ARM Sub-Architecture Maintainers workshop at Kernel Summit 2011 Grant Likely
2011-08-30  6:27 ` Igor Grinberg
2011-08-30 13:44   ` Grant Likely
2011-08-30 14:00     ` Igor Grinberg
2011-08-30 19:17     ` [Ksummit-2011-discuss] " Chris Ball
2011-08-30 12:55 ` Nicolas Ferre
2011-08-30 13:56 ` Wolfram Sang
2011-08-30 14:42 ` David Brown
2011-08-30 16:58 ` Paul Walmsley
2011-08-30 19:51 ` Olof Johansson
2011-08-30 23:42   ` Stephen Warren
2011-08-31  5:50   ` Marek Szyprowski
2011-08-30 23:10 ` Pavel Machek
2011-08-31  1:29   ` Marek Vasut
2011-08-31  2:31     ` Bryan Wu
2011-08-31  2:58       ` Marek Vasut
2011-08-31  3:07         ` Bryan Wu
2011-08-31 18:57     ` Grant Likely
2011-08-31  2:57 ` Bryan Wu
2011-08-31  2:59   ` Marek Vasut
2011-08-31  3:08     ` Bryan Wu
2011-08-31  4:01       ` Marek Vasut
2011-08-31  5:52         ` Eric Miao
2011-08-31 15:15 ` Marc Zyngier
2011-09-27 13:25 ` Igor Grinberg
2011-10-12  9:14   ` Igor Grinberg
2011-10-12  9:19     ` Catalin Marinas
2011-10-17 17:36       ` Igor Grinberg
2011-10-12 15:33     ` Nicolas Pitre
2011-10-17 17:31       ` Igor Grinberg
2011-10-12 10:01 ` Catalin Marinas
2011-10-12 15:00   ` Nicolas Pitre
2011-10-17  8:54 ` Catalin Marinas
2011-10-17 10:56   ` Marek Vasut [this message]
2011-10-20 13:35 ` Linus Walleij
2011-10-20 13:48   ` Jonathan Cameron
2011-10-20 14:25     ` Barry Song
2011-10-20 14:46       ` Mark Brown
2011-10-20 14:55         ` Jonathan Cameron
2011-10-21  9:39           ` Barry Song

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=201110171256.00909.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.