From: Justin Mattock <justinmattock@gmail.com>
To: mingo@redhat.com, hpa@zytor.com, justinmattock@gmail.com,
linux-kernel@vger.kernel.org, jbeulich@novell.com,
tglx@linutronix.de, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86: Fix placement of FIX_OHCI1394_BASE
Date: Tue, 16 Mar 2010 14:03:57 -0700 [thread overview]
Message-ID: <dd18b0c31003161403r56f9fd88kcc561a630be136a3@mail.gmail.com> (raw)
In-Reply-To: <tip-ff30a0543e9a6cd732582063e7cae951cdb7acf2@git.kernel.org>
On Tue, Mar 16, 2010 at 7:48 AM, tip-bot for Jan Beulich
<JBeulich@novell.com> wrote:
> Commit-ID: ff30a0543e9a6cd732582063e7cae951cdb7acf2
> Gitweb: http://git.kernel.org/tip/ff30a0543e9a6cd732582063e7cae951cdb7acf2
> Author: Jan Beulich <JBeulich@novell.com>
> AuthorDate: Mon, 15 Mar 2010 10:11:15 +0000
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Tue, 16 Mar 2010 11:16:27 +0100
>
> x86: Fix placement of FIX_OHCI1394_BASE
>
> Ever for 32-bit with sufficiently high NR_CPUS, and starting
> with commit 789d03f584484af85dbdc64935270c8e45f36ef7 also for
> 64-bit, the statically allocated early fixmap page tables were
> not covering FIX_OHCI1394_BASE, leading to a boot time crash
> when "ohci1394_dma=early" was used. Despite this entry not being
> a permanently used one, it needs to be moved into the permanent
> range since it has to be close to FIX_DBGP_BASE and
> FIX_EARLYCON_MEM_BASE.
>
> Reported-bisected-and-tested-by: Justin P. Mattock <justinmattock@gmail.com>
> Fixes-bug: http://bugzilla.kernel.org/show_bug.cgi?id=14487
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
> Cc: <stable@kernel.org> # [as far back as long as it still applies]
> LKML-Reference: <4B9E15D30200007800034D23@vpn.id2.novell.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> arch/x86/include/asm/fixmap.h | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/include/asm/fixmap.h b/arch/x86/include/asm/fixmap.h
> index 635f03b..d07b44f 100644
> --- a/arch/x86/include/asm/fixmap.h
> +++ b/arch/x86/include/asm/fixmap.h
> @@ -82,6 +82,9 @@ enum fixed_addresses {
> #endif
> FIX_DBGP_BASE,
> FIX_EARLYCON_MEM_BASE,
> +#ifdef CONFIG_PROVIDE_OHCI1394_DMA_INIT
> + FIX_OHCI1394_BASE,
> +#endif
> #ifdef CONFIG_X86_LOCAL_APIC
> FIX_APIC_BASE, /* local (CPU) APIC) -- required for SMP or not */
> #endif
> @@ -132,9 +135,6 @@ enum fixed_addresses {
> (__end_of_permanent_fixed_addresses & (TOTAL_FIX_BTMAPS - 1))
> : __end_of_permanent_fixed_addresses,
> FIX_BTMAP_BEGIN = FIX_BTMAP_END + TOTAL_FIX_BTMAPS - 1,
> -#ifdef CONFIG_PROVIDE_OHCI1394_DMA_INIT
> - FIX_OHCI1394_BASE,
> -#endif
> #ifdef CONFIG_X86_32
> FIX_WP_TEST,
> #endif
>
looks good over here..
--
Justin P. Mattock
prev parent reply other threads:[~2010-03-16 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 10:11 [PATCH, resend] x86: fix " Jan Beulich
2010-03-16 14:48 ` [tip:x86/urgent] x86: Fix " tip-bot for Jan Beulich
2010-03-16 21:03 ` Justin Mattock [this message]
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=dd18b0c31003161403r56f9fd88kcc561a630be136a3@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®