mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] kmemcheck fixes for -tip
Date: Sat, 28 Feb 2009 10:14:24 +0100	[thread overview]
Message-ID: <20090228091424.GB20533@elte.hu> (raw)
In-Reply-To: <20090228091201.GA28985@damson.getinternet.no>


* Vegard Nossum <vegard.nossum@gmail.com> wrote:

> Hi,
> 
> I hope this fixes all outstanding problems. We'll have to look 
> more closely at the CPA conflict (just a temporary Kconfig 
> workaround in place now), but this should allow your testing 
> to continue.
> 
> The following changes since commit 42f6e3ebe50cc97ce0459d4be1bed66117d104c1:
>   Ingo Molnar (1):
>         Merge branch 'for-tip' of git://git.kernel.org/.../vegard/kmemcheck into kmemcheck
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/vegard/kmemcheck.git for-tip
> 
> Pekka Enberg (1):
>       kmemcheck: make kconfig accessible for other architectures
> 
> Vegard Nossum (6):
>       kmemcheck: add opcode self-testing at boot
>       kmemcheck: decode sign/zero-extension move instructions correctly
>       kmemcheck: bitfields: introduce hack to work around gcc bug
>       trace: annotate bitfields in struct ring_buffer_event
>       kmemcheck: fix split_page() of the page allocator
>       kmemcheck: disable CPA self-test
> 
>  arch/x86/Kconfig                  |    1 +
>  arch/x86/Kconfig.debug            |   89 +-----------------------------------
>  arch/x86/mm/kmemcheck/Makefile    |    2 +-
>  arch/x86/mm/kmemcheck/kmemcheck.c |   38 +++++++++------
>  arch/x86/mm/kmemcheck/opcode.c    |   46 ++++++++++++++-----
>  arch/x86/mm/kmemcheck/selftest.c  |   69 ++++++++++++++++++++++++++++
>  arch/x86/mm/kmemcheck/selftest.h  |    6 +++
>  include/linux/kmemcheck.h         |    9 +++-
>  include/linux/ring_buffer.h       |    6 ++-
>  kernel/trace/ring_buffer.c        |    3 +
>  lib/Kconfig.debug                 |    2 +
>  lib/Kconfig.kmemcheck             |   91 +++++++++++++++++++++++++++++++++++++
>  mm/page_alloc.c                   |    8 +++
>  13 files changed, 252 insertions(+), 118 deletions(-)
>  create mode 100644 arch/x86/mm/kmemcheck/selftest.c
>  create mode 100644 arch/x86/mm/kmemcheck/selftest.h
>  create mode 100644 lib/Kconfig.kmemcheck

Pulled, thanks Vegard!

	Ingo

  reply	other threads:[~2009-02-28  9:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28  9:12 Vegard Nossum
2009-02-28  9:14 ` Ingo Molnar [this message]
2009-05-27  5:43 Vegard Nossum
2009-05-27  7:26 ` Ingo Molnar
2009-05-27 14:38   ` Vegard Nossum
2009-05-27 22:29     ` Ingo Molnar

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=20090228091424.GB20533@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=vegard.nossum@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®