From: Alexander Graf <agraf@suse.de>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
kvmarm@lists.cs.columbia.edu, patches@linaro.org,
Marc Zyngier <marc.zyngier@arm.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH v3] KVM: Specify byte order for KVM_EXIT_MMIO
Date: Wed, 29 Jan 2014 15:31:51 +0100 [thread overview]
Message-ID: <52E910D7.20202@suse.de> (raw)
In-Reply-To: <1390926522-18267-1-git-send-email-christoffer.dall@linaro.org>
On 01/28/2014 05:28 PM, Christoffer Dall wrote:
> The KVM API documentation is not clear about the semantics of the data
> field on the mmio struct on the kvm_run struct.
>
> This has become problematic when supporting ARM guests on big-endian
> host systems with guests of both endianness types, because it is unclear
> how the data should be exported to user space.
>
> This should not break with existing implementations as all supported
> existing implementations of known user space applications (QEMU and
> kvmtools for virtio) only support default endianness of the
> architectures on the host side.
>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Peter Maydell <peter.maydell@linaro.org>
> Cc: Alexander Graf <agraf@suse.de>
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Acked-by: Alexander Graf <agraf@suse.de>
Alex
next prev parent reply other threads:[~2014-01-29 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 16:28 [PATCH v3] KVM: Specify byte order for KVM_EXIT_MMIO Christoffer Dall
2014-01-29 14:31 ` Alexander Graf [this message]
2014-02-02 12:50 ` Peter Maydell
2014-02-02 21:02 ` Christoffer Dall
2014-03-14 4:27 ` Christoffer Dall
2014-03-17 19:00 ` Marc Zyngier
2014-03-29 14:45 ` Paolo Bonzini
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=52E910D7.20202@suse.de \
--to=agraf@suse.de \
--cc=christoffer.dall@linaro.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=patches@linaro.org \
--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 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).