From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Anson Jacob <Anson.Jacob@amd.com>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
christophe.leroy@csgroup.eu, linuxppc-dev@lists.ozlabs.org,
amd-gfx@lists.freedesktop.org
Cc: Sunpeng.Li@amd.com, Bhawanpreet.Lakha@amd.com,
qingqing.zhuo@amd.com, Rodrigo.Siqueira@amd.com,
roman.li@amd.com, Aurabindo.Pillai@amd.com,
Harry.Wentland@amd.com, bindu.r@amd.com
Subject: Re: [RFC 0/2] Add generic FPU api similar to x86
Date: Tue, 20 Jul 2021 08:17:24 +0200 [thread overview]
Message-ID: <cd330e45-f8e0-8751-813a-98f1810881c1@gmail.com> (raw)
In-Reply-To: <20210719195211.520428-1-Anson.Jacob@amd.com>
While you already CCed a bunch of people stuff like that needs to go to
the appropriate mailing list and not just amd-gfx.
Especially LKML so that other core devs can take a look as well.
Regards,
Christian.
Am 19.07.21 um 21:52 schrieb Anson Jacob:
> This is an attempt to have generic FPU enable/disable
> calls similar to x86.
> So that we can simplify gpu/drm/amd/display/dc/os_types.h
>
> Also adds FPU correctness logic seen in x86.
>
> Anson Jacob (2):
> ppc/fpu: Add generic FPU api similar to x86
> drm/amd/display: Use PPC FPU functions
>
> arch/powerpc/include/asm/switch_to.h | 29 ++---
> arch/powerpc/kernel/process.c | 130 ++++++++++++++++++++++
> drivers/gpu/drm/amd/display/dc/os_types.h | 28 +----
> 3 files changed, 139 insertions(+), 48 deletions(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Anson Jacob <Anson.Jacob@amd.com>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
christophe.leroy@csgroup.eu, linuxppc-dev@lists.ozlabs.org,
amd-gfx@lists.freedesktop.org
Cc: Sunpeng.Li@amd.com, Bhawanpreet.Lakha@amd.com,
qingqing.zhuo@amd.com, Rodrigo.Siqueira@amd.com,
roman.li@amd.com, Aurabindo.Pillai@amd.com,
Harry.Wentland@amd.com, bindu.r@amd.com
Subject: Re: [RFC 0/2] Add generic FPU api similar to x86
Date: Tue, 20 Jul 2021 08:17:24 +0200 [thread overview]
Message-ID: <cd330e45-f8e0-8751-813a-98f1810881c1@gmail.com> (raw)
In-Reply-To: <20210719195211.520428-1-Anson.Jacob@amd.com>
While you already CCed a bunch of people stuff like that needs to go to
the appropriate mailing list and not just amd-gfx.
Especially LKML so that other core devs can take a look as well.
Regards,
Christian.
Am 19.07.21 um 21:52 schrieb Anson Jacob:
> This is an attempt to have generic FPU enable/disable
> calls similar to x86.
> So that we can simplify gpu/drm/amd/display/dc/os_types.h
>
> Also adds FPU correctness logic seen in x86.
>
> Anson Jacob (2):
> ppc/fpu: Add generic FPU api similar to x86
> drm/amd/display: Use PPC FPU functions
>
> arch/powerpc/include/asm/switch_to.h | 29 ++---
> arch/powerpc/kernel/process.c | 130 ++++++++++++++++++++++
> drivers/gpu/drm/amd/display/dc/os_types.h | 28 +----
> 3 files changed, 139 insertions(+), 48 deletions(-)
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2021-07-20 6:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 19:52 [RFC 0/2] Add generic FPU api similar to x86 Anson Jacob
2021-07-19 19:52 ` Anson Jacob
2021-07-19 19:52 ` [RFC 1/2] ppc/fpu: " Anson Jacob
2021-07-19 19:52 ` Anson Jacob
2021-07-20 6:04 ` Christoph Hellwig
2021-07-20 6:04 ` Christoph Hellwig
2021-07-20 19:30 ` kernel test robot
2021-07-19 19:52 ` [RFC 2/2] drm/amd/display: Use PPC FPU functions Anson Jacob
2021-07-19 19:52 ` Anson Jacob
2021-07-20 6:06 ` Christoph Hellwig
2021-07-20 6:06 ` Christoph Hellwig
2021-07-20 23:00 ` kernel test robot
2021-07-20 6:17 ` Christian König [this message]
2021-07-20 6:17 ` [RFC 0/2] Add generic FPU api similar to x86 Christian König
2022-03-02 16:00 ` Christophe Leroy
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=cd330e45-f8e0-8751-813a-98f1810881c1@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Anson.Jacob@amd.com \
--cc=Aurabindo.Pillai@amd.com \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Sunpeng.Li@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=benh@kernel.crashing.org \
--cc=bindu.r@amd.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=qingqing.zhuo@amd.com \
--cc=roman.li@amd.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.