From: Toshi Kani <toshi.kani@hp.com>
To: mcgrof@suse.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, dan.j.williams@intel.com,
mingo@kernel.org, mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
roland@purestorage.com, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86/mm: Move warning from __ioremap_check_ram() to the call site
Date: Wed, 22 Jul 2015 09:36:55 -0600 [thread overview]
Message-ID: <1437579415.3214.263.camel@hp.com> (raw)
In-Reply-To: <tip-1c9cf9b211030a454a84cbc1cb15b82d9aa49011@git.kernel.org>
Thomas,
Dan took this series and updated patch 1/3 (and 2/3 as it contains the
change from 1/3) to fix build warning on i386. Can you please replace
patch 1/3 and 2/3 with the following version?
https://lkml.org/lkml/2015/7/19/365 (Patch 1/3)
https://lkml.org/lkml/2015/7/19/366 (Patch 2/3)
https://lkml.org/lkml/2015/7/19/367 (Patch 3/3)
Thanks,
-Toshi
On Wed, 2015-07-22 at 08:25 -0700, tip-bot for Toshi Kani wrote:
> Commit-ID: 1c9cf9b211030a454a84cbc1cb15b82d9aa49011
> Gitweb:
> http://git.kernel.org/tip/1c9cf9b211030a454a84cbc1cb15b82d9aa49011
> Author: Toshi Kani <toshi.kani@hp.com>
> AuthorDate: Thu, 16 Jul 2015 17:23:14 -0600
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitDate: Wed, 22 Jul 2015 17:20:33 +0200
>
> x86/mm: Move warning from __ioremap_check_ram() to the call site
>
> __ioremap_check_ram() has a WARN_ONCE() which is emitted when the
> given pfn range is not RAM. The warning is bogus in two aspects:
>
> - it never triggers since walk_system_ram_range() only calls
> __ioremap_check_ram() for RAM ranges.
>
> - the warning message is wrong as it says: "ioremap on RAM' after it
> established that the pfn range is not RAM.
>
> Move the WARN_ONCE() to __ioremap_caller(), and update the message to
> include the address range so we get an actual warning when something
> tries to ioremap system RAM.
>
> [ tglx: Massaged changelog ]
>
> Signed-off-by: Toshi Kani <toshi.kani@hp.com>
> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
> Cc: Roland Dreier <roland@purestorage.com>
> Cc: Luis R. Rodriguez <mcgrof@suse.com>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: linux-mm@kvack.org
> Link: http://lkml.kernel.org/r/1437088996-28511-2-git-send-email
> -toshi.kani@hp.com
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> arch/x86/mm/ioremap.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c
> index cc5ccc4..fd3df0d 100644
> --- a/arch/x86/mm/ioremap.c
> +++ b/arch/x86/mm/ioremap.c
> @@ -63,8 +63,6 @@ static int __ioremap_check_ram(unsigned long start_pfn,
> unsigned long nr_pages,
> !PageReserved(pfn_to_page(start_pfn + i)))
> return 1;
>
> - WARN_ONCE(1, "ioremap on RAM pfn 0x%lx\n", start_pfn);
> -
> return 0;
> }
>
> @@ -131,8 +129,11 @@ static void __iomem
> *__ioremap_caller(resource_size_t phys_addr,
> pfn = phys_addr >> PAGE_SHIFT;
> last_pfn = last_addr >> PAGE_SHIFT;
> if (walk_system_ram_range(pfn, last_pfn - pfn + 1, NULL,
> - __ioremap_check_ram) == 1)
> + __ioremap_check_ram) == 1) {
> + WARN_ONCE(1, "ioremap on RAM at 0x%llx -
> 0x%llx\n",
> + phys_addr, last_addr);
> return NULL;
> + }
> }
> /*
> * Mappings have to be page-aligned
next prev parent reply other threads:[~2015-07-22 15:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 23:23 [PATCH RESEND 0/3] mm, x86: Fix ioremap RAM check interfaces Toshi Kani
2015-07-16 23:23 ` [PATCH RESEND 1/3] mm, x86: Fix warning in ioremap RAM check Toshi Kani
2015-07-22 15:25 ` [tip:x86/urgent] x86/mm: Move warning from __ioremap_check_ram() to the call site tip-bot for Toshi Kani
2015-07-22 15:36 ` Toshi Kani [this message]
2015-07-22 16:44 ` Thomas Gleixner
2015-07-22 16:56 ` Toshi Kani
2015-07-16 23:23 ` [PATCH RESEND 2/3] mm, x86: Remove region_is_ram() call from ioremap Toshi Kani
2015-07-21 14:31 ` Thomas Gleixner
2015-07-21 15:07 ` Toshi Kani
2015-07-22 15:25 ` [tip:x86/urgent] x86/mm: " tip-bot for Toshi Kani
2015-07-16 23:23 ` [PATCH RESEND 3/3] mm: Fix bugs in region_is_ram() Toshi Kani
2015-07-22 15:26 ` [tip:x86/urgent] " tip-bot for Toshi Kani
2015-07-18 1:23 ` [PATCH RESEND 0/3] mm, x86: Fix ioremap RAM check interfaces Dan Williams
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=1437579415.3214.263.camel@hp.com \
--to=toshi.kani@hp.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=roland@purestorage.com \
--cc=tglx@linutronix.de \
/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