<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/tools/testing/ktest, branch v3.16</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/tools/testing/ktest?h=v3.16</id>
<link rel='self' href='https://git.amat.us/linux/atom/tools/testing/ktest?h=v3.16'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-02-26T20:26:24Z</updated>
<entry>
<title>ktest: Set CLOSE_CONSOLE_SIGNAL in the kvm.conf</title>
<updated>2014-02-26T20:26:24Z</updated>
<author>
<name>Satoru Takeuchi</name>
<email>satoru.takeuchi@gmail.com</email>
</author>
<published>2014-02-23T01:19:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=62183dcac539a14ed0a820b8392db353d72a7d7e'/>
<id>urn:sha1:62183dcac539a14ed0a820b8392db353d72a7d7e</id>
<content type='text'>
As mentioned at commit 5a5d8e48449, we can't terminate 'virsh console'
with the default signal(INT). So it's better to set CLOSE_CONSOLE_SIGNAL
in the kvm.conf.

Link: http://lkml.kernel.org/r/8738jatylb.wl%satoru.takeuchi@gmail.com

Signed-off-by: Satoru Takeuchi &lt;satoru.takeuchi@gmail.com&gt;
[ Typo fixed by ]
Signed-off-by: MUNEDA Takahiro &lt;muneda.takahiro@jp.fujitsu.com&gt;
Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'ktest-v3.14' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest</title>
<updated>2014-01-20T17:39:18Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2014-01-20T17:39:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9451ee2d17e6b4bfbc5871f3c86ea744581b0413'/>
<id>urn:sha1:9451ee2d17e6b4bfbc5871f3c86ea744581b0413</id>
<content type='text'>
Pull ktest updates from Steven Rostedt:
 "Here's some basic updates to ktest.pl.  They include:

   - add config to modify the signal to terminate console
   - update to documentation (missing some config options)
   - add KERNEL_VERSION variable to use for other configs
   - add '=~' to let configs eval other configs
   - add BISECT_TRIES to run multiple tests per git bisect good"

* tag 'ktest-v3.14' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest:
  ktest: Add BISECT_TRIES to bisect test
  ktest: Add eval '=~' command to modify variables in config file
  ktest: Add special variable ${KERNEL_VERSION}
  ktest: Add documentation of CLOSE_CONSOLE_SIGNAL
  ktest: Make the signal to terminate the console configurable
</content>
</entry>
<entry>
<title>ktest: Add BISECT_TRIES to bisect test</title>
<updated>2014-01-19T00:52:13Z</updated>
<author>
<name>Steven Rostedt (Red Hat)</name>
<email>rostedt@goodmis.org</email>
</author>
<published>2014-01-19T00:52:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=961d9caceea2d5350a15c17b7d3ffc24c08c9b09'/>
<id>urn:sha1:961d9caceea2d5350a15c17b7d3ffc24c08c9b09</id>
<content type='text'>
For those cases that it takes several tries to hit a bug, it would be
useful for ktest.pl to try a test multiple times before it considers
the test as a pass. To accomplish this, BISECT_TRIES ktest config
option has been added. It is default to one, as most of the time a
bisect only needs to try a test once. But the user can now up this
to make ktest run a given test multiple times. The first failure
that is detected will set a bisect bad. It only repeats on success.

Note, as with all race bugs, there's no guarantee that if it succeeds,
it is really a good bisect. But it helps in case the bug is somewhat
reliable.

You can set BISECT_TRIES to zero, and all tests will be considered
good, unless you also set BISECT_MANUAL.

Suggested-by: "Paul E. McKenney" &lt;paulmck@linux.vnet.ibm.com&gt;
Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;
</content>
</entry>
<entry>
<title>ktest: Add eval '=~' command to modify variables in config file</title>
<updated>2013-12-12T02:16:59Z</updated>
<author>
<name>Steven Rostedt (Red Hat)</name>
<email>rostedt@goodmis.org</email>
</author>
<published>2013-12-12T02:16:59Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c75d22d9c675c4c77d87ff36de6e5023f14724ef'/>
<id>urn:sha1:c75d22d9c675c4c77d87ff36de6e5023f14724ef</id>
<content type='text'>
With the added variable ${KERNEL_VERSION}, it is useful to be
able to use parts of it for other variables.

For example, if you want to create a warnings file for each major
kernel version to test sub versions against you can create
your warnings file with like this:

  WARNINGS_FILE = warnings-file-${KERNEL_VERSION}

But this may add 3.8.12 or something, and we want all 3.8.* to
use the same file, and 3.10.* to use another file, and so on.
With the eval command we can, by adding:

  WARNINGS_FILE =~ s/(-file-\d+\.\d+).*/$1/

Which will chop off the extra characters after the 3.8.

Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;
</content>
</entry>
<entry>
<title>ktest: Add special variable ${KERNEL_VERSION}</title>
<updated>2013-12-11T20:53:31Z</updated>
<author>
<name>Steven Rostedt (Red Hat)</name>
<email>rostedt@goodmis.org</email>
</author>
<published>2013-12-11T20:40:46Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8e80bf05ff7e7bda6f1683b1201ada56c4efa4c1'/>
<id>urn:sha1:8e80bf05ff7e7bda6f1683b1201ada56c4efa4c1</id>
<content type='text'>
Add a special variable that can be used in other variables called
${KERNEL_VERSION}. This will embed the current kernel version into
the variable. For example:

WARNINGS_FILE = ${OUTPUT_DIR}/warnings-${KERNEL_VERSION}

If the current version is v3.8 then the WARNINGS_FILE will become

  ${OUTPUT_DIR}/warnings-v3.8

Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;
</content>
</entry>
<entry>
<title>ktest: Add documentation of CLOSE_CONSOLE_SIGNAL</title>
<updated>2013-12-03T17:02:36Z</updated>
<author>
<name>Steven Rostedt (Red Hat)</name>
<email>rostedt@goodmis.org</email>
</author>
<published>2013-12-03T16:57:23Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=298a0d1d575026edec7fbb9b7e8cbb8fe18498cd'/>
<id>urn:sha1:298a0d1d575026edec7fbb9b7e8cbb8fe18498cd</id>
<content type='text'>
The sample.conf file needs to document all available options.
With the new CLOSE_CONSOE_SIGNAL option, it too needs to be
document.

Cc: Satoru Takeuchi &lt;satoru.takeuchi@gmail.com&gt;
Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;
</content>
</entry>
<entry>
<title>ktest: Make the signal to terminate the console configurable</title>
<updated>2013-12-03T16:56:07Z</updated>
<author>
<name>Satoru Takeuchi</name>
<email>satoru.takeuchi@gmail.com</email>
</author>
<published>2013-11-30T22:57:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5a5d8e4844987b6d8d64d583eb33dd926973a270'/>
<id>urn:sha1:5a5d8e4844987b6d8d64d583eb33dd926973a270</id>
<content type='text'>
 Currently ktest sends SIGINT to terminate the console.
 However, there are consoles which do not exit by this signal, for example,
 in my case, "virsh console &lt;guest OS&gt;". In such case, ktest is blocked in
 close_console(). It prevents this automate test.

This patch adds new option CLOSE_CONSOLE_SIGNAL which mean the
signal to terminate the console. Since its default value is "INT",
the original behavior isn't changed.

Link: http://lkml.kernel.org/r/87zjol8pl5.wl%satoru.takeuchi@gmail.com

Signed-off-by: Satoru Takeuchi &lt;satoru.takeuchi@gmail.com&gt;
Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;
</content>
</entry>
<entry>
<title>Drop support for Renesas H8/300 (h8300) architecture</title>
<updated>2013-09-17T01:19:04Z</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2013-08-30T13:01:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4b08478422040ae8cb11acc15d51f1cdb0ac39c8'/>
<id>urn:sha1:4b08478422040ae8cb11acc15d51f1cdb0ac39c8</id>
<content type='text'>
H8/300 has been dead for several years, and the kernel for it
has not compiled for ages. Drop support for it.

Cc: Yoshinori Sato &lt;ysato@users.sourceforge.jp&gt;
Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
</entry>
<entry>
<title>treewide: Fix typo in printk</title>
<updated>2013-05-28T10:02:13Z</updated>
<author>
<name>Masanari Iida</name>
<email>standby24x7@gmail.com</email>
</author>
<published>2013-05-21T14:13:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8b513d0cf603c0a9ccf86a92cb22931f05a7bc86'/>
<id>urn:sha1:8b513d0cf603c0a9ccf86a92cb22931f05a7bc86</id>
<content type='text'>
Correct spelling typo in various part of drivers

Signed-off-by: Masanari Iida &lt;standby24x7@gmail.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>ktest: Reset grub menu cache with different machines</title>
<updated>2013-04-24T20:03:30Z</updated>
<author>
<name>Steven Rostedt (Red Hat)</name>
<email>rostedt@goodmis.org</email>
</author>
<published>2013-04-24T20:03:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=df5f7c66013c46cec9aa8156af257bc5eb29b5c5'/>
<id>urn:sha1:df5f7c66013c46cec9aa8156af257bc5eb29b5c5</id>
<content type='text'>
Different tests may use a different machine. In such cases, we need to
try to get the current grub menu index. If the same grub menu is used
for two different machines, it may not be at the same index on the
second machine. A search for the index must be performed again.

Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;
</content>
</entry>
</feed>
