From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Christoffer Dall <christoffer.dall@linaro.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [PATCH 2/3] arm/arm64: KVM: MMIO support for BE guest
Date: Mon, 11 Nov 2013 19:05:00 +0100 [thread overview]
Message-ID: <52811C4C.3060708@redhat.com> (raw)
In-Reply-To: <CAFEAcA_8EPBscwnqudXU+qj3Z2Tbm=_Q9zeo=AwnkdVH6iRtSw@mail.gmail.com>
Il 11/11/2013 19:03, Peter Maydell ha scritto:
>> How does this patch affect guest
>> ABI, and is guest ABI not yet considered stable for KVM ARM?
>
> QEMU currently insists on 4 CPUs max for A15, so the
> question doesn't come up in that case.
Still, does the guest ABI not matter only for kvmtool, or also for QEMU?
Paolo
next prev parent reply other threads:[~2013-11-11 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 10:07 [GIT PULL] KVM/arm64 fixes for 3.13 Marc Zyngier
2013-11-08 10:07 ` [PATCH 1/3] arm64: KVM: Yield CPU when vcpu executes a WFE Marc Zyngier
2013-11-08 10:07 ` [PATCH 2/3] arm/arm64: KVM: MMIO support for BE guest Marc Zyngier
2013-11-11 11:04 ` Paolo Bonzini
2013-11-11 14:56 ` Christoffer Dall
2013-11-11 15:10 ` Paolo Bonzini
2013-11-11 15:49 ` Christoffer Dall
2013-11-11 17:56 ` Paolo Bonzini
2013-11-11 18:03 ` Peter Maydell
2013-11-11 18:05 ` Paolo Bonzini [this message]
2013-11-11 18:26 ` Marc Zyngier
2013-11-11 18:41 ` Christoffer Dall
2013-11-11 18:41 ` Paolo Bonzini
2013-11-12 9:41 ` Andrew Jones
2013-11-12 10:03 ` Marc Zyngier
2013-11-12 10:07 ` Paolo Bonzini
2013-11-12 16:30 ` Christoffer Dall
2013-11-11 18:39 ` Christoffer Dall
2013-11-08 10:07 ` [PATCH 3/3] arm/arm64: KVM: PSCI: propagate caller endianness to the incoming vcpu 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=52811C4C.3060708@redhat.com \
--to=pbonzini@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=peter.maydell@linaro.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.