[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a48080a5-7ece-280d-2c1f-9d3f4c273a8d@amazon.com>
Date: Mon, 19 Aug 2019 11:57:13 +0200
From: Alexander Graf <graf@...zon.com>
To: "Suthikulpanit, Suravee" <Suravee.Suthikulpanit@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
CC: "pbonzini@...hat.com" <pbonzini@...hat.com>,
"rkrcmar@...hat.com" <rkrcmar@...hat.com>,
"joro@...tes.org" <joro@...tes.org>,
"jschoenh@...zon.de" <jschoenh@...zon.de>,
"karahmed@...zon.de" <karahmed@...zon.de>,
"rimasluk@...zon.com" <rimasluk@...zon.com>,
"Grimm, Jon" <Jon.Grimm@....com>
Subject: Re: [PATCH v2 04/15] kvm: x86: Add per-VM APICv state debugfs
On 15.08.19 18:25, Suthikulpanit, Suravee wrote:
> Currently, there is no way to tell whether APICv is active
> on a particular VM. This often cause confusion since APICv
> can be deactivated at runtime.
>
> Introduce a debugfs entry to report APICv state of a VM.
> This creates a read-only file:
>
> /sys/kernel/debug/kvm/70860-14/apicv-state
>
> Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@....com>
Shouldn't this first and foremost be a VM ioctl so that user space can
inquire its own state?
Alex
Powered by blists - more mailing lists