linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Andi Kleen <andi@firstfloor.org>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH 1/1] MM: virtual address debug
Date: Wed, 18 Jun 2008 14:12:21 +0200	[thread overview]
Message-ID: <20080618121221.GB13714@elte.hu> (raw)
In-Reply-To: <1213271800-1556-1-git-send-email-jirislaby@gmail.com>

* Jiri Slaby <jirislaby@gmail.com> wrote:

> Add some (configurable) expensive sanity checking to catch wrong address
> translations on x86.
> 
> - create linux/mmdebug.h file to be able include this file in
>   asm headers to not get unsolvable loops in header files
> - __phys_addr on x86_32 became a function in ioremap.c since
>   PAGE_OFFSET, is_vmalloc_addr and VMALLOC_* non-constasts are undefined
>   if declared in page_32.h
> - add __phys_addr_const for initializing doublefault_tss.__cr3

applied, thanks Jiri. I have created a new tip/x86/mm-debug topic for 
this because the patch touches mm/vmalloc.c and other MM bits.

Andrew, is that fine for you, can we push it into linux-next via 
auto-x86-next if it passes testing?

	Ingo

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-06-18 12:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 11:56 Jiri Slaby
2008-06-18 12:12 ` Ingo Molnar [this message]
2008-06-18 13:59   ` Ingo Molnar
2008-06-18 14:11     ` Jiri Slaby
2008-06-18 16:11     ` Jiri Slaby
2008-06-18 18:35     ` [PATCH v2] " Jiri Slaby
2008-06-19 11:34       ` Ingo Molnar
2008-06-18 12:51 ` [PATCH 1/1] " Nick Piggin
2008-06-18 13:41   ` Jiri Slaby
2008-06-18 14:01     ` Nick Piggin

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=20080618121221.GB13714@elte.hu \
    --to=mingo@elte.hu \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox