From: Yinghai Lu <Yinghai.Lu@Sun.COM>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: copy srat table and unmap in acpi_parse_table
Date: Thu, 17 Jan 2008 14:09:56 -0800 [thread overview]
Message-ID: <200801171409.56611.yinghai.lu@sun.com> (raw)
In-Reply-To: <20080117204343.GA32175@elte.hu>
On Thursday 17 January 2008 12:43:43 pm Ingo Molnar wrote:
>
> * Yinghai Lu <Yinghai.Lu@Sun.COM> wrote:
>
> > [PATCH] x86: copy srat table and unmap in acpi_parse_table
> >
> >
> > the old acpi_numa_slit_init was saving old address in early stage
> > acpi_slit and acpi_parse_table can not unmap address that. the patch
> > copy the slit in the callback, so we could unmap table in
> > acpi_parse_table instead of outside track it.
> >
> > need to revert
> > "
> > commit d8d28f25f33c6a035cdfb1d421c79293d16e5c58
> > Author: Ingo Molnar <mingo@elte.hu>
> > Date: Thu Jan 17 15:26:42 2008 +0100
> >
> > x86: ACPI: fix mapping leaks
> >
> > ioremap_early() is stateful, hence we cannot tolerate mapping leaks.
> > "
> >
> > before appling this patch
>
> do you mean your patch should be applied first, then the
> d8d28f25f33c6a03 patch should applied as second?
d8d28f25f33c6a03 is not needed
>
> Or if d8d28f25f33c6a03 really needs to be reverted to get your system to
> boot properly, which particular bit of it was causing trouble for you?
> (or the whole thing?)
we need to call acpi_os_unmap_memory in acpi_table_parse or just after it.
call it in acpi_table_parse is much cleaner
the problem is that acpi_numa_slit_init do bad assumaption that it still can use address after it's callback function.
so we need to copy the slit.
YH
next prev parent reply other threads:[~2008-01-17 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 20:44 [PATCH] x86: copy srat table and unmap in acpi_parse_table Yinghai Lu
2008-01-17 20:43 ` Ingo Molnar
2008-01-17 22:09 ` Yinghai Lu [this message]
2008-01-17 22:06 ` 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=200801171409.56611.yinghai.lu@sun.com \
--to=yinghai.lu@sun.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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