[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <926fdc5e-8ef2-0995-6a74-77b76af0905e@de.ibm.com>
Date: Tue, 14 May 2019 18:31:36 +0200
From: Christian Borntraeger <borntraeger@...ibm.com>
To: "Sironi, Filippo" <sironi@...zon.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
KVM list <kvm@...r.kernel.org>,
"boris.ostrovsky@...cle.com" <boris.ostrovsky@...cle.com>,
"cohuck@...hat.com" <cohuck@...hat.com>,
"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>,
"xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
"vasu.srinivasan@...cle.com" <vasu.srinivasan@...cle.com>
Subject: Re: [PATCH v2 1/2] KVM: Start populating /sys/hypervisor with KVM
entries
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.
Powered by blists - more mailing lists