Re: [RFC PATCH v3 13/59] KVM: Add max_vcpus field in common 'struct kvm'

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

Subject: Re: [RFC PATCH v3 13/59] KVM: Add max_vcpus field in common 'struct kvm'
From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Date: Thu, 25 Nov 2021 20:06:26 +0100
Cc: isaku.yamahata@xxxxxxxxx, isaku.yamahata@xxxxxxxxx, Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
In-reply-to: <cb707c90542c9ad4768dae88c80fefcc15a264d6.1637799475.git.isaku.yamahata@intel.com>
References: <cover.1637799475.git.isaku.yamahata@intel.com> <cb707c90542c9ad4768dae88c80fefcc15a264d6.1637799475.git.isaku.yamahata@intel.com>

On Wed, Nov 24 2021 at 16:19, isaku yamahata wrote:
> From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>

Why?

References:
- [RFC PATCH v3 00/59] KVM: X86: TDX support
  - From: isaku . yamahata
- [RFC PATCH v3 13/59] KVM: Add max_vcpus field in common 'struct kvm'
  - From: isaku . yamahata

Prev by Date: Re: [RFC PATCH v3 12/59] KVM: x86/mmu: Zap only leaf SPTEs for deleted/moved memslot by default
Next by Date: Re: [RFC PATCH v3 14/59] KVM: x86: Add vm_type to differentiate legacy VMs from protected VMs
Previous by thread: [RFC PATCH v3 13/59] KVM: Add max_vcpus field in common 'struct kvm'
Next by thread: [RFC PATCH v3 15/59] KVM: x86: Introduce "protected guest" concept and block disallowed ioctls
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]

Powered by Linux