On Tue, Jun 18, 2024 at 10:12:54PM +1000, Michael Ellerman wrote:
> Segher Boessenkool writes:
> > On Mon, Jun 17, 2024 at 10:35:09AM +0800, Jinglin Wen wrote:
> >> + cmplwi cr0,r4,0/* runtime base addr is zero */
> >
> > Just write
> >cmpwi r4,0
> >
> > cr0 is the default, also impl
Segher Boessenkool writes:
> Hi!
>
> On Mon, Jun 17, 2024 at 10:35:09AM +0800, Jinglin Wen wrote:
>> +cmplwi cr0,r4,0/* runtime base addr is zero */
>
> Just write
>cmpwi r4,0
>
> cr0 is the default, also implicit in many other instructions, please
> don't clutter the source code.
Hi Segher Boessenkool,
Segher Boessenkool writes:
> Hi!
>
> On Mon, Jun 17, 2024 at 10:35:09AM +0800, Jinglin Wen wrote:
> > + cmplwi cr0,r4,0/* runtime base addr is zero */
>
> Just write
>cmpwi r4,0
>
> cr0 is the default, also implicit in many other instructions, please
> don
Hi Michael Ellerman,
Michael Ellerman writes:
> Jinglin Wen writes:
> > According to the code logic, when the kernel is loaded to address 0,
> > no copying operation should be performed, but it is currently being
> > done.
> >
> > This patch fixes the issue where the kernel code was incorrectly
Hi!
On Mon, Jun 17, 2024 at 10:35:09AM +0800, Jinglin Wen wrote:
> + cmplwi cr0,r4,0/* runtime base addr is zero */
Just write
cmpwi r4,0
cr0 is the default, also implicit in many other instructions, please
don't clutter the source code. All the extra stuff makes you miss the
th
Jinglin Wen writes:
> According to the code logic, when the kernel is loaded to address 0,
> no copying operation should be performed, but it is currently being
> done.
>
> This patch fixes the issue where the kernel code was incorrectly
> duplicated to address 0 when booting from address 0.
>
> S
According to the code logic, when the kernel is loaded to address 0,
no copying operation should be performed, but it is currently being
done.
This patch fixes the issue where the kernel code was incorrectly
duplicated to address 0 when booting from address 0.
Signed-off-by: Jinglin Wen
---
arc
