From: kraxel@redhat.com (Gerd Hoffmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] KVM: ARM: Enable vtimers with user space gic
Date: Fri, 16 Sep 2016 15:50:26 +0200 [thread overview]
Message-ID: <1474033826.7158.10.camel@redhat.com> (raw)
In-Reply-To: <20160916133027.GA27036@cbox>
Hi,
> That being said, I'm not categorically against these patches, but I
> share Marc's view that we've already seen that non-vgic support had been
> broken for multiple versions without anyone complaining,
Oh, did this ever work? Work as in "can actually run a virtual
machine", not as in "kvm doesn't throw an error on initialization".
> and without
> automated testing or substantial interest in the work, the patches
> really are likely to bit-rot.
Well, as far I know the rpi3 is the *only* aarch64 hardware which is
easily available and can (with these patches) run kvm.
More powerful stuff with more ram and sata storage and gbit network
(which I'd love to have to play with arm virt on real hardware) is
announced to be available really soon now since ... half a year at
least?
cheers,
Gerd
next prev parent reply other threads:[~2016-09-16 13:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 6:26 [PATCH v3 0/2] KVM: ARM: Enable vtimers with user space gic Alexander Graf
2016-09-16 6:26 ` [PATCH v3 1/2] KVM: arm/arm64: Add vcpu ENABLE_CAP functionality Alexander Graf
2016-09-16 6:26 ` [PATCH v3 2/2] KVM: arm/arm64: Route vtimer events to user space Alexander Graf
2016-09-16 9:11 ` Peter Maydell
2016-09-16 9:18 ` Alexander Graf
2016-09-16 10:20 ` [PATCH v3 0/2] KVM: ARM: Enable vtimers with user space gic Marc Zyngier
2016-09-16 12:18 ` Paolo Bonzini
2016-09-16 12:30 ` Christoffer Dall
2016-09-16 12:31 ` Paolo Bonzini
2016-09-16 13:30 ` Christoffer Dall
2016-09-16 13:46 ` Andrew Jones
2016-09-16 15:45 ` Paolo Bonzini
2016-09-16 19:36 ` Alexander Graf
2016-09-19 7:52 ` Andrew Jones
2016-09-19 11:45 ` Alexander Graf
2016-09-16 13:50 ` Gerd Hoffmann [this message]
2016-09-19 10:51 ` Alexander Graf
2016-09-19 11:41 ` Christoffer Dall
2016-09-16 12:25 ` Alexander Graf
2016-09-16 12:29 ` Christoffer Dall
2016-09-16 12:40 ` Paolo Bonzini
2016-09-16 12:44 ` Alexander Graf
2016-09-16 12:54 ` Paolo Bonzini
2016-09-17 15:28 ` Ard Biesheuvel
2016-09-17 15:38 ` Peter Maydell
2016-09-17 16:47 ` Ard Biesheuvel
2016-09-16 12:43 ` Alexander Graf
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=1474033826.7158.10.camel@redhat.com \
--to=kraxel@redhat.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).