linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: A15 h/w virtulization support
Date: Tue, 12 Apr 2011 21:47:14 +0100	[thread overview]
Message-ID: <20110412204714.GD7806@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <BANLkTi=cOmWQuPY_aG5T6JoOAYCXshdyPg@mail.gmail.com>

On Tue, Apr 12, 2011 at 12:16:10PM +0530, Subash Patel wrote:
> If I am not wrong, Cortex-A15 is WIP with many SoC vendors. From my
> understanding, A15 has additional operational mode "hypervisor mode"
> and SMMU support for GuestOS memory to IPA in VMM, and IPA in VMM into
> PA. I was curious to know whether ARM v7 changes for Linux
> is happening for this? This will help to understand the KVM changes
> that may be required to run Linux directly in ring-0, and support
> guest OS?

Currently, I am planning no work on merging virtualization support.

Linus complained during the last merge window about the size of the
arch/arm sub-tree, and we - as the *entire* ARM community - really
need to address this issue right now.

Therefore, I will be taking no patches which aren't bug fixes or
consolidation patches for code which already lives in the kernel.

I am presently not convinced that many people are taking this issue
seriously enough, believing that "someone else will sort it out for
me."  This isn't going to happen.  If that's what many people are
doing, then I believe that we'll see ARM being removed from mainline
kernels.

Longer term, folk need to open their minds and look through code
which is already present to see whether code which one SoC already
implements can be re-used for their SoC, and actually sort out
re-using that code rather than submitting their own thing.

I believe that we are far too large in mainline to allow anything new
in.

If you're wondering "why doesn't X do that work" the answer is that
there have already been efforts to consolidate things, but because of
the sheer amount of new ARM specific code flowing into the kernel,
these consolidations completely disappear into the noise.  We need an
army of people working on this.

So, at the moment, virtualization support for ARM in mainline kernels
is completely out of the question.

      reply	other threads:[~2011-04-12 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12  6:46 A15 h/w virtulization support Subash Patel
2011-04-12 20:47 ` Russell King - ARM Linux [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=20110412204714.GD7806@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).