From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
dri-devel@lists.freedesktop.org, linux-riscv@lists.infradead.org,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
amd-gfx@lists.freedesktop.org,
"Nicolas Schier" <nicolas@fjasle.eu>,
"Will Deacon" <will@kernel.org>,
linux-kbuild@vger.kernel.org, "Leo Li" <sunpeng.li@amd.com>,
"Nathan Chancellor" <nathan@kernel.org>,
linux-arm-kernel@lists.infradead.org,
"Pan Xinhui" <Xinhui.Pan@amd.com>,
"Nick Desaulniers" <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org,
"Samuel Holland" <samuel.holland@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
linuxppc-dev@lists.ozlabs.org,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 3/3] drm/amd/display: Support DRM_AMD_DC_FP on RISC-V
Date: Tue, 12 Dec 2023 09:42:52 -0800 [thread overview]
Message-ID: <20231212174252.ycztjhgyhtcrffur@treble> (raw)
In-Reply-To: <ZXgH6un2uLdjQ48X@infradead.org>
On Mon, Dec 11, 2023 at 11:12:42PM -0800, Christoph Hellwig wrote:
> On Thu, Dec 07, 2023 at 10:49:53PM -0600, Samuel Holland wrote:
> > Actually tracking all possibly-FPU-tainted functions and their call sites is
> > probably possible, but a much larger task.
>
> I think objtool should be able to do that reasonably easily, it already
> does it for checking section where userspace address access is enabled
> or not, which is very similar.
Yeah, that might be doable. I can look into it.
--
Josh
prev parent reply other threads:[~2023-12-12 17:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 3:05 [PATCH 0/3] riscv: Add kernel-mode FPU support for amdgpu Samuel Holland
2023-11-22 3:05 ` [PATCH 1/3] riscv: Add support for kernel-mode FPU Samuel Holland
2023-11-22 20:23 ` kernel test robot
2023-11-23 1:54 ` kernel test robot
[not found] ` <ZV283NfE/K5zLXDD@infradead.org>
2023-12-08 4:17 ` Samuel Holland
2023-11-22 3:05 ` [PATCH 2/3] riscv: Factor out riscv-march-y to a separate Makefile Samuel Holland
2023-11-22 3:05 ` [PATCH 3/3] drm/amd/display: Support DRM_AMD_DC_FP on RISC-V Samuel Holland
2023-11-23 14:23 ` Conor Dooley
2023-11-30 0:42 ` Nathan Chancellor
2023-11-30 8:27 ` Conor Dooley
2023-12-08 5:04 ` Samuel Holland
2023-12-09 20:38 ` Arnd Bergmann
2023-12-09 21:29 ` Samuel Holland
2023-12-09 21:42 ` Arnd Bergmann
2023-12-11 15:17 ` Alex Deucher
2023-12-11 15:40 ` Samuel Holland
[not found] ` <ZV2+f/yu3C6xTVqn@infradead.org>
2023-12-08 4:49 ` Samuel Holland
[not found] ` <ZXgH6un2uLdjQ48X@infradead.org>
2023-12-12 17:42 ` Josh Poimboeuf [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=20231212174252.ycztjhgyhtcrffur@treble \
--to=jpoimboe@kernel.org \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=catalin.marinas@arm.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=samuel.holland@sifive.com \
--cc=sunpeng.li@amd.com \
--cc=will@kernel.org \
/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).