From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f171.google.com ([209.85.210.171]:39086 "EHLO mail-pf1-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732039AbfIIB2p (ORCPT ); Sun, 8 Sep 2019 21:28:45 -0400 Received: by mail-pf1-f171.google.com with SMTP id s12so8108539pfe.6 for ; Sun, 08 Sep 2019 18:28:44 -0700 (PDT) Date: Sun, 8 Sep 2019 18:28:37 -0700 From: Brendan Higgins Subject: Re: [RFC 03/19] ktf: Introduce a generic netlink protocol for test result communication Message-ID: <20190909012837.GA33048@google.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Knut Omang Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org, Shuah Khan , Jonathan Corbet , Masahiro Yamada , Michal Marek , Greg Kroah-Hartman , Shreyans Devendra Doshi <0xinfosect0r@gmail.com>, Alan Maguire , Kevin Hilman , Hidenori Yamaji , Frank Rowand , Timothy Bird , Luis Chamberlain , Theodore Ts'o , Daniel Vetter , Stephen Boyd On Tue, Aug 13, 2019 at 08:09:18AM +0200, Knut Omang wrote: > The generic netlink protocol used to communicate between > kernel and user space about tests and test results, as well as some > means for configuring tests within the kernel. > > Unlike other kernel side test code in the kernel, ktf does not print > anything from inside the kernel (except for optional debugging > features to help "internal" debugging of ktf or ktf tests). > Instead all test results are communicated back to the user space > frontend, which decides how to do the reporting. So why netlink? Why not just a file interface? [...] Cheers