public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
	kvm@vger.kernel.org, Sanjay Lal <sanjayl@kymasys.com>,
	Gleb Natapov <gleb@redhat.com>,
	linux-kernel@vger.kernel.org,
	David Daney <david.daney@cavium.com>
Subject: Re: [PATCH 0/2] kvm/mips: ABI fix for 3.10
Date: Mon, 17 Jun 2013 17:26:04 +0200	[thread overview]
Message-ID: <51BF2A8C.5020903@redhat.com> (raw)
In-Reply-To: <1370892828-21676-1-git-send-email-ddaney.cavm@gmail.com>

Il 10/06/2013 21:33, David Daney ha scritto:
> From: David Daney <david.daney@cavium.com>
> 
> As requested by Gleb Natapov, we need to define and use KVM_REG_MIPS
> when using the GET_ONE_REG/SET_ONE_REG ioctl.  Since this is part of
> the MIPS kvm support that is new in 3.10, it should be merged before a
> bad ABI leaks out into an 'official' kernel release.
> 
> David Daney (2):
>   kvm: Add definition of KVM_REG_MIPS
>   mips/kvm: Use KVM_REG_MIPS and proper size indicators for *_ONE_REG
> 
>  arch/mips/include/uapi/asm/kvm.h | 81 +++++++++++++++++++--------------------
>  arch/mips/kvm/kvm_mips.c         | 83 ++++++++++++++++++++++++++--------------
>  include/uapi/linux/kvm.h         |  1 +
>  3 files changed, 94 insertions(+), 71 deletions(-)
> 

CCed people probably already know, but anyway: this is already in
Linus's tree (commit af180b81a3f4ea925fae88878f367e676e99bf73).

Paolo

      parent reply	other threads:[~2013-06-17 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 19:33 [PATCH 0/2] kvm/mips: ABI fix for 3.10 David Daney
2013-06-10 19:33 ` [PATCH 1/2] kvm: Add definition of KVM_REG_MIPS David Daney
2013-06-10 19:33 ` [PATCH 2/2] mips/kvm: Use KVM_REG_MIPS and proper size indicators for *_ONE_REG David Daney
2013-06-17 15:26 ` Paolo Bonzini [this message]

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=51BF2A8C.5020903@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=david.daney@cavium.com \
    --cc=ddaney.cavm@gmail.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=sanjayl@kymasys.com \
    /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