linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sironi, Filippo" <sironi@amazon.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: "Graf, Alexander" <graf@amazon.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"borntraeger@de.ibm.com" <borntraeger@de.ibm.com>,
	"cohuck@redhat.com" <cohuck@redhat.com>,
	"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH v2 1/2] KVM: Start populating /sys/hypervisor with KVM entries
Date: Thu, 16 May 2019 15:14:16 +0000	[thread overview]
Message-ID: <649AEBAC-8408-4BC0-AA22-F721CC23648D@amazon.de> (raw)
In-Reply-To: <92f2f186-2e29-d798-84bd-7209e874f103@oracle.com>


> On 16. May 2019, at 17:02, Boris Ostrovsky <boris.ostrovsky@oracle.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



  reply	other threads:[~2019-05-16 15:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09  9:54 [PATCH] KVM: Start populating /sys/hypervisor with KVM entries Filippo Sironi
2018-10-09 10:41 ` Christian Borntraeger
2018-10-09 16:21   ` Boris Ostrovsky
2018-10-09 17:50     ` Cornelia Huck
2018-10-09 15:00 ` Konrad Rzeszutek Wilk
2018-10-10  5:19 ` kbuild test robot
2019-05-14 15:16 ` Filippo Sironi
2019-05-14 15:16   ` [PATCH v2 1/2] " Filippo Sironi
2019-05-14 15:26     ` Christian Borntraeger
2019-05-14 16:09       ` Sironi, Filippo
2019-05-14 16:31         ` Christian Borntraeger
2019-05-14 22:08         ` Sironi, Filippo
2019-05-16 13:50     ` Alexander Graf
2019-05-16 14:02       ` [Xen-devel] " Andrew Cooper
2019-05-16 14:08         ` Alexander Graf
2019-05-16 15:02           ` Boris Ostrovsky
2019-05-16 15:14             ` Sironi, Filippo [this message]
2019-05-17 15:41       ` Sironi, Filippo
2019-05-31  9:06         ` Alexander Graf
2019-05-31  9:12           ` Raslan, KarimAllah
2019-05-31  9:26             ` Alexander Graf
2019-05-31  9:38             ` Marc Zyngier
2019-05-14 15:16   ` [PATCH v2 2/2] KVM: x86: Implement the arch-specific hook to report the VM UUID Filippo Sironi
2019-05-16 13:56     ` Alexander Graf
2019-05-16 15:25       ` Sironi, Filippo
2019-05-16 15:33         ` Alexander Graf
2019-05-16 16:40           ` Boris Ostrovsky
2019-05-16 17:41             ` Sironi, Filippo
2019-05-16 17:49               ` Alexander Graf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=649AEBAC-8408-4BC0-AA22-F721CC23648D@amazon.de \
    --to=sironi@amazon.de \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=graf@amazon.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).