From: Paolo Bonzini <pbonzini@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, guang.zeng@intel.com, jing2.liu@intel.com,
kevin.tian@intel.com, seanjc@google.com, tglx@linutronix.de,
wei.w.wang@intel.com, yang.zhong@intel.com
Subject: Re: [PATCH] kvm: Move KVM_GET_XSAVE2 IOCTL definition at the end of kvm.h
Date: Mon, 31 Jan 2022 15:22:17 +0100 [thread overview]
Message-ID: <8396dda5-d82c-8b5d-f94e-28ba84ec422d@redhat.com> (raw)
In-Reply-To: <20220128154025.102666-1-frankja@linux.ibm.com>
On 1/28/22 16:40, Janosch Frank wrote:
> This way we can more easily find the next free IOCTL number when
> adding new IOCTLs.
>
> Fixes: be50b2065dfa ("kvm: x86: Add support for getting/setting expanded xstate buffer")
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> include/uapi/linux/kvm.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
> index 9563d294f181..efe81fef25eb 100644
> --- a/include/uapi/linux/kvm.h
> +++ b/include/uapi/linux/kvm.h
> @@ -1623,9 +1623,6 @@ struct kvm_enc_region {
> #define KVM_S390_NORMAL_RESET _IO(KVMIO, 0xc3)
> #define KVM_S390_CLEAR_RESET _IO(KVMIO, 0xc4)
>
> -/* Available with KVM_CAP_XSAVE2 */
> -#define KVM_GET_XSAVE2 _IOR(KVMIO, 0xcf, struct kvm_xsave)
> -
> struct kvm_s390_pv_sec_parm {
> __u64 origin;
> __u64 length;
> @@ -2047,4 +2044,7 @@ struct kvm_stats_desc {
>
> #define KVM_GET_STATS_FD _IO(KVMIO, 0xce)
>
> +/* Available with KVM_CAP_XSAVE2 */
> +#define KVM_GET_XSAVE2 _IOR(KVMIO, 0xcf, struct kvm_xsave)
> +
> #endif /* __LINUX_KVM_H */
Queued, thanks.
prev parent reply other threads:[~2022-01-31 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 15:40 [PATCH] kvm: Move KVM_GET_XSAVE2 IOCTL definition at the end of kvm.h Janosch Frank
2022-01-29 1:35 ` Wang, Wei W
2022-01-31 6:28 ` Janosch Frank
2022-01-31 14:22 ` 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=8396dda5-d82c-8b5d-f94e-28ba84ec422d@redhat.com \
--to=pbonzini@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=guang.zeng@intel.com \
--cc=jing2.liu@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=wei.w.wang@intel.com \
--cc=yang.zhong@intel.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;
as well as URLs for NNTP newsgroup(s).