From: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, patches@apm.com,
alex.bennee@linaro.org, kvmarm@lists.cs.columbia.edu,
christoffer.dall@linaro.org,
Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Subject: [Qemu-devel] [PATCH V2 0/2] Add virtio endianness determination in KVM ARM/ARM64
Date: Mon, 22 Dec 2014 14:34:55 +0530 [thread overview]
Message-ID: <1419239097-14758-1-git-send-email-pranavkumar@linaro.org> (raw)
In KVM ARM/ARM64 one can run cross-endian guset with respect to host kernel.
For virtio to work with this we need to make virtio code aware of
guest's endianness.
This patchset adds the guest endianness determination for KVM ARM/ARM64
and related small fix in KVM ARM64.
V2:
- Change the patch to be used generically for both ARM and ARM64.
- Define TARGET_IS_BIENDIAN for target-arm
- Address the review comments received in v1.
- Rebased code on top of latest qemu code.
V1:
- First patch in this series.
- http://lists.gnu.org/archive/html/qemu-devel/2014-10/msg03321.html
Pranavkumar Sawargaonkar (2):
target-arm: KVM64: Get and Sync up guest register state like kvm32.
target-arm: Guest cpu endianness determination for virtio KVM
ARM/ARM64
target-arm/cpu.c | 27 +++++++++++++++++++++++++++
target-arm/cpu.h | 2 ++
target-arm/kvm64.c | 12 ++++++++++++
3 files changed, 41 insertions(+)
--
1.9.1
next reply other threads:[~2014-12-22 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 9:04 Pranavkumar Sawargaonkar [this message]
2014-12-22 9:04 ` [Qemu-devel] [PATCH V2 1/2] target-arm: KVM64: Get and Sync up guest register state like kvm32 Pranavkumar Sawargaonkar
2015-01-05 13:28 ` Peter Maydell
2014-12-22 9:04 ` [Qemu-devel] [PATCH V2 2/2] target-arm: Guest cpu endianness determination for virtio KVM ARM/ARM64 Pranavkumar Sawargaonkar
2015-01-05 13:56 ` Peter Maydell
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=1419239097-14758-1-git-send-email-pranavkumar@linaro.org \
--to=pranavkumar@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@apm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).