From: Alistair John Strachan <alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>
To: Sitsofe Wheeler <sitsofe-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Kernel checking options
Date: Sun, 25 May 2008 22:31:18 +0100 [thread overview]
Message-ID: <200805252231.18095.alistair@devzero.co.uk> (raw)
In-Reply-To: <g1cfbn$uic$1@ger.gmane.org>
On Sunday 25 May 2008 20:27:36 Sitsofe Wheeler wrote:
> Is this list complete? Are they all enabling additional checks?
>
> Additionally are there any options that will make (real) bugs more likely
> to occur? For example does preemption make bugs related to races (that
> could happen without preemption) happen more often?
You're missing the IOMMU test code, which is only available on x86-64 systems.
There might be some other architecture specific options you've missed.
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Alistair John Strachan <alistair@devzero.co.uk>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org
Subject: Re: Kernel checking options
Date: Sun, 25 May 2008 22:31:18 +0100 [thread overview]
Message-ID: <200805252231.18095.alistair@devzero.co.uk> (raw)
In-Reply-To: <g1cfbn$uic$1@ger.gmane.org>
On Sunday 25 May 2008 20:27:36 Sitsofe Wheeler wrote:
> Is this list complete? Are they all enabling additional checks?
>
> Additionally are there any options that will make (real) bugs more likely
> to occur? For example does preemption make bugs related to races (that
> could happen without preemption) happen more often?
You're missing the IOMMU test code, which is only available on x86-64 systems.
There might be some other architecture specific options you've missed.
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
next prev parent reply other threads:[~2008-05-25 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 19:27 Kernel checking options Sitsofe Wheeler
2008-05-25 21:31 ` Alistair John Strachan [this message]
2008-05-25 21:31 ` Alistair John Strachan
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=200805252231.18095.alistair@devzero.co.uk \
--to=alistair-t7esmzptz7iqdljmjb21zg@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sitsofe-/E1597aS9LQAvxtiuMwx3w@public.gmane.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 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.