From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [kvmarm] [GIT PULL] KVM/ARM core implementation
Date: Thu, 24 Jan 2013 15:35:39 +0100 [thread overview]
Message-ID: <6686cc0110a04573c650fc03a0f42017@localhost> (raw)
In-Reply-To: <CANM98qLq5wfuUWHmjn_SHG=f1O9kG_cgwpA2VfOy5y4t0m-52Q@mail.gmail.com>
On Wed, 23 Jan 2013 14:22:23 -0500, Christoffer Dall
<c.dall@virtualopensystems.com> wrote:
> Hi Will,
>
> I've prepared a stable branch for you, for-will/kvm/core, based on
> your stable perf branch.
>
> Since the last patch series, I've addressed the reviewer comments, and
> rev'ed KVM_CAP_ARM_PSCI to 87, since 86 is already used by PPC in
> kvm/next.
>
> kvmtool should probably be updated acoordingly.
>
> I rebased the VGIC and the Arch. Timers series on the stable branch
> and made these available in kvm/vgic and kvm/vgic-timers,
> respectively. These branches are, however, not yet stable.
FWIW, I've now created a kvm-arm/vgic branch, based on for-will/kvm/core
and arm-soc's irqchip/gic-vic-move.
Not much has changed, apart from the obvious include paths and an
additional guard in arm-gic.h. This should definitely be stable now.
The timer code is currently blocked by the lack of a stable branch for the
broadcast stuff.
M.
--
Fast, cheap, reliable. Pick two.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Christoffer Dall <c.dall@virtualopensystems.com>
Cc: Will Deacon <will.deacon@arm.com>, <kvm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<kvmarm@lists.cs.columbia.edu>
Subject: Re: [kvmarm] [GIT PULL] KVM/ARM core implementation
Date: Thu, 24 Jan 2013 15:35:39 +0100 [thread overview]
Message-ID: <6686cc0110a04573c650fc03a0f42017@localhost> (raw)
In-Reply-To: <CANM98qLq5wfuUWHmjn_SHG=f1O9kG_cgwpA2VfOy5y4t0m-52Q@mail.gmail.com>
On Wed, 23 Jan 2013 14:22:23 -0500, Christoffer Dall
<c.dall@virtualopensystems.com> wrote:
> Hi Will,
>
> I've prepared a stable branch for you, for-will/kvm/core, based on
> your stable perf branch.
>
> Since the last patch series, I've addressed the reviewer comments, and
> rev'ed KVM_CAP_ARM_PSCI to 87, since 86 is already used by PPC in
> kvm/next.
>
> kvmtool should probably be updated acoordingly.
>
> I rebased the VGIC and the Arch. Timers series on the stable branch
> and made these available in kvm/vgic and kvm/vgic-timers,
> respectively. These branches are, however, not yet stable.
FWIW, I've now created a kvm-arm/vgic branch, based on for-will/kvm/core
and arm-soc's irqchip/gic-vic-move.
Not much has changed, apart from the obvious include paths and an
additional guard in arm-gic.h. This should definitely be stable now.
The timer code is currently blocked by the lack of a stable branch for the
broadcast stuff.
M.
--
Fast, cheap, reliable. Pick two.
next prev parent reply other threads:[~2013-01-24 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 19:22 [GIT PULL] KVM/ARM core implementation Christoffer Dall
2013-01-23 19:22 ` Christoffer Dall
2013-01-24 14:35 ` Marc Zyngier [this message]
2013-01-24 14:35 ` [kvmarm] " 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=6686cc0110a04573c650fc03a0f42017@localhost \
--to=marc.zyngier@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 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.