Re: [PATCH v2 1/2] KVM: Start populating /sys/hypervisor with KVM entries

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

Subject: Re: [PATCH v2 1/2] KVM: Start populating /sys/hypervisor with KVM entries
From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
Date: Tue, 14 May 2019 18:31:36 +0200
Cc: LKML <linux-kernel@xxxxxxxxxxxxxxx>, KVM list <kvm@xxxxxxxxxxxxxxx>, "boris.ostrovsky@xxxxxxxxxx" <boris.ostrovsky@xxxxxxxxxx>, "cohuck@xxxxxxxxxx" <cohuck@xxxxxxxxxx>, "konrad.wilk@xxxxxxxxxx" <konrad.wilk@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "vasu.srinivasan@xxxxxxxxxx" <vasu.srinivasan@xxxxxxxxxx>
In-reply-to: <56DAB9BD-2543-49DA-9886-C9C8F2B814F9@amazon.de>
Openpgp: preference=signencrypt
References: <1539078879-4372-1-git-send-email-sironi@amazon.de> <1557847002-23519-1-git-send-email-sironi@amazon.de> <1557847002-23519-2-git-send-email-sironi@amazon.de> <d03f6be5-d8dc-4389-e14c-295f36a68827@de.ibm.com> <56DAB9BD-2543-49DA-9886-C9C8F2B814F9@amazon.de>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1


On 14.05.19 18:09, Sironi, Filippo wrote:

>> Isnt kvm_para_available a function that is defined in the context of the HOST
>> and not of the guest?
> 
> No, kvm_para_available is defined in the guest context.
> On x86, it checks for the presence of the KVM CPUID leafs.
> 

Right you are, I mixed that up.

References:
- [PATCH] KVM: Start populating /sys/hypervisor with KVM entries
  - From: Filippo Sironi
- KVM: Start populating /sys/hypervisor with KVM entries
  - From: Filippo Sironi
- [PATCH v2 1/2] KVM: Start populating /sys/hypervisor with KVM entries
  - From: Filippo Sironi
- Re: [PATCH v2 1/2] KVM: Start populating /sys/hypervisor with KVM entries
  - From: Christian Borntraeger
- Re: [PATCH v2 1/2] KVM: Start populating /sys/hypervisor with KVM entries
  - From: Sironi, Filippo

Prev by Date: Re: [RFC KVM 18/27] kvm/isolation: function to copy page table entries for percpu buffer
Next by Date: Re: [PATCH v2 1/8] vsock/virtio: limit the memory used per-socket
Previous by thread: Re: [PATCH v2 1/2] KVM: Start populating /sys/hypervisor with KVM entries
Next by thread: Re: [PATCH v2 1/2] KVM: Start populating /sys/hypervisor with KVM entries
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]