| Message ID | 20240208101156.735389-1-aleksey.smirnov@yadro.com |
|---|---|
| State | Accepted, archived |
| Commit | 10f7eeafd16c8b825b3c9b96b8433311f122df1e |
| Delegated to: | Ross Burton |
| Headers | show |
| Series | configuration: add Power8 tune to PowerPC architecture | expand |
On Thu, 2024-02-08 at 13:11 +0300, Aleksey Smirnov wrote: > Description: now we can tune our build only for power7 or power9 > processor for PowerPC arch, this patch add posibility to choose power8 tune. > > Signed-off-by: Aleksey Smirnov <aleksey.smirnov@yadro.com> > --- > .../machine/include/powerpc/tune-power8.inc | 31 +++++++++++++++++++ > 1 file changed, 31 insertions(+) > create mode 100644 meta/conf/machine/include/powerpc/tune-power8.inc The patch is probably fine but I do have to ask, are you actively using Power8 based devices? Are these current/new designs or old ones for compatibility? I ask since I get a lot of questions about dropping mips and power support so it would be useful for me to be able to point to users. Mips and power are also not represented at the membership level in the Yocto Project, unlike the other architectures which does make maintaining all the testing a bit tricky to justify. Cheers, Richard
On Thu, 8 Feb 2024 at 12:20, Richard Purdie <richard.purdie@linuxfoundation.org> wrote: > The patch is probably fine but I do have to ask, are you actively using > Power8 based devices? Are these current/new designs or old ones for > compatibility? > > I ask since I get a lot of questions about dropping mips and power > support so it would be useful for me to be able to point to users. > > Mips and power are also not represented at the membership level in the > Yocto Project, unlike the other architectures which does make > maintaining all the testing a bit tricky to justify. I think we're testing only 32 bit ppc, and this is for the purpose of building for 64 bit ppc designs? Then dropping the former won't affect the latter. Alex
On Thu, Feb 8, 2024 at 3:30 AM Alexander Kanavin <alex.kanavin@gmail.com> wrote: > On Thu, 8 Feb 2024 at 12:20, Richard Purdie > <richard.purdie@linuxfoundation.org> wrote: > > The patch is probably fine but I do have to ask, are you actively using > > Power8 based devices? Are these current/new designs or old ones for > > compatibility? > > > > I ask since I get a lot of questions about dropping mips and power > > support so it would be useful for me to be able to point to users. > > > > Mips and power are also not represented at the membership level in the > > Yocto Project, unlike the other architectures which does make > > maintaining all the testing a bit tricky to justify. > > I think we're testing only 32 bit ppc, and this is for the purpose of > building for 64 bit ppc designs? Then dropping the former won't affect > the latter. Testing matrix is one of them but there are other concerns like multilib support. So knowing this is quite helpful on decision making > > Alex > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#195137): > https://lists.openembedded.org/g/openembedded-core/message/195137 > Mute This Topic: https://lists.openembedded.org/mt/104236370/1997914 > Group Owner: openembedded-core+owner@lists.openembedded.org > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ > raj.khem@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- > >
diff --git a/meta/conf/machine/include/powerpc/tune-power8.inc b/meta/conf/machine/include/powerpc/tune-power8.inc new file mode 100644 index 0000000000..ee10f2428f --- /dev/null +++ b/meta/conf/machine/include/powerpc/tune-power8.inc @@ -0,0 +1,31 @@ +DEFAULTTUNE ?= "ppc64p8le" + +require conf/machine/include/powerpc/arch-powerpc64.inc + +TUNEVALID[power8] = "Enable IBM Power8 specific processor optimizations" +TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'power8', ' -mcpu=power8', '', d)}" + +AVAILTUNES += "ppcp8 ppc64p8 ppcp8le ppc64p8le" + +TUNE_FEATURES:tune-ppcp8 = "m32 fpu-hard power8 altivec bigendian" +BASE_LIB:tune-ppcp8 = "lib" +TUNE_PKGARCH:tune-ppcp8 = "ppcp8" +PACKAGE_EXTRA_ARCHS:tune-ppcp8 = "${PACKAGE_EXTRA_ARCHS:tune-powerpc} ppcp8" + +TUNE_FEATURES:tune-ppc64p8 = "m64 fpu-hard power8 altivec bigendian" +BASE_LIB:tune-ppc64p8 = "lib64" +TUNE_PKGARCH:tune-ppc64p8 = "ppc64p8" +PACKAGE_EXTRA_ARCHS:tune-ppc64p8 = "${PACKAGE_EXTRA_ARCHS:tune-powerpc64} ppc64p8" + +TUNE_FEATURES:tune-ppcp8le = "m32 fpu-hard power8 altivec" +BASE_LIB:tune-ppcp8le = "lib" +TUNE_PKGARCH:tune-ppcp8le = "ppcp8le" +PACKAGE_EXTRA_ARCHS:tune-ppcp8le = "${PACKAGE_EXTRA_ARCHS:tune-powerpcle} ppcp8le" + +TUNE_FEATURES:tune-ppc64p8le = "m64 fpu-hard power8 altivec" +BASE_LIB:tune-ppc64p8le = "lib64" +TUNE_PKGARCH:tune-ppc64p8le = "ppc64p8le" +PACKAGE_EXTRA_ARCHS:tune-ppc64p8le = "${PACKAGE_EXTRA_ARCHS:tune-powerpc64le} ppc64p8le" + +# glibc configure options to get power8 specific library +GLIBC_EXTRA_OECONF += "${@bb.utils.contains('TUNE_FEATURES', 'power8', '--with-cpu=power8', '', d)}"
Description: now we can tune our build only for power7 or power9 processor for PowerPC arch, this patch add posibility to choose power8 tune. Signed-off-by: Aleksey Smirnov <aleksey.smirnov@yadro.com> --- .../machine/include/powerpc/tune-power8.inc | 31 +++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 meta/conf/machine/include/powerpc/tune-power8.inc