[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75dc4403-cc07-0f99-00ec-86f61092fff9@redhat.com>
Date: Tue, 26 Nov 2019 11:50:29 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: KVM list <kvm@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Christian Borntraeger <borntraeger@...ibm.com>,
Alex Williamson <alex.williamson@...hat.com>,
Peter Feiner <pfeiner@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: "statsfs" API design
On 26/11/19 11:09, Greg Kroah-Hartman wrote:
> So I think there are two different things here:
> - a simple data structure for in-kernel users of statistics
> - a way to export statistics to userspace
>
> Now if they both can be solved with the same "solution", wonderful! But
> don't think that you have to do both of these at the same time.
>
> Which one are you trying to solve here, I can't figure it out. Is it
> the second one?
I already have the second in KVM using debugfs, but that's not good. So
I want to do:
- a simple data structure for in-kernel *publishers* of statistics
- a sysfs-based interface to export it to userspace, which looks a lot
like KVM's debugfs-based statistics.
What we don't have to do at the same time, is a new interface to
userspace, one that is more efficient while keeping the self-describing
property that we agree is needed. That is also planned, but would come
later.
Paolo
Powered by blists - more mailing lists