LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sasha.levin@oracle.com
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, netdev@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH] mm: kill kmemcheck
Date: Wed, 11 Mar 2015 13:20:52 -0400 (EDT)	[thread overview]
Message-ID: <20150311.132052.205877953171712952.davem@davemloft.net> (raw)
In-Reply-To: <55004595.7020304@oracle.com>

From: Sasha Levin <sasha.levin@oracle.com>
Date: Wed, 11 Mar 2015 09:39:33 -0400

> On 03/11/2015 08:40 AM, Steven Rostedt wrote:
>> On Wed, 11 Mar 2015 08:34:46 -0400
>> Sasha Levin <sasha.levin@oracle.com> wrote:
>> 
>>> > Fair enough. We knew there are existing kmemcheck users, but KASan should be
>>> > superior both in performance and the scope of bugs it finds. It also shouldn't
>>> > impose new limitations beyond requiring gcc 4.9.2+.
>>> >
>> Ouch! OK, then I can't use it. I'm currently compiling with gcc 4.6.3.
>> 
>> It will be a while before I upgrade my build farm to something newer.
> 
> Are you actually compiling new kernels with 4.6.3, or are you using older
> kernels as well?
> 
> There's no real hurry to kill kmemcheck right now, but we do want to stop
> supporting that in favour of KASan.

Is the spectrum of CPU's supported by this GCC feature equal to all of the
CPU's supported by the kernel right now?

If not, removing kmemcheck will always be a regression for someone.

  parent reply	other threads:[~2015-03-11 17:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1426074547-21888-1-git-send-email-sasha.levin@oracle.com>
2015-03-11 12:19 ` Steven Rostedt
2015-03-11 12:34   ` Sasha Levin
2015-03-11 12:40     ` Steven Rostedt
2015-03-11 13:39       ` Sasha Levin
2015-03-11 14:23         ` Dave Jones
2015-03-11 14:26         ` Steven Rostedt
2015-03-11 14:43           ` Sasha Levin
2015-03-11 14:52             ` Steven Rostedt
2015-03-17  1:48               ` Sasha Levin
2015-03-17  2:33                 ` Steven Rostedt
2015-03-11 14:35         ` Boaz Harrosh
2015-03-11 17:20         ` David Miller [this message]
2015-03-11 17:25           ` Sasha Levin
2015-03-11 18:44             ` David Miller
2015-03-11 20:01               ` Andrey Ryabinin
2015-03-11 20:48                 ` David Miller
     [not found] ` <1426132192.25936.7.camel@ellerman.id.au>
     [not found]   ` <55018936.5080805@oracle.com>
2015-03-12 18:11     ` David Miller

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=20150311.132052.205877953171712952.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sasha.levin@oracle.com \
    --subject='Re: [PATCH] mm: kill kmemcheck' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).