public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ken Hofsass <hofsass@google.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, david@redhat.com, jmattson@google.com,
	Ken Hofsass <hofsass@google.com>
Subject: [PATCH v4 0/2] KVM: x86: Add SYNC REGS functionality.
Date: Wed, 31 Jan 2018 16:03:34 -0800	[thread overview]
Message-ID: <20180201000336.154170-1-hofsass@google.com> (raw)

This patch set adds KVM_CAP_SYNC_REGS functionality for x86.

Changes from v3 <https://www.spinics.net/lists/kvm/msg162834.html>
SYNC_REGS_SIZE_BYTES patch (1/2)
- No changes.
KVM_CAP_SYNC_REGS patch (2/2)
- KVM_SYNC_X86_NUM_FIELDS removed.
- Avoid overwriting error code in kvm_arch_vcpu_ioctl_run.
- Shortened __kvm_arch_vcpu_ioctl_{{set,get}_{sregs,regs}
  to __{set,get}_{sregs,regs}.
- Renamed sync_regs/store_regs to match s390.

Changes from v2 <https://patchwork.kernel.org/patch/10161941/>
- v3 splits v2 changes into two separate patches, moving
  SYNC_REGS_SIZE_BYTES #define change to its own patch.
- Refactors kvm_arch_vcpu_ioctl_set_{regs,sregs} to avoid
  redundant calls to both vcpu_load and vcpu_put in their
  usage by sync regs code.

Please see the individual patches for details.

Ken Hofsass (2):
  KVM: x86: add SYNC_REGS_SIZE_BYTES #define.
  KVM: x86: KVM_CAP_SYNC_REGS

 Documentation/virtual/kvm/api.txt |  42 ++++++++++++++-
 arch/x86/include/uapi/asm/kvm.h   |  19 ++++++-
 arch/x86/kvm/x86.c                | 108 +++++++++++++++++++++++++++++++++-----
 include/uapi/linux/kvm.h          |   6 ++-
 4 files changed, 158 insertions(+), 17 deletions(-)

-- 
2.16.0.rc1.238.g530d649a79-goog

             reply	other threads:[~2018-02-01  0:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01  0:03 Ken Hofsass [this message]
2018-02-01  0:03 ` [PATCH v4 1/2] KVM: x86: add SYNC_REGS_SIZE_BYTES #define Ken Hofsass
2018-02-01  0:03 ` [PATCH v4 2/2] KVM: x86: KVM_CAP_SYNC_REGS Ken Hofsass
2018-02-01 13:05   ` David Hildenbrand
2018-02-02 21:04     ` Radim Krčmář
2018-02-02 23:54       ` Ken Hofsass
2018-02-05  1:29   ` Wanpeng Li
2018-02-06  0:32     ` Ken Hofsass
2018-02-06  0:46       ` Wanpeng Li
2018-02-06 20:03         ` Ken Hofsass

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=20180201000336.154170-1-hofsass@google.com \
    --to=hofsass@google.com \
    --cc=david@redhat.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.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