Re: [PATCH] powerpc/kexec: Don't use .machine ppc64 in trampoline_64.S

2021-04-10 Thread Michael Ellerman
On Mon, 15 Mar 2021 14:41:59 +1100, Michael Ellerman wrote: > The ".machine" directive allows changing the machine for which code is > being generated. It's equivalent to passing an -mcpu option on the > command line. > > Although it can be useful, it's generally a bad idea because it adds > anoth

Re: [PATCH] powerpc/kexec: Don't use .machine ppc64 in trampoline_64.S

2021-03-18 Thread Michael Ellerman
Segher Boessenkool writes: > Hi! > > On Mon, Mar 15, 2021 at 02:41:59PM +1100, Michael Ellerman wrote: >> The ".machine" directive allows changing the machine for which code is >> being generated. It's equivalent to passing an -mcpu option on the >> command line. >> >> Although it can be useful,

Re: [PATCH] powerpc/kexec: Don't use .machine ppc64 in trampoline_64.S

2021-03-15 Thread Segher Boessenkool
Hi! On Mon, Mar 15, 2021 at 02:41:59PM +1100, Michael Ellerman wrote: > The ".machine" directive allows changing the machine for which code is > being generated. It's equivalent to passing an -mcpu option on the > command line. > > Although it can be useful, it's generally a bad idea because it a

[PATCH] powerpc/kexec: Don't use .machine ppc64 in trampoline_64.S

2021-03-14 Thread Michael Ellerman
The ".machine" directive allows changing the machine for which code is being generated. It's equivalent to passing an -mcpu option on the command line. Although it can be useful, it's generally a bad idea because it adds another way to influence code generation separate from the flags passed via t