On Tue, 27 Jun 2017 17:44:03 +0300
"Kirill A. Shutemov" <[email protected]> wrote:

> On Tue, Jun 27, 2017 at 09:38:25AM -0400, Steven Rostedt wrote:
> > On Tue, 27 Jun 2017 14:59:48 +0300
> > "Kirill A. Shutemov" <[email protected]> wrote:
> >   
> > > We've moved most logic of early boot up from startup_64() written in
> > > assembly to __startup_64() written in C.
> > > 
> > > Fengguang reported breakage due to the change. It was tracked down to
> > > CONFIG_FUNCTION_TRACER being enabled.  
> > 
> > Is this due to code that is in linux-next or is this issue currently in
> > mainline?
> > 
> > If it is in linux-next, I'll give you:
> > 
> >  Acked-by: Steven Rostedt (VMware) <[email protected]>
> > 
> > and you can take it. If the issue happens in current mainline, then I'll
> > take it and push it out.  
> 
> It's in -next.
> 
> Fixes: c88d71508e36 ("x86/boot/64: Rewrite startup_64() in C")
> 
> Although, I'm not sure if commit-id is stable yet.
> 

OK, great! Then you can take the patch along with that change, and just
add the above Acked-by from me.

-- Steve

Reply via email to