From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Balamuruhan S <bala24@linux.ibm.com>, mpe@ellerman.id.au
Cc: ravi.bangoria@linux.ibm.com, jniethe5@gmail.com,
paulus@samba.org, sandipan@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH v2 0/7] consolidate PowerPC instruction encoding macros
Date: Tue, 28 Apr 2020 21:45:08 +0530 [thread overview]
Message-ID: <1588090451.55tcacz2g5.naveen@linux.ibm.com> (raw)
In-Reply-To: <20200424070853.443969-1-bala24@linux.ibm.com>
Balamuruhan S wrote:
> ppc-opcode.h have base instruction encoding wrapped with stringify_in_c()
> for raw encoding to have compatibility. But there are redundant macros for
> base instruction encodings in bpf, instruction emulation test infrastructure
> and powerpc selftests.
>
> Currently PPC_INST_* macros are used for encoding instruction opcode and PPC_*
> for raw instuction encoding, this rfc patchset introduces PPC_RAW_* macros for
> base instruction encoding and reuse it from elsewhere. With this change we can
> avoid redundant macro definitions in multiple files and start adding new
> instructions in ppc-opcode.h in future.
>
> Changes in v2:
> -------------
> Fix review comments/suggestions from Naveen and Michael Ellerman,
>
> * Rename PPC_ENCODE_* to PPC_RAW_* for base instruction encoding macros.
> * Split the patches that does mass renaming and make them simpler that just
> adds new macros.
> * Keep the patch to update all the existing names later (patch 6).
> * Lot of PPC_INST_* macros are used only in ppc-opcode.h for PPC_* macros,
> fold PPC_INST_* encoding into PPC_RAW_* to avoid using them accidentally.
> * Fixed clipped macros that was due to a typo/copy-paste
> * Consolidated all the instruction encoding macros from bpf_jit.h to
> ppc-opcode.h
> * squashed patch that removes the duplicate macro PPC_MR() in bpf_jit.h
> * merge few changes in bpf_jit files from patch 2 into patch 3
> * few fixes in powerpc selftest stringloops Makefile
> * build tested for ppc64le_defconfig, ppc64e_defconfig and pmac32_defconfig
> * Rebased on next branch of linuxppc tree
>
> Testing:
> -------
> * Tested it by compiling vmlinux and comparing objdump of it with and without
> the patchset and observed that it remains same,
>
> # diff vmlinux_objdump vmlinux_rfc_objdump
> 2c2
> < vmlinux: file format elf64-powerpcle
> ---
> > vmlinux_rfc: file format elf64-powerpcle
>
> * Tested building it with this changes for Fedora30 config, booted VM
> with powerpc next and powerpc next + patchset to run powerpc selftest and
> ftrace selftest. There were couple of failures that were common and
> patchset did not introduce any new failures.
>
> ftrace selftest:
> ---------------
> # # of passed: 96
> # # of failed: 1
> # # of unresolved: 7
> # # of untested: 0
> # # of unsupported: 1
> # # of xfailed: 1
> # # of undefined(test bug): 0
> not ok 1 selftests: ftrace: ftracetest # exit=1
>
> powerpc selftest:
> ----------------
> not ok 7 selftests: powerpc/dscr: dscr_sysfs_thread_test # exit=1
> not ok 20 selftests: powerpc/pmu/ebb: lost_exception_test # TIMEOUT
> not ok 2 selftests: powerpc/security: spectre_v2 # exit=1
>
> Thanks to Naveen, Sandipan and Michael on overall suggestions/improvements.
>
> I would request for review and suggestions to make it better.
>
> v1: https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-March/206494.html
>
> Balamuruhan S (7):
> powerpc/ppc-opcode: introduce PPC_RAW_* macros for base instruction
> encoding
> powerpc/ppc-opcode: move ppc instruction encoding from
> test_emulate_step
> powerpc/bpf_jit: reuse instruction macros from ppc-opcode.h
> powerpc/ppc-opcode: consolidate powerpc instructions from bpf_jit.h
> powerpc/ppc-opcode: reuse raw instruction macros to stringify
> powerpc/ppc-opcode: fold PPC_INST_* macros into PPC_RAW_* macros
> powerpc/selftest: reuse ppc-opcode macros to avoid redundancy
>
> arch/powerpc/include/asm/ppc-opcode.h | 706 +++++++++++-------
> arch/powerpc/lib/test_emulate_step.c | 155 ++--
> arch/powerpc/net/bpf_jit.h | 184 +----
> arch/powerpc/net/bpf_jit32.h | 34 +-
> arch/powerpc/net/bpf_jit64.h | 16 +-
> arch/powerpc/net/bpf_jit_comp.c | 134 ++--
> arch/powerpc/net/bpf_jit_comp64.c | 298 ++++----
> .../selftests/powerpc/stringloops/Makefile | 34 +-
> .../powerpc/stringloops/asm/asm-const.h | 1 +
> .../powerpc/stringloops/asm/ppc-opcode.h | 36 +-
> 10 files changed, 762 insertions(+), 836 deletions(-)
> create mode 120000 tools/testing/selftests/powerpc/stringloops/asm/asm-const.h
> mode change 100644 => 120000 tools/testing/selftests/powerpc/stringloops/asm/ppc-opcode.h
This LGTM. Except the last patch:
Acked-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Tested-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Thanks!
- Naveen
prev parent reply other threads:[~2020-04-28 16:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 7:08 [RFC PATCH v2 0/7] consolidate PowerPC instruction encoding macros Balamuruhan S
2020-04-24 7:08 ` [RFC PATCH v2 1/7] powerpc/ppc-opcode: introduce PPC_RAW_* macros for base instruction encoding Balamuruhan S
2020-04-24 7:08 ` [RFC PATCH v2 2/7] powerpc/ppc-opcode: move ppc instruction encoding from test_emulate_step Balamuruhan S
2020-04-24 7:08 ` [RFC PATCH v2 3/7] powerpc/bpf_jit: reuse instruction macros from ppc-opcode.h Balamuruhan S
2020-04-24 7:08 ` [RFC PATCH v2 4/7] powerpc/ppc-opcode: consolidate powerpc instructions from bpf_jit.h Balamuruhan S
2020-04-28 16:19 ` Naveen N. Rao
2020-04-24 7:08 ` [RFC PATCH v2 5/7] powerpc/ppc-opcode: reuse raw instruction macros to stringify Balamuruhan S
2020-04-24 7:08 ` [RFC PATCH v2 6/7] powerpc/ppc-opcode: fold PPC_INST_* macros into PPC_RAW_* macros Balamuruhan S
2020-04-24 7:08 ` [RFC PATCH v2 7/7] powerpc/selftest: reuse ppc-opcode macros to avoid redundancy Balamuruhan S
2020-04-28 16:14 ` Naveen N. Rao
2020-04-29 10:06 ` Michael Ellerman
2020-04-29 14:17 ` Naveen N. Rao
2020-04-30 2:41 ` Michael Ellerman
2020-04-30 11:57 ` Naveen N. Rao
2020-05-26 7:45 ` Balamuruhan S
2020-04-28 16:15 ` Naveen N. Rao [this message]
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=1588090451.55tcacz2g5.naveen@linux.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=bala24@linux.ibm.com \
--cc=jniethe5@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=sandipan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).