qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"Bonzini, Paolo" <pbonzini@redhat.com>,
	mhartmay@linux.ibm.com,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	imbrenda@linux.ibm.com, Halil Pasic <pasic@linux.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>, Thomas Huth <thuth@redhat.com>,
	"open list:S390 SCLP-backed..." <qemu-s390x@nongnu.org>,
	seiden@linux.ibm.com
Subject: Re: [PATCH v3 10/14] linux header sync
Date: Thu, 21 Jul 2022 17:10:04 +0200	[thread overview]
Message-ID: <a78ca84f-f51a-9bcf-cce5-320f0442ba06@linux.ibm.com> (raw)
In-Reply-To: <CAMxuvazJW2zuVQRfoQqHXF6AZyuhqV_HMfLA0D973eu2-yCF1w@mail.gmail.com>

On 7/21/22 17:05, Marc-André Lureau wrote:
> On Thu, Jul 21, 2022 at 5:23 PM Janosch Frank <frankja@linux.ibm.com> wrote:
>>
>> Add the uapi data for KVM_CAP_S390_PROTECTED_DUMP which I expect to be
>> added with 5.20.
> 
> It's going to be overwritten by the next update-linux-headers.sh. I'd
> mark this patch as WIP or Draft: in the title until it's actually sync
> and imported from the kernel.

Yes, such patches are normally just ignored by maintainers as they 
provide their own sync patch that's why it doesn't have a proper subject 
or a WIP prefix. It's needed to be able to compile it until the proper 
sync has arrived.



> 
> 
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>>   linux-headers/linux/kvm.h | 54 +++++++++++++++++++++++++++++++++++++++
>>   1 file changed, 54 insertions(+)
>>
>> diff --git a/linux-headers/linux/kvm.h b/linux-headers/linux/kvm.h
>> index 0d05d02ee4..213216c27c 100644
>> --- a/linux-headers/linux/kvm.h
>> +++ b/linux-headers/linux/kvm.h
>> @@ -1150,6 +1150,7 @@ struct kvm_ppc_resize_hpt {
>>   #define KVM_CAP_DISABLE_QUIRKS2 213
>>   /* #define KVM_CAP_VM_TSC_CONTROL 214 */
>>   #define KVM_CAP_SYSTEM_EVENT_DATA 215
>> +#define KVM_CAP_S390_PROTECTED_DUMP 217
>>
>>   #ifdef KVM_CAP_IRQ_ROUTING
>>
>> @@ -1651,6 +1652,55 @@ struct kvm_s390_pv_unp {
>>          __u64 tweak;
>>   };
>>
>> +enum pv_cmd_info_id {
>> +       KVM_PV_INFO_VM,
>> +       KVM_PV_INFO_DUMP,
>> +};
>> +
>> +struct kvm_s390_pv_info_dump {
>> +       __u64 dump_cpu_buffer_len;
>> +       __u64 dump_config_mem_buffer_per_1m;
>> +       __u64 dump_config_finalize_len;
>> +};
>> +
>> +struct kvm_s390_pv_info_vm {
>> +       __u64 inst_calls_list[4];
>> +       __u64 max_cpus;
>> +       __u64 max_guests;
>> +       __u64 max_guest_addr;
>> +       __u64 feature_indication;
>> +};
>> +
>> +struct kvm_s390_pv_info_header {
>> +       __u32 id;
>> +       __u32 len_max;
>> +       __u32 len_written;
>> +       __u32 reserved;
>> +};
>> +
>> +struct kvm_s390_pv_info {
>> +       struct kvm_s390_pv_info_header header;
>> +       union {
>> +               struct kvm_s390_pv_info_dump dump;
>> +               struct kvm_s390_pv_info_vm vm;
>> +       };
>> +};
>> +
>> +enum pv_cmd_dmp_id {
>> +        KVM_PV_DUMP_INIT,
>> +        KVM_PV_DUMP_CONFIG_STATE,
>> +        KVM_PV_DUMP_COMPLETE,
>> +        KVM_PV_DUMP_CPU,
>> +};
>> +
>> +struct kvm_s390_pv_dmp {
>> +        __u64 subcmd;
>> +        __u64 buff_addr;
>> +        __u64 buff_len;
>> +        __u64 gaddr;
>> +        __u64 reserved[4];
>> +};
>> +
>>   enum pv_cmd_id {
>>          KVM_PV_ENABLE,
>>          KVM_PV_DISABLE,
>> @@ -1659,6 +1709,8 @@ enum pv_cmd_id {
>>          KVM_PV_VERIFY,
>>          KVM_PV_PREP_RESET,
>>          KVM_PV_UNSHARE_ALL,
>> +        KVM_PV_INFO,
>> +        KVM_PV_DUMP,
>>   };
>>
>>   struct kvm_pv_cmd {
>> @@ -2066,4 +2118,6 @@ struct kvm_stats_desc {
>>   /* Available with KVM_CAP_XSAVE2 */
>>   #define KVM_GET_XSAVE2           _IOR(KVMIO,  0xcf, struct kvm_xsave)
>>
>> +#define KVM_S390_PV_CPU_COMMAND _IOWR(KVMIO, 0xd0, struct kvm_pv_cmd)
>> +
>>   #endif /* __LINUX_KVM_H */
>> --
>> 2.34.1
>>
> 


  reply	other threads:[~2022-07-21 15:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 13:22 [PATCH v3 00/14] dump: Add arch section and s390x PV dump Janosch Frank
2022-07-21 13:22 ` [PATCH v3 01/14] dump: Introduce GuestPhysBlock offset and length filter functions Janosch Frank
2022-07-21 14:24   ` Marc-André Lureau
2022-07-21 13:22 ` [PATCH v3 02/14] dump: Rename write_elf_loads to write_elf_phdr_loads Janosch Frank
2022-07-21 14:26   ` Marc-André Lureau
2022-07-21 13:22 ` [PATCH v3 03/14] dump: Convert GuestPhysBlock iterators and use the filter functions Janosch Frank
2022-07-21 14:36   ` Marc-André Lureau
2022-07-21 16:26     ` Janosch Frank
2022-07-21 13:22 ` [PATCH v3 04/14] dump: Allocate header Janosch Frank
2022-07-21 14:38   ` Marc-André Lureau
2022-07-21 13:22 ` [PATCH v3 05/14] dump: Split write of section headers and data and add a prepare step Janosch Frank
2022-07-21 14:41   ` Marc-André Lureau
2022-07-21 14:59     ` Janosch Frank
2022-07-21 13:22 ` [PATCH v3 06/14] dump: Reorder struct DumpState Janosch Frank
2022-07-21 14:43   ` Marc-André Lureau
2022-07-21 13:22 ` [PATCH v3 07/14] dump: Swap segment and section header locations Janosch Frank
2022-07-21 15:07   ` Marc-André Lureau
2022-07-21 15:13     ` Janosch Frank
2022-07-21 13:22 ` [PATCH v3 08/14] dump/dump: Add section string table support Janosch Frank
2022-07-21 15:31   ` Janosch Frank
2022-07-21 13:22 ` [PATCH v3 09/14] dump/dump: Add arch section support Janosch Frank
2022-07-21 13:22 ` [PATCH v3 10/14] linux header sync Janosch Frank
2022-07-21 15:05   ` Marc-André Lureau
2022-07-21 15:10     ` Janosch Frank [this message]
2022-07-21 13:22 ` [PATCH v3 11/14] s390x: Add protected dump cap Janosch Frank
2022-07-22 11:45   ` Steffen Eiden
2022-07-21 13:22 ` [PATCH v3 12/14] s390x: Introduce PV query interface Janosch Frank
2022-07-22 11:46   ` Steffen Eiden
2022-07-21 13:22 ` [PATCH v3 13/14] s390x: Add KVM PV dump interface Janosch Frank
2022-07-22 11:46   ` Steffen Eiden
2022-07-21 13:22 ` [PATCH v3 14/14] s390x: pv: Add dump support Janosch Frank
2022-07-22 11:46   ` Steffen Eiden

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=a78ca84f-f51a-9bcf-cce5-320f0442ba06@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mhartmay@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=seiden@linux.ibm.com \
    --cc=thuth@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;
as well as URLs for NNTP newsgroup(s).