From: James Hogan <james.hogan@imgtec.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: <qemu-devel@nongnu.org>, Leon Alrae <leon.alrae@imgtec.com>,
"Aurelien Jarno" <aurelien@aurel32.net>, <kvm@vger.kernel.org>,
<qemu-stable@nongnu.org>
Subject: Re: [PATCH 0/2] mips/kvm: Fixes for big endian & MIPS64 hosts
Date: Wed, 8 Jul 2015 16:03:25 +0100 [thread overview]
Message-ID: <559D3BBD.4040302@imgtec.com> (raw)
In-Reply-To: <1429871214-23514-1-git-send-email-james.hogan@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
Hi Paolo,
On 24/04/15 11:26, James Hogan wrote:
> A couple of small fixes for accessing 32-bit KVM registers on big
> endian, and to sign extend struct kvm_regs registers so as to work on
> MIPS64 hosts.
>
> James Hogan (2):
> mips/kvm: Fix Big endian 32-bit register access
> mips/kvm: Sign extend registers written to KVM
Any chance of applying these in time for v2.4?
Thanks
James
>
> target-mips/kvm.c | 21 +++++++--------------
> 1 file changed, 7 insertions(+), 14 deletions(-)
>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Leon Alrae <leon.alrae@imgtec.com>
> Cc: Aurelien Jarno <aurelien@aurel32.net>
> Cc: kvm@vger.kernel.org
> Cc: qemu-stable@nongnu.org
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-08 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 10:26 [PATCH 0/2] mips/kvm: Fixes for big endian & MIPS64 hosts James Hogan
2015-04-24 10:26 ` [PATCH 1/2] mips/kvm: Fix Big endian 32-bit register access James Hogan
2015-04-24 10:26 ` [PATCH 2/2] mips/kvm: Sign extend registers written to KVM James Hogan
2015-07-08 15:03 ` James Hogan [this message]
2015-07-08 15:22 ` [PATCH 0/2] mips/kvm: Fixes for big endian & MIPS64 hosts Paolo Bonzini
2015-07-09 8:13 ` Leon Alrae
2015-07-09 13:49 ` Paolo Bonzini
2015-07-09 13:58 ` [Qemu-devel] " Peter Maydell
2015-07-09 14:00 ` Peter Maydell
2015-07-09 14:00 ` 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=559D3BBD.4040302@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 \
--cc=qemu-stable@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).