public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [RFC] KVM/arm64, take #3
Date: Tue, 22 Jan 2013 19:02:59 +0000	[thread overview]
Message-ID: <50FEE263.3040001@arm.com> (raw)

Guys,

I've once more updated the branches for KVM/arm64

- kvm-arm/pre-arm64: kvm-arm-master as of today + the "cleanup" branch +
some basic perf support

- arm64/soc-armv8-model: Catalin Marinas' arm64 branch

- arm64/psci: Implementation of PSCI for the above

- arm64/perf: host/guest discrimination

- kvm-arm64/kvm-prereq: a bunch of random bits that KVM/arm requires to
compile on arm64.

- kvm-arm64/kvm-prereq-merged: all the above, plus Mark Rutland's timer
rework.

- kvm-arm64/kvm: KVM/arm64 itself, and the only branch you should use
unless you're completely hatstand.

All that is at:
git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git

You'll also need Will Deacon's KVM Tool port:
git://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git kvmtool/arm


A few random notes:
- If you're using the Foundation Model, use the provided DTS for your
host kernel (arch/arm64/boot/dts/foundation-v8.dts).
- The only supported models are the AEMv8 and the Foundation models. If
you're using something else and have any issue, first reproduce it with
one of the supported implementations.

What's new:
- Rebased on 3.8-rc4
- Resynced with kvm-arm-master
- More 32bit fixes (ThumbEE, check for lack of 32bit support in HW)
- Some basic perf support

Enjoy,

	M.
-- 
Jazz is not dead. It just smells funny...


             reply	other threads:[~2013-01-22 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 19:02 Marc Zyngier [this message]
     [not found] ` <CAAHg+Hijc6o5G3VtX--QgNRhmaFN+N0ZnnOnzpss3bowHPkiNA@mail.gmail.com>
2013-01-23 12:01   ` [kvmarm] [RFC] KVM/arm64, take #3 Marc Zyngier

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=50FEE263.3040001@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    /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