Re: [PATCH v3 05/22] KVM: Add KVM_CAP_MEMORY_FAULT_INFO

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v3 05/22] KVM: Add KVM_CAP_MEMORY_FAULT_INFO
From: Robert Hoo <robert.hoo.linux@xxxxxxxxx>
Date: Fri, 21 Apr 2023 20:28:26 +0800
Cc: pbonzini@xxxxxxxxxx, maz@xxxxxxxxxx, oliver.upton@xxxxxxxxx, seanjc@xxxxxxxxxx, jthoughton@xxxxxxxxxx, bgardon@xxxxxxxxxx, dmatlack@xxxxxxxxxx, ricarkol@xxxxxxxxxx, axelrasmussen@xxxxxxxxxx, peterx@xxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, kvmarm@xxxxxxxxxxxxxxx
In-reply-to: <CAF7b7mopmS5dQEQSC4g5NVmDpfV7UJv2UursruROrr3kb=BQHQ@mail.gmail.com>
References: <20230412213510.1220557-1-amoorthy@google.com> <20230412213510.1220557-6-amoorthy@google.com> <a518e669-c758-57c8-3ba9-b4844e2cb79d@gmail.com> <CAF7b7mopmS5dQEQSC4g5NVmDpfV7UJv2UursruROrr3kb=BQHQ@mail.gmail.com>

Anish Moorthy <amoorthy@xxxxxxxxxx> 于2023年4月21日周五 02:10写道：
> > struct exit_reason[] string for KVM_EXIT_MEMORY_FAULT can be added as
> > well.
>
> Done, assuming you mean the exit_reasons_known definition in kvm_util.c

Yes.

References:
- [PATCH v3 00/22] Improve scalability of KVM + userfaultfd live migration via annotated memory faults.
  - From: Anish Moorthy
- [PATCH v3 05/22] KVM: Add KVM_CAP_MEMORY_FAULT_INFO
  - From: Anish Moorthy
- Re: [PATCH v3 05/22] KVM: Add KVM_CAP_MEMORY_FAULT_INFO
  - From: Hoo Robert
- Re: [PATCH v3 05/22] KVM: Add KVM_CAP_MEMORY_FAULT_INFO
  - From: Anish Moorthy

Prev by Date: Re: [PATCH v3 01/22] KVM: selftests: Allow many vCPUs and reader threads per UFFD in demand paging test
Next by Date: Re: RMRR device on non-Intel platform
Previous by thread: Re: [PATCH v3 05/22] KVM: Add KVM_CAP_MEMORY_FAULT_INFO
Next by thread: Re: [PATCH v3 05/22] KVM: Add KVM_CAP_MEMORY_FAULT_INFO
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]