public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Pawel Dziekonski <dzieko@gmail.com>, Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>, Tejun Heo <tj@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CPU scheduler question/problem
Date: Wed, 11 Feb 2009 01:06:59 -0800	[thread overview]
Message-ID: <49929533.6040602@kernel.org> (raw)
In-Reply-To: <2cd4df870902091056v7287e53fx8e7c8c5599b856b3@mail.gmail.com>

Pawel Dziekonski wrote:
> 2009/2/9 Ingo Molnar <mingo@elte.hu>:
> 
>> What you need to do after this is to:
>>  git checkout tip/master
>> to be on the latest tip/master tree.
> 
> looks good.
> 
> again I got warnings (not errors!) around MODPOST about mismatch.
> make CONFIG_DEBUG_SECTION_MISMATCH=y
> shows 2 warning about some acpi related functions having (or not)
> necesary __init prefix.
> 
> after reboot I got this:
> 
> ------------[ cut here ]------------
> WARNING: at arch/x86/mm/ioremap.c:616 check_early_ioremap_leak+0x52/0x67()
> Hardware name:
> Debug warning: early ioremap leak of 1 areas detected.
> Modules linked in:


please check

[PATCH] pci: fix one early_ioremap leaking

Impact: fix map leaking

Pawel reported:
------------[ cut here ]------------
WARNING: at arch/x86/mm/ioremap.c:616 check_early_ioremap_leak+0x52/0x67()
Hardware name:
Debug warning: early ioremap leak of 1 areas detected.
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.29-rc4-tip #2
...

Reported-by: Pawel Dziekonski <dzieko@gmail.com>
Signed-off-by: Yinghai Lu <yinghai@kernel.org>

---
 drivers/pci/dmar.c |    7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

Index: linux-2.6/drivers/pci/dmar.c
===================================================================
--- linux-2.6.orig/drivers/pci/dmar.c
+++ linux-2.6/drivers/pci/dmar.c
@@ -42,6 +42,7 @@
 LIST_HEAD(dmar_drhd_units);
 
 static struct acpi_table_header * __initdata dmar_tbl;
+static acpi_size dmar_tbl_size;
 
 static void __init dmar_register_drhd_unit(struct dmar_drhd_unit *drhd)
 {
@@ -288,8 +289,9 @@ static int __init dmar_table_detect(void
 	acpi_status status = AE_OK;
 
 	/* if we could find DMAR table, then there are DMAR devices */
-	status = acpi_get_table(ACPI_SIG_DMAR, 0,
-				(struct acpi_table_header **)&dmar_tbl);
+	status = acpi_get_table_with_size(ACPI_SIG_DMAR, 0,
+				(struct acpi_table_header **)&dmar_tbl,
+				&dmar_tbl_size);
 
 	if (ACPI_SUCCESS(status) && !dmar_tbl) {
 		printk (KERN_WARNING PREFIX "Unable to map DMAR\n");
@@ -481,6 +483,7 @@ void __init detect_intel_iommu(void)
 			iommu_detected = 1;
 #endif
 	}
+	early_acpi_os_unmap_memory(dmar_tbl, dmar_tbl_size);
 	dmar_tbl = NULL;
 }
 

       reply	other threads:[~2009-02-11  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2cd4df870902031544h5f0b4e59na2c0a0804125dd9a@mail.gmail.com>
     [not found] ` <2cd4df870902040600r2974362r4e9eabf2608b05b4@mail.gmail.com>
     [not found]   ` <20090204142455.GE4411@elte.hu>
     [not found]     ` <2cd4df870902040751l19332473ic36e2642723f5ec8@mail.gmail.com>
     [not found]       ` <20090205192502.GC27422@elte.hu>
     [not found]         ` <2cd4df870902051514k31582fbal11113b37b756dda0@mail.gmail.com>
     [not found]           ` <1233914595.10894.1.camel@laptop>
     [not found]             ` <20090206155311.GQ18368@elte.hu>
     [not found]               ` <2cd4df870902061444p335a9433l73fe6e820ec11c6@mail.gmail.com>
     [not found]                 ` <20090209122538.GI17782@elte.hu>
     [not found]                   ` <2cd4df870902091056v7287e53fx8e7c8c5599b856b3@mail.gmail.com>
2009-02-11  9:06                     ` Yinghai Lu [this message]
2009-02-11 13:22                       ` [PATCH] pci, x86, acpi: fix early_ioremap() leak Ingo Molnar
2009-01-22 21:34 CPU scheduler question/problem Pawel Dziekonski
2009-01-23 15:40 ` Peter Zijlstra
2009-01-26 13:48   ` Pawel Dziekonski
2009-01-26 13:55     ` Peter Zijlstra
2009-01-26 22:55     ` Ingo Molnar
2009-01-27 16:04       ` Pawel Dziekonski

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=49929533.6040602@kernel.org \
    --to=yinghai@kernel.org \
    --cc=dzieko@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=tj@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