From: James Hogan <james.hogan@imgtec.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: James Hogan <james.hogan@imgtec.com>,
Leon Alrae <leon.alrae@imgtec.com>,
kvm@vger.kernel.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] [PATCH v2 0/9] mips/kvm: Support FPU & SIMD (MSA) in MIPS KVM guests
Date: Wed, 25 Mar 2015 10:23:45 +0000 [thread overview]
Message-ID: <1427279034-9459-1-git-send-email-james.hogan@imgtec.com> (raw)
Review on v1 has gone quiet, so here's v2 which addresses the feedback
received for v1. Thanks to all who have taken the time to review it so
far.
This patchset primarily adds support for FPU and MIPS SIMD Architecture
(MSA) in MIPS KVM guests to QEMU. It depends on the KVM patchset which I
recently submitted to add the corresponding hypervisor support to KVM
("[PATCH 00/20] MIPS: KVM: Guest FPU & SIMD (MSA) support").
All comments welcome.
Changes in v2:
- Moved most of patch 7 and updates to linux-headers/linux/kvm.h from
patches 8 and 9 into a new patch 1, which is purely for reference
(Paolo).
- Add the changes to MIPS_CP0_{32,64} macros from v1 patch 7 to patch 2,
since the rest of that patch is now unnecessary and the change is
along the same lines as patch 2 (not added Leon's Reviewed-by to this
patch due to that non-reviewed change).
- Fix line wrapping of kvm_mips_get_one_reg() calls from Config4 and
Config5 in patch 5 (Leon).
- Change (1 << x) to (1U << x) in important places in patch 5, 8 & 9 to
avoid compiler defined behaviour (Leon).
James Hogan (9):
DONT APPLY: linux-headers: Update MIPS KVM headers
mips/kvm: Sync with newer MIPS KVM headers
mips/kvm: Remove a couple of noisy DPRINTFs
mips/kvm: Implement PRid CP0 register
mips/kvm: Implement Config CP0 registers
mips/kvm: Support unsigned KVM registers
mips/kvm: Support signed 64-bit KVM registers
mips/kvm: Support FPU in MIPS KVM guests
mips/kvm: Support MSA in MIPS KVM guests
linux-headers/asm-mips/kvm.h | 160 ++++++++++-------
linux-headers/linux/kvm.h | 2 +
target-mips/cpu.h | 2 +
target-mips/kvm.c | 410 ++++++++++++++++++++++++++++++++++++++++---
4 files changed, 487 insertions(+), 87 deletions(-)
--
2.0.5
next reply other threads:[~2015-03-25 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 10:23 James Hogan [this message]
2015-03-25 10:23 ` [Qemu-devel] [PATCH v2 1/9] DONT APPLY: linux-headers: Update MIPS KVM headers James Hogan
2015-03-25 10:23 ` [Qemu-devel] [PATCH v2 2/9] mips/kvm: Sync with newer " James Hogan
2015-03-25 10:23 ` [Qemu-devel] [PATCH v2 3/9] mips/kvm: Remove a couple of noisy DPRINTFs James Hogan
2015-03-25 10:23 ` [Qemu-devel] [PATCH v2 4/9] mips/kvm: Implement PRid CP0 register James Hogan
2015-03-25 10:23 ` [Qemu-devel] [PATCH v2 5/9] mips/kvm: Implement Config CP0 registers James Hogan
2015-03-25 10:23 ` [Qemu-devel] [PATCH v2 6/9] mips/kvm: Support unsigned KVM registers James Hogan
2015-04-24 10:39 ` [Qemu-devel] [PATCH v3 " James Hogan
2015-03-25 10:23 ` [Qemu-devel] [PATCH v2 7/9] mips/kvm: Support signed 64-bit " James Hogan
2015-03-25 10:23 ` [Qemu-devel] [PATCH v2 8/9] mips/kvm: Support FPU in MIPS KVM guests James Hogan
2015-03-25 10:23 ` [Qemu-devel] [PATCH v2 9/9] mips/kvm: Support MSA " James Hogan
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=1427279034-9459-1-git-send-email-james.hogan@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=aurelien@aurel32.net \
--cc=kvm@vger.kernel.org \
--cc=leon.alrae@imgtec.com \
--cc=pbonzini@redhat.com \
--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).