From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752013AbdF3QeJ (ORCPT ); Fri, 30 Jun 2017 12:34:09 -0400 Received: from resqmta-po-06v.sys.comcast.net ([96.114.154.165]:52022 "EHLO resqmta-po-06v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751722AbdF3Qdt (ORCPT ); Fri, 30 Jun 2017 12:33:49 -0400 Reply-To: shuah@kernel.org Subject: Re: [PATCH 0/4] Convert to TAP13 using ksft_ var arg msg api To: Paul Elder , alice.ferrazzi@gmail.com, gregkh@linuxfoundation.org, labath@google.com, panand@redhat.com, will.deacon@arm.com Cc: Shuah Khan , linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org, Shuah Khan References: <6fb6618f-7f39-dd6b-07bb-0e7e9929e6e1@pitt.edu> From: Shuah Khan Message-ID: <3d5e18c0-781d-b9d3-c9df-c02e62ded88d@kernel.org> Date: Fri, 30 Jun 2017 10:33:47 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <6fb6618f-7f39-dd6b-07bb-0e7e9929e6e1@pitt.edu> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfDqzi2NT7YoA1UFr5vXnFMi2d9rV3H5BWT3jE6yP2iC+yK6vsTVRZLOPgeysswh+9YYntHFnxxj2hSBNtUqllPbUUHZQx/B5iqw0ZLh9hERujH3SKR3K PCQjiCXtCucmJrLQt4uoGAYJAP7phv6cGqmer0+insG8gRvsI1cBLRYhjjbJsPHvIDE2pRhEdcxRsmjxtBSSUaNju5pIPhbTYJ29Rgaa2eNdm85JoUFxtWpi Xxa/GXjPM0KIg0viR06lUAJHXTHBz+N3tCGaYgkvrI4S10ggD8QAaNpYhPpin0IXkwIbNxybIkhegBnzH2gLvn/gwEFYS55hVAEc/XVbxVQVkIHyfr2L+GDo frIXlNCWADJYJagHxFpPNAhCYOxlmlOH+nw5cOKIBnrtGH4W2SKUHvQSh2/U+zeDuk8WpqVvbPJ8v5p++tBQIdUVYxlxCZAgzVsKnl1ASa4X7xNZyFmVgyrh GRfI3eKcO+7QZ2bj Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/30/2017 10:13 AM, Paul Elder wrote: > On 06/30/2017 08:18 AM, Shuah Khan wrote: >> This patch series converts breakpoint_test_arm64 to TAP13 output. Uses >> ksft_ var arg msg functions as needed. Changed to ensure parent is the >> one that increments test counters. >> >> breakpoint_test, step_after_suspend_test, membarrier tests are changed >> to use ksft_ var arg msg functions as needed. >> >> This patch series depends on Paul Elder's >> >> [PATCH v2 0/2] kselftest: make ksft_* output functions variadic >> The v2 series doesn't append newline and makes it easier to use. >> >> Shuah Khan (4): >> selftests: breakpoint_test: use ksft_* var arg msg api >> selftests: breakpoints: step_after_suspend_test use ksft_* var arg msg >> api >> selftests: breakpoints: breakpoint_test_arm64: convert test to use >> TAP13 >> selftests: membarrier: use ksft_* var arg msg api >> >> .../selftests/breakpoints/breakpoint_test.c | 28 ++++--- >> .../selftests/breakpoints/breakpoint_test_arm64.c | 94 +++++++++++++--------- >> .../breakpoints/step_after_suspend_test.c | 59 ++++++++------ >> .../testing/selftests/membarrier/membarrier_test.c | 91 ++++++++++----------- >> 4 files changed, 148 insertions(+), 124 deletions(-) >> > Looks good to me. > > Although I am wondering why you said earlier that you were going to go with > my v1, while this depends on v2. > > Thank you, > > Paul > > Yeah my bad! I was playing with both v1 and v2 for my testing. I lost track of which one worked well. I had to start from square one and re-test. v2 by not appending newline, allows custom formats in individual test messages. For example, a test wants to use tabs between two ksft_print_msg() calls or _report_ messages. v2 is flexible and works better and leds itself well. Users can just pass the format and expect it to stick. If there are no issues with this series, I plan to apply your v2 series and this series later on today or early tomorrow to linux-kselftest next. If we have this infrastructure in place, we will be able to make progress in the next release with the TAP13 conversion of other tests. thanks, -- Shuah thanks, -- Shuah