linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andre.przywara@arm.com (Andre Przywara)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm: configs: improve KVM support
Date: Mon,  4 Jan 2016 14:50:32 +0000	[thread overview]
Message-ID: <1451919034-12846-1-git-send-email-andre.przywara@arm.com> (raw)

Hi,

there doesn't seem to be a good generic defconfig which includes
KVM support, so this config tends to get less testing.
This mini-series addresses this with a two-fold approach:

Patch 1/2 introduces VIRTIO drivers to the existing multi_v7_defconfig,
so those kernels can be easily used as guest kernels in KVM.
This goes with the arm64 defconfig, which has those drivers compiled
in as well.

Patch 2/2 adds a new kvm_defconfig, which includes LPAE and KVM host
capability on top of the said multi_v7_defconfig. This should help to
find compatibility issues with LPAE configs on the way.
I didn't bother to deselect platforms that are not LPAE capable, as:
a) some platforms may include LPAE capable cores in the future
b) compile testing drivers is part of this exercise.
I guess with LPAE capable machines adding some KBytes to the
kernel image is not really an issue, so let's just keep those
platforms in. Also that makes the diff to multi_v7_defconfig pretty
small.

Alison, the last patch comes pretty close to your:
"[RFC PATCH] ARM: add v7 LPAE multi-platform defconfig" from early
November, though with a slightly different focus. If you have a new
version of your patch in the queue, I am happy to withdraw mine and
rather help to get yours merged, possibly with the KVM options added.
What is your take on this?

Cheers,
Andre.

Andre Przywara (2):
  arm: multi_v7_defconfig: Add virtio drivers
  arm: configs: add kvm_defconfig

 arch/arm/configs/{multi_v7_defconfig => kvm_defconfig} | 14 ++++++++++++++
 arch/arm/configs/multi_v7_defconfig                    |  8 ++++++++
 2 files changed, 22 insertions(+)
 copy arch/arm/configs/{multi_v7_defconfig => kvm_defconfig} (98%)

-- 
2.6.4

             reply	other threads:[~2016-01-04 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 14:50 Andre Przywara [this message]
2016-01-04 14:50 ` [PATCH 1/2] arm: multi_v7_defconfig: Add virtio drivers Andre Przywara
2016-01-04 15:11   ` Arnd Bergmann
2016-01-08 10:52     ` Arnd Bergmann
2016-01-04 14:50 ` [PATCH 2/2] arm: configs: add kvm_defconfig Andre Przywara
2016-01-04 15:15   ` Arnd Bergmann

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=1451919034-12846-1-git-send-email-andre.przywara@arm.com \
    --to=andre.przywara@arm.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 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).