From: Borislav Petkov <bp@amd64.org>
To: Greg KH <greg@kroah.com>
Cc: "Roedel, Joerg" <Joerg.Roedel@amd.com>, Greg KH <gregkh@suse.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Erratum 383 fix for 32 bit x86 kernels
Date: Fri, 24 Sep 2010 18:24:34 +0200 [thread overview]
Message-ID: <20100924162433.GB7627@aftab> (raw)
In-Reply-To: <20100924160205.GB21235@kroah.com>
From: Greg KH <greg@kroah.com>
Date: Fri, Sep 24, 2010 at 12:02:06PM -0400
> > extern unsigned long setup_trampoline(void);
> > +extern void __init setup_trampoline_page_table(void);
> > extern void __init reserve_trampoline_memory(void);
> > #else
> > static inline void reserve_trampoline_memory(void) {};
> > +extern void __init setup_trampoline_page_table(void) {};
> > #endif /* CONFIG_X86_TRAMPOLINE */
>
> I don't think that last setup_trampoline_page_table() line is correct
> here.
>
> Shouldn't it be:
> static inline void setup_trampoline_page_table(void) {};
> instead?
>
> Otherwise I get the following error building the .32 code with this
> patch:
> CC arch/x86/kernel/setup.o
> arch/x86/kernel/setup.c: In function ‘setup_arch’:
> arch/x86/kernel/setup.c:1001:2: error: implicit declaration of function ‘setup_trampoline_page_table’
>
> Is this really how the code looks upstream?
>
> Hm, even with changing the function prototype, I still get an error
> building on the .32-stable tree on x86-64, so I'm dropping this patch
> from there.
Yeah, Joerg forgot 8848a91068c018bc91f597038a0f41462a0f88a4.
> Also, it didn't apply cleanly to .32-stable, I had to apply this chunk
> by hand, no big deal.
>
> So, why not I just take the original git commits that are in Linus's
> tree? That should work, right? If so, do I just need to use those two
> above-mentioned commits? Or something else? I prefer taking the
> original commits as it makes spelunking over time much easier.
Sure, you need
1. fd89a137924e0710078c3ae855e7cec1c43cb845 <-- erratum fix
2. 8848a91068c018bc91f597038a0f41462a0f88a4 <-- build fix
3. b7d460897739e02f186425b7276e3fdb1595cea7 <-- VMSPLIT_* fix
in that order and they should cherry-pick fine.
Let me know if you need something tested on our end.
Thanks and sorry for the confusion.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2010-09-24 16:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 11:52 Erratum 383 fix for 32 bit x86 kernels Joerg Roedel
2010-09-24 11:58 ` Joerg Roedel
2010-09-24 13:47 ` Greg KH
2010-09-24 13:53 ` Roedel, Joerg
2010-09-24 16:02 ` Greg KH
2010-09-24 16:24 ` Borislav Petkov [this message]
2010-09-24 16:29 ` Greg KH
2010-10-22 16:18 ` Greg KH
2010-10-22 16:20 ` Greg KH
2010-10-23 8:26 ` Borislav Petkov
2010-11-11 13:56 ` [PATCH 0/3] " Joerg Roedel
2010-11-11 13:56 ` [PATCH 1/3] x86-32: Separate 1:1 pagetables from swapper_pg_dir Joerg Roedel
2011-01-19 0:39 ` Konrad Rzeszutek Wilk
2011-01-19 7:19 ` Borislav Petkov
2011-01-19 15:52 ` Konrad Rzeszutek Wilk
2010-11-11 13:56 ` [PATCH 2/3] x86, mm: Fix CONFIG_VMSPLIT_1G and 2G_OPT trampoline Joerg Roedel
2010-11-11 14:11 ` Greg KH
2010-11-11 14:13 ` Greg KH
2010-11-11 14:17 ` Roedel, Joerg
2010-11-11 15:16 ` [PATCH 0/3] Erratum 383 fix for 32 bit x86 kernels Joerg Roedel
2010-11-11 15:16 ` [PATCH 1/3] x86-32: Separate 1:1 pagetables from swapper_pg_dir Joerg Roedel
2010-12-07 21:05 ` Greg KH
2010-12-08 3:06 ` Jeremy Fitzhardinge
2010-12-08 4:15 ` Greg KH
2010-12-08 9:34 ` Ian Campbell
2010-12-08 11:58 ` Borislav Petkov
2010-12-08 15:21 ` Jeremy Fitzhardinge
2010-11-11 15:16 ` [PATCH 2/3] x86, mm: Fix CONFIG_VMSPLIT_1G and 2G_OPT trampoline Joerg Roedel
2010-12-07 21:06 ` [stable] " Greg KH
2010-11-11 15:16 ` [PATCH 3/3] x86-32: Fix dummy trampoline-related inline stubs Joerg Roedel
2010-12-07 21:07 ` Greg KH
2010-11-11 13:56 ` Joerg Roedel
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=20100924162433.GB7627@aftab \
--to=bp@amd64.org \
--cc=Joerg.Roedel@amd.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.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