From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753433AbdFMQYV (ORCPT ); Tue, 13 Jun 2017 12:24:21 -0400 Received: from bombadil.infradead.org ([65.50.211.133]:33046 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750899AbdFMQYT (ORCPT ); Tue, 13 Jun 2017 12:24:19 -0400 Date: Tue, 13 Jun 2017 09:24:14 -0700 From: Darren Hart To: Greg Kroah-Hartman Cc: Pali =?iso-8859-1?Q?Roh=E1r?= , Christoph Hellwig , Linus Torvalds , Mario Limonciello , Andy Shevchenko , Rafael Wysocki , Andy Lutomirski , LKML , platform-driver-x86@vger.kernel.org Subject: Re: WMI and Kernel:User interface Message-ID: <20170613162414.GG27850@fury> References: <20170509231639.GB11404@fury> <201706101236.40663@pali> <20170612170249.GA27850@fury> <201706130017.29023@pali> <20170613012435.GB27850@fury> <20170613070535.GA13252@infradead.org> <20170613120741.GG5248@pali> <20170613154419.GD27850@fury> <20170613160547.GA25404@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170613160547.GA25404@kroah.com> User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 13, 2017 at 06:05:47PM +0200, Greg Kroah-Hartman wrote: > On Tue, Jun 13, 2017 at 08:44:19AM -0700, Darren Hart wrote: > > > In some cases filter function can be simple in some cases hard. I can > > > image that usage of while listing, plus in some cases also filtering > > > (when it would be relatively easy to implement). > > > > See my response to Christoph - to address the concern of breaking userspace > > later, if we consider this a proxy instead of a filter, we can make it > > transparent to userspace and maintain kernel driver state. The driver can > > register a wmi_method_proxy callback which can choose to proxy the method call > > or not. If it does, it can update it's own state and perform the requested > > action through it's own infrastructure, populate the out buffer and send it back > > up to userspace. I would hope to see as few of these as possible, but they would > > allow for protecting the kernel drivers while still enabling userspace usage of > > WMI. > > Ok, I think we need to see some real code here to get any further with > this. There's a reason we don't do big design discussions without > patches, as that usually answers all of the questions involved. > > Please, let's see some code before anything else. Agreed. That was my intent earlier with getting the chardev and calling conventions established. -- Darren Hart VMware Open Source Technology Center