All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Stuart Yoder <stuart.yoder@freescale.com>
Cc: "linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	Kevin Hilman <khilman@linaro.org>
Subject: Re: kvm status on lsk-3.14
Date: Thu, 3 Sep 2015 10:52:23 +0200	[thread overview]
Message-ID: <20150903085223.GD5171@cbox> (raw)
In-Reply-To: <BY2PR0301MB0743E324B8112812CC532C2587690@BY2PR0301MB0743.namprd03.prod.outlook.com>

On Wed, Sep 02, 2015 at 04:56:46PM +0000, Stuart Yoder wrote:
> Chris,
> 
> On the Linaro wiki there is an ARMv8 status page
> https://wiki.linaro.org/LSK/ARMv8
> 
> ...that seems a bit out of date.  It reports that KVM
> support on the Linaro 3.14 kernel had a "target" of
> release 14.10 (last October).
> 
> I see ~70 "arm64:" + "kvm:" patches added or backported
> to the Linaro 3.14 kernel.  Is KVM considered 'supported'
> in the latest lsk-3.14? If yes, are there any known
> limitations or anything missing?

We've backported most of the functionality and fixes up until 4.0, I
believe.

> 
> We have a customer interested in 3.14 on 
> ARMv8 and would like to understand what I can say
> about KVM support on the Linaro 3.14 kernel.
> 

The biggest weakness is probably lack of testing for virtualization
purposes.  I'm not aware of anyone haveing done any serious testing on
LSK with KVM.

Cc'ing Kevin for his comments on the testing and status aspect.

Thanks,
-Christoffer

  reply	other threads:[~2015-09-03  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 16:56 kvm status on lsk-3.14 Stuart Yoder
2015-09-03  8:52 ` Christoffer Dall [this message]
2015-09-03 20:38   ` Kevin Hilman

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=20150903085223.GD5171@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=khilman@linaro.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=stuart.yoder@freescale.com \
    /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.