From: Leon Alrae <leon.alrae@imgtec.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
James Hogan <james.hogan@imgtec.com>
Cc: qemu-stable@nongnu.org, qemu-devel@nongnu.org,
Aurelien Jarno <aurelien@aurel32.net>,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/2] mips/kvm: Fixes for big endian & MIPS64 hosts
Date: Thu, 9 Jul 2015 09:13:09 +0100 [thread overview]
Message-ID: <559E2D15.7040905@imgtec.com> (raw)
In-Reply-To: <559D403A.80307@redhat.com>
On 08/07/2015 16:22, Paolo Bonzini wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
>
> On 08/07/2015 17:03, James Hogan wrote:
>> 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?
>
> I had assumed they'd go through Leon, but I can apply them for 2.4-rc1
> as well.
I thought these changes would get applied via kvm queue since they touch
target-mips/kvm.c only. But if such target-specific kvm patches usually go via
target-* tree then I'm happy to pick them up.
Leon
next prev parent reply other threads:[~2015-07-09 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 10:26 [Qemu-devel] [PATCH 0/2] mips/kvm: Fixes for big endian & MIPS64 hosts James Hogan
2015-04-24 10:26 ` [Qemu-devel] [PATCH 1/2] mips/kvm: Fix Big endian 32-bit register access James Hogan
2015-04-24 10:26 ` [Qemu-devel] [PATCH 2/2] mips/kvm: Sign extend registers written to KVM James Hogan
2015-07-08 15:03 ` [Qemu-devel] [PATCH 0/2] mips/kvm: Fixes for big endian & MIPS64 hosts James Hogan
2015-07-08 15:22 ` Paolo Bonzini
2015-07-09 8:13 ` Leon Alrae [this message]
2015-07-09 13:49 ` Paolo Bonzini
2015-07-09 13:58 ` 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=559E2D15.7040905@imgtec.com \
--to=leon.alrae@imgtec.com \
--cc=aurelien@aurel32.net \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--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).