ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] kernel testing standard
Date: Fri, 06 Jun 2014 18:10:12 +0900	[thread overview]
Message-ID: <53918574.3090307@hitachi.com> (raw)
In-Reply-To: <CAKMK7uGNyXrRuRj0p_zRVdsjs-kcvW-+VTJWkEUc7Cqu-SNjCw@mail.gmail.com>

(2014/06/05 20:58), Daniel Vetter wrote:
> On Thu, Jun 5, 2014 at 1:17 PM, Masami Hiramatsu
> <masami.hiramatsu.pt@hitachi.com> wrote:
>> (2014/06/05 17:53), Daniel Vetter wrote:
>>> On Thu, Jun 5, 2014 at 10:30 AM, Geert Uytterhoeven
>>> <geert@linux-m68k.org> wrote:
>>>> On Thu, Jun 5, 2014 at 8:54 AM, Mel Gorman <mgorman@suse.de> wrote:
>>>>> There is a hazard that someone bisecting the tree would need to be careful
>>>>> to not bisect LTP instead.
>>>>
>>>> That may actually be a good reason not to import LTP...
>>>> I'd imagine you usually want to bisect the kernel to find when a regression
>>>> was introduced in the syscall API.
>>>>
>>>> Is there a reason not to run the latest version of LTP (unless bisecting
>>>> LTP ;-)? The syscall API is supposed to be stable.
>>>
>>> Same for validating backports - you want the latest testsuite to make
>>> sure you don't miss important fixes. Downside is that the testsuite
>>> needs to be compatible over a much wider range of kernels to be
>>> useful, which is a pain for e.g. checking that garbage in reserved
>>> fields (like reserved flags) are properly rejected on each kernel
>>> version.
>>
>> Perhaps, the testsuite can recognize which patch is merged or not
>> if it can access the git repository by "git log | grep <commit-id>"
>> or something like that. Then, it can self-configure to reject
>> non-supported test. :)
> 
> Well we have feature flags and stuff (need them anyway) and magic
> macros to skip tests if something isn't there/supported. So (at least
> for us) not a technical issue at all.

Nice :) , and I think we can use git commit-id as feature flags in other
subsystems. Since the patches in stable tree have [ Upstream commit <commit-id> ]
tag in the description, we can use them for checking which fixes are already
merged.

> The problem is in getting these
> tests right in all cases and maintaining them while updating tests for
> new features.

Is that a limitation comes from feature flags? or version synchronizing
problem?

Thank you,

-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com

  reply	other threads:[~2014-06-06  9:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 11:47 Masami Hiramatsu
2014-05-23 13:32 ` Jason Cooper
2014-05-23 16:24   ` Olof Johansson
2014-05-23 16:35     ` Guenter Roeck
2014-05-23 16:36     ` Jason Cooper
2014-05-23 18:10     ` Masami Hiramatsu
2014-05-23 18:36       ` Jason Cooper
2014-05-23 18:06   ` Masami Hiramatsu
2014-05-23 18:32     ` Jason Cooper
2014-05-23 14:05 ` Justin M. Forbes
2014-05-23 16:04   ` Mark Brown
2014-05-24  0:30   ` Theodore Ts'o
2014-05-24  1:15     ` Guenter Roeck
2014-05-26 11:33     ` Masami Hiramatsu
2014-05-30 18:35       ` Steven Rostedt
2014-05-30 20:59         ` Kees Cook
2014-05-30 22:53         ` Theodore Ts'o
2014-06-04 13:51           ` Masami Hiramatsu
2014-05-26 17:08     ` Daniel Vetter
2014-05-26 18:21       ` Mark Brown
2014-05-28 15:37 ` Mel Gorman
2014-05-28 18:57   ` Greg KH
2014-05-30 12:07     ` Linus Walleij
2014-06-05  0:23       ` Greg KH
2014-06-05  6:54         ` Mel Gorman
2014-06-05  8:30           ` Geert Uytterhoeven
2014-06-05  8:44             ` chrubis
2014-06-05  8:53             ` Daniel Vetter
2014-06-05 11:17               ` Masami Hiramatsu
2014-06-05 11:58                 ` Daniel Vetter
2014-06-06  9:10                   ` Masami Hiramatsu [this message]
2014-06-05 14:10             ` James Bottomley
2014-06-06  9:17               ` Masami Hiramatsu
2014-06-09 14:44               ` chrubis
2014-06-09 17:54                 ` Michael Kerrisk (man-pages)
2014-06-05  8:39           ` chrubis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53918574.3090307@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox