From: Sathvika Vasireddy <sv@linux.vnet.ibm.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"aik@ozlabs.ru" <aik@ozlabs.ru>,
"mingo@redhat.com" <mingo@redhat.com>,
Sathvika Vasireddy <sv@linux.ibm.com>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"jpoimboe@redhat.com" <jpoimboe@redhat.com>,
"naveen.n.rao@linux.vnet.ibm.com"
<naveen.n.rao@linux.vnet.ibm.com>,
"mbenes@suse.cz" <mbenes@suse.cz>,
"chenzhongjin@huawei.com" <chenzhongjin@huawei.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 02/16] powerpc: override __ALIGN() and __ALIGN_STR() macros
Date: Thu, 18 Aug 2022 16:16:47 +0530 [thread overview]
Message-ID: <6a0cf3a8-2153-1bed-314e-f9ba2bc74400@linux.vnet.ibm.com> (raw)
In-Reply-To: <0d2438e6-9aaa-a9c9-9613-b833771c9362@csgroup.eu>
Hi Christophe,
On 10/08/22 14:01, Christophe Leroy wrote:
>
> Le 08/08/2022 à 13:48, Sathvika Vasireddy a écrit :
>> Since we need an alignment of 4 bytes, override
>> __ALIGN() and __ALIGN_STR() accordingly.
> Why/When do we now need an alignment of 4 bytes ? Please explain the
> reason in the commit message.
Powerpc instructions must be word-aligned. Currently, there is an
alignment of 16 bytes (by default),
and it is much more than what is required for powerpc (4 bytes).
The default expansion of these macros are:
#define __ALIGN .align 4,0x90
#define __ALIGN_STR ".align 4,0x90"
Since Powerpc Linux does not require a 16 byte alignment, override
_ALIGN() and __ALIGN_STR() macros
to use required 4 byte alignment.
Sure, I'll explain the reason in commit message.
>
>> Signed-off-by: Sathvika Vasireddy <sv@linux.ibm.com>
>> ---
>> arch/powerpc/include/asm/linkage.h | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/powerpc/include/asm/linkage.h b/arch/powerpc/include/asm/linkage.h
>> index b71b9582e754..8df88fe61438 100644
>> --- a/arch/powerpc/include/asm/linkage.h
>> +++ b/arch/powerpc/include/asm/linkage.h
>> @@ -2,8 +2,12 @@
>> #ifndef _ASM_POWERPC_LINKAGE_H
>> #define _ASM_POWERPC_LINKAGE_H
>>
>> +#include <linux/stringify.h>
>> #include <asm/types.h>
>>
>> +#define __ALIGN .align 2
>> +#define __ALIGN_STR __stringify(__ALIGN)
> Why do you need to use __stringify ?
>
> ARM64 does:
>
> #define __ALIGN .align 2
> #define __ALIGN_STR ".align 2"
We could use either __stringify() or quotes, both do the same thing.
While arm64 does ".align 2",
x86 does:
#define __ALIGN .p2align 4, 0x90
#define __ALIGN_STR __stringify(__ALIGN)
>
>
>
>
>> +
>> #ifdef CONFIG_PPC64_ELF_ABI_V1
>> #define cond_syscall(x) \
>> asm ("\t.weak " #x "\n\t.set " #x ", sys_ni_syscall\n" \
Thanks for reviewing!
- Sathvika
WARNING: multiple messages have this Message-ID (diff)
From: Sathvika Vasireddy <sv@linux.vnet.ibm.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "jpoimboe@redhat.com" <jpoimboe@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"aik@ozlabs.ru" <aik@ozlabs.ru>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"mingo@redhat.com" <mingo@redhat.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"mbenes@suse.cz" <mbenes@suse.cz>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"chenzhongjin@huawei.com" <chenzhongjin@huawei.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"naveen.n.rao@linux.vnet.ibm.com"
<naveen.n.rao@linux.vnet.ibm.com>,
Sathvika Vasireddy <sv@linux.ibm.com>
Subject: Re: [PATCH 02/16] powerpc: override __ALIGN() and __ALIGN_STR() macros
Date: Thu, 18 Aug 2022 16:16:47 +0530 [thread overview]
Message-ID: <6a0cf3a8-2153-1bed-314e-f9ba2bc74400@linux.vnet.ibm.com> (raw)
In-Reply-To: <0d2438e6-9aaa-a9c9-9613-b833771c9362@csgroup.eu>
Hi Christophe,
On 10/08/22 14:01, Christophe Leroy wrote:
>
> Le 08/08/2022 à 13:48, Sathvika Vasireddy a écrit :
>> Since we need an alignment of 4 bytes, override
>> __ALIGN() and __ALIGN_STR() accordingly.
> Why/When do we now need an alignment of 4 bytes ? Please explain the
> reason in the commit message.
Powerpc instructions must be word-aligned. Currently, there is an
alignment of 16 bytes (by default),
and it is much more than what is required for powerpc (4 bytes).
The default expansion of these macros are:
#define __ALIGN .align 4,0x90
#define __ALIGN_STR ".align 4,0x90"
Since Powerpc Linux does not require a 16 byte alignment, override
_ALIGN() and __ALIGN_STR() macros
to use required 4 byte alignment.
Sure, I'll explain the reason in commit message.
>
>> Signed-off-by: Sathvika Vasireddy <sv@linux.ibm.com>
>> ---
>> arch/powerpc/include/asm/linkage.h | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/powerpc/include/asm/linkage.h b/arch/powerpc/include/asm/linkage.h
>> index b71b9582e754..8df88fe61438 100644
>> --- a/arch/powerpc/include/asm/linkage.h
>> +++ b/arch/powerpc/include/asm/linkage.h
>> @@ -2,8 +2,12 @@
>> #ifndef _ASM_POWERPC_LINKAGE_H
>> #define _ASM_POWERPC_LINKAGE_H
>>
>> +#include <linux/stringify.h>
>> #include <asm/types.h>
>>
>> +#define __ALIGN .align 2
>> +#define __ALIGN_STR __stringify(__ALIGN)
> Why do you need to use __stringify ?
>
> ARM64 does:
>
> #define __ALIGN .align 2
> #define __ALIGN_STR ".align 2"
We could use either __stringify() or quotes, both do the same thing.
While arm64 does ".align 2",
x86 does:
#define __ALIGN .p2align 4, 0x90
#define __ALIGN_STR __stringify(__ALIGN)
>
>
>
>
>> +
>> #ifdef CONFIG_PPC64_ELF_ABI_V1
>> #define cond_syscall(x) \
>> asm ("\t.weak " #x "\n\t.set " #x ", sys_ni_syscall\n" \
Thanks for reviewing!
- Sathvika
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Sathvika Vasireddy <sv@linux.vnet.ibm.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "jpoimboe@redhat.com" <jpoimboe@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"aik@ozlabs.ru" <aik@ozlabs.ru>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"mingo@redhat.com" <mingo@redhat.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"mbenes@suse.cz" <mbenes@suse.cz>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"chenzhongjin@huawei.com" <chenzhongjin@huawei.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"naveen.n.rao@linux.vnet.ibm.com"
<naveen.n.rao@linux.vnet.ibm.com>,
Sathvika Vasireddy <sv@linux.ibm.com>
Subject: Re: [PATCH 02/16] powerpc: override __ALIGN() and __ALIGN_STR() macros
Date: Thu, 18 Aug 2022 16:16:47 +0530 [thread overview]
Message-ID: <6a0cf3a8-2153-1bed-314e-f9ba2bc74400@linux.vnet.ibm.com> (raw)
In-Reply-To: <0d2438e6-9aaa-a9c9-9613-b833771c9362@csgroup.eu>
Hi Christophe,
On 10/08/22 14:01, Christophe Leroy wrote:
>
> Le 08/08/2022 à 13:48, Sathvika Vasireddy a écrit :
>> Since we need an alignment of 4 bytes, override
>> __ALIGN() and __ALIGN_STR() accordingly.
> Why/When do we now need an alignment of 4 bytes ? Please explain the
> reason in the commit message.
Powerpc instructions must be word-aligned. Currently, there is an
alignment of 16 bytes (by default),
and it is much more than what is required for powerpc (4 bytes).
The default expansion of these macros are:
#define __ALIGN .align 4,0x90
#define __ALIGN_STR ".align 4,0x90"
Since Powerpc Linux does not require a 16 byte alignment, override
_ALIGN() and __ALIGN_STR() macros
to use required 4 byte alignment.
Sure, I'll explain the reason in commit message.
>
>> Signed-off-by: Sathvika Vasireddy <sv@linux.ibm.com>
>> ---
>> arch/powerpc/include/asm/linkage.h | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/powerpc/include/asm/linkage.h b/arch/powerpc/include/asm/linkage.h
>> index b71b9582e754..8df88fe61438 100644
>> --- a/arch/powerpc/include/asm/linkage.h
>> +++ b/arch/powerpc/include/asm/linkage.h
>> @@ -2,8 +2,12 @@
>> #ifndef _ASM_POWERPC_LINKAGE_H
>> #define _ASM_POWERPC_LINKAGE_H
>>
>> +#include <linux/stringify.h>
>> #include <asm/types.h>
>>
>> +#define __ALIGN .align 2
>> +#define __ALIGN_STR __stringify(__ALIGN)
> Why do you need to use __stringify ?
>
> ARM64 does:
>
> #define __ALIGN .align 2
> #define __ALIGN_STR ".align 2"
We could use either __stringify() or quotes, both do the same thing.
While arm64 does ".align 2",
x86 does:
#define __ALIGN .p2align 4, 0x90
#define __ALIGN_STR __stringify(__ALIGN)
>
>
>
>
>> +
>> #ifdef CONFIG_PPC64_ELF_ABI_V1
>> #define cond_syscall(x) \
>> asm ("\t.weak " #x "\n\t.set " #x ", sys_ni_syscall\n" \
Thanks for reviewing!
- Sathvika
next prev parent reply other threads:[~2022-08-18 10:48 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 11:48 [PATCH 00/16] objtool: Enable and implement --mcount option on powerpc Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:48 ` [PATCH 01/16] powerpc: Replace unreachable() with it's builtin variant in WARN_ON() Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-10 8:28 ` Christophe Leroy
2022-08-10 8:28 ` Christophe Leroy
2022-08-10 8:28 ` Christophe Leroy
2022-08-18 10:46 ` Naveen N. Rao
2022-08-18 10:46 ` Naveen N. Rao
2022-08-18 10:46 ` Naveen N. Rao
2022-08-18 11:06 ` Christophe Leroy
2022-08-18 11:06 ` Christophe Leroy
2022-08-18 11:06 ` Christophe Leroy
2022-08-18 12:25 ` Naveen N. Rao
2022-08-18 12:25 ` Naveen N. Rao
2022-08-18 12:25 ` Naveen N. Rao
2022-08-26 10:18 ` Christophe Leroy
2022-08-26 10:18 ` Christophe Leroy
2022-08-26 10:18 ` Christophe Leroy
2022-08-29 5:46 ` Sathvika Vasireddy
2022-08-29 5:46 ` Sathvika Vasireddy
2022-08-29 5:46 ` Sathvika Vasireddy
2022-08-08 11:48 ` [PATCH 02/16] powerpc: override __ALIGN() and __ALIGN_STR() macros Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-10 8:31 ` Christophe Leroy
2022-08-10 8:31 ` Christophe Leroy
2022-08-10 8:31 ` Christophe Leroy
2022-08-18 10:46 ` Sathvika Vasireddy [this message]
2022-08-18 10:46 ` Sathvika Vasireddy
2022-08-18 10:46 ` Sathvika Vasireddy
2022-08-08 11:48 ` [PATCH 03/16] powerpc: Fix objtool unannotated intra-function call warnings Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-10 8:32 ` Christophe Leroy
2022-08-10 8:32 ` Christophe Leroy
2022-08-10 8:32 ` Christophe Leroy
2022-08-18 10:55 ` Sathvika Vasireddy
2022-08-18 10:55 ` Sathvika Vasireddy
2022-08-18 10:55 ` Sathvika Vasireddy
2022-08-08 11:48 ` [PATCH 04/16] powerpc: curb " Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:48 ` [PATCH 05/16] powerpc: Skip objtool from running on drivers/crypto/vmx/aesp8-ppc.o Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-10 8:34 ` Christophe Leroy
2022-08-10 8:34 ` Christophe Leroy
2022-08-10 8:34 ` Christophe Leroy
2022-08-18 11:12 ` Sathvika Vasireddy
2022-08-18 11:12 ` Sathvika Vasireddy
2022-08-18 11:12 ` Sathvika Vasireddy
2022-08-08 11:48 ` [PATCH 06/16] powerpc: Fix objtool unannotated intra-function call warnings on PPC32 Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-09 23:31 ` kernel test robot
2022-08-09 23:31 ` kernel test robot
2022-08-09 23:31 ` kernel test robot
2022-08-08 11:48 ` [PATCH 07/16] powerpc: Skip objtool from running on VDSO files Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:48 ` Sathvika Vasireddy
2022-08-08 11:49 ` [PATCH 08/16] objtool: Fix SEGFAULT Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` [PATCH 09/16] objtool: Use target file endianness instead of a compiled constant Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` [PATCH 10/16] objtool: Use target file class size " Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` [PATCH 11/16] objtool: Add --mnop as an option to --mcount Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` [PATCH 12/16] objtool: Read special sections with alts only when specific options are selected Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` [PATCH 13/16] objtool: Use macros to define arch specific reloc types Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` [PATCH 14/16] objtool: Add arch specific function arch_ftrace_match() Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-12 10:58 ` kernel test robot
2022-08-12 10:58 ` kernel test robot
2022-08-12 10:58 ` kernel test robot
2022-08-13 13:48 ` kernel test robot
2022-08-13 13:48 ` kernel test robot
2022-08-13 13:48 ` kernel test robot
2022-08-08 11:49 ` [PATCH 15/16] objtool/powerpc: Enable objtool to be built on ppc Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` [PATCH 16/16] objtool/powerpc: Add --mcount specific implementation Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
2022-08-08 11:49 ` Sathvika Vasireddy
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=6a0cf3a8-2153-1bed-314e-f9ba2bc74400@linux.vnet.ibm.com \
--to=sv@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=chenzhongjin@huawei.com \
--cc=christophe.leroy@csgroup.eu \
--cc=jpoimboe@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sv@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.