[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <649AEBAC-8408-4BC0-AA22-F721CC23648D@amazon.de>
Date: Thu, 16 May 2019 15:14:16 +0000
From: "Sironi, Filippo" <sironi@...zon.de>
To: Boris Ostrovsky <boris.ostrovsky@...cle.com>
CC: "Graf, Alexander" <graf@...zon.com>,
Andrew Cooper <andrew.cooper3@...rix.com>,
LKML <linux-kernel@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"borntraeger@...ibm.com" <borntraeger@...ibm.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>
Subject: Re: [Xen-devel] [PATCH v2 1/2] KVM: Start populating /sys/hypervisor
with KVM entries
> On 16. May 2019, at 17:02, Boris Ostrovsky <boris.ostrovsky@...cle.com> wrote:
>
> On 5/16/19 10:08 AM, Alexander Graf wrote:
>>
>> My point is mostly that we should be as common
>> as possible when it comes to /sys/hypervisor, so that tools don't have
>> to care about the HV they're working against.
>
> It might make sense to have a common sys-hypervisor.c file
> (drivers/hypervisor/sys-hypervisor.c or some such), with
> hypervisor-specific ops/callbacks/etc.
>
> -boris
Yes, it definitely does. I would follow up with future patches to make it
happen.
Filippo
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrer: Christian Schlaeger, Ralf Herbrich
Ust-ID: DE 289 237 879
Eingetragen am Amtsgericht Charlottenburg HRB 149173 B
Powered by blists - more mailing lists