All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: linux-kernel@vger.kernel.org, mason@suse.com
Subject: Re: What exactly are the issues with 2.6.0-test10 preempt?
Date: Tue, 25 Nov 2003 01:05:26 +0100	[thread overview]
Message-ID: <20031125000526.GD28026@wotan.suse.de> (raw)
In-Reply-To: <20031125000002.GB1586@mis-mike-wstn.matchmail.com>

> > Me and Chris used that to track down some nasty corruptions on x86-64,
> > it is especially useful together with LTP which calls a lot of system
> > calls that could cause corruption.
> 
> Do you have your code posted anywhere, and when are you going to merge it
> with LTP? ;)

I wrote it always custom tailored to the problem (it is not very difficult, but
you often have to tune it a bit until it has the right frequency to find the
corruption) Don't have one here right now, sorry.  Chris had a aimed to be 
generic patch for 2.4 that may still be around. I don't think it would fit 
into current LTP because it is an kernel module (LTP doesn't have a kernel build 
infrastructure right now).  But it would be an useful addition longer term to it 
I agree, once they support kernel modules.

-Andi


  reply	other threads:[~2003-11-25  0:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031124224514.56242.qmail@web40908.mail.yahoo.com.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.58.0311241452550.15101@home.osdl.org.suse.lists.linux.kernel>
2003-11-24 23:50   ` What exactly are the issues with 2.6.0-test10 preempt? Andi Kleen
2003-11-25  0:00     ` Mike Fedyk
2003-11-25  0:05       ` Andi Kleen [this message]
2003-11-25  0:16         ` Chris Mason
2003-11-25 18:31 kernel
2003-11-26  9:30 ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2003-11-25 18:14 root
2003-11-25 18:13 kernel
2003-11-24 19:14 Bradley Chapman
2003-11-24 21:08 ` Guennadi Liakhovetski
2003-11-24 21:29   ` Bradley Chapman
2003-11-24 21:47     ` Guennadi Liakhovetski
2003-11-24 21:55       ` Bradley Chapman
2003-11-24 21:59   ` Linus Torvalds
2003-11-24 22:26     ` Bradley Chapman
2003-11-24 22:32       ` Linus Torvalds
2003-11-24 22:45         ` Bradley Chapman
2003-11-24 23:00           ` Linus Torvalds
2003-11-24 23:45             ` Linus Torvalds
2003-11-25  7:55         ` Jos Hulzink
2003-11-24 22:41       ` Måns Rullgård
2003-11-24 22:51         ` Mike Fedyk
2003-11-25  1:37           ` Måns Rullgård
2003-11-25 17:22           ` bill davidsen
2003-11-24 22:57     ` Guennadi Liakhovetski
2003-11-25  7:17     ` Guennadi Liakhovetski
2003-11-25 16:20       ` Linus Torvalds
2003-11-30  9:09 ` Matthias Urlichs

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=20031125000526.GD28026@wotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.