Date: Sun, 31 Dec 2023 06:14:45 +0300 From: Vladimir Kondratyev <vladimir@kondratyev.su> To: John Baldwin <jhb@freebsd.org>, Vladimir Kondratyev <wulf@freebsd.org>, src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: b4efc6277634 - main - LinuxKPI: Do not use explicit context in FPU sections on powerpc64 Message-ID: <d00e79fb-29de-4bb3-a5e4-6b79e03191e1@kondratyev.su> In-Reply-To: <e2cbddfc-0646-41b7-a8c3-d25ea60dda66@FreeBSD.org> References: <202312241320.3BODK2DA076069@gitrepo.freebsd.org> <e2cbddfc-0646-41b7-a8c3-d25ea60dda66@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27.12.2023 20:05, John Baldwin wrote: > On 12/24/23 5:20 AM, Vladimir Kondratyev wrote: >> The branch main has been updated by wulf: >>=20 >> URL:=20 >> https://cgit.FreeBSD.org/src/commit/?id=3Db4efc62776344a9aaada5a0866e4= 53e528a0e977 >>=20 >> commit b4efc62776344a9aaada5a0866e453e528a0e977 >> Author:=C2=A0=C2=A0=C2=A0=C2=A0 Vladimir Kondratyev <wulf@FreeBSD.org> >> AuthorDate: 2023-12-24 12:48:06 +0000 >> Commit:=C2=A0=C2=A0=C2=A0=C2=A0 Vladimir Kondratyev <wulf@FreeBSD.org> >> CommitDate: 2023-12-24 12:48:06 +0000 >>=20 >> =C2=A0=C2=A0=C2=A0=C2=A0 LinuxKPI: Do not use explicit context in FPU = sections on=20 >> powerpc64 >> =C2=A0=C2=A0=C2=A0=C2=A0 It is not supported yet. >> =C2=A0=C2=A0=C2=A0=C2=A0 Sponsored by:=C2=A0=C2=A0 Serenity Cyber Secu= rity, LLC >> =C2=A0=C2=A0=C2=A0=C2=A0 Fixes:=C2=A0 5a3bd281672b ("LinuxKPI: Add exp= licit software context to=20 >> FPU sections") >> =C2=A0=C2=A0=C2=A0=C2=A0 MFC after:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1 we= ek >> --- >> =C2=A0 sys/compat/linuxkpi/common/include/linux/compat.h | 5 ----- >> =C2=A0 sys/compat/linuxkpi/common/src/linux_current.c=C2=A0=C2=A0=C2=A0= | 9 ++++++--- >> =C2=A0 sys/compat/linuxkpi/common/src/linux_fpu.c=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 | 3 ++- >> =C2=A0 3 files changed, 8 insertions(+), 9 deletions(-) >=20 > Do you need explicit contexts at all? Original version of https://reviews.freebsd.org/D42822 did not use explicit contexts. =C2=A0 That is, can you not just > use FPU_KERN_NOCTX all the time?=C2=A0 Most code in the tree now uses > FPU_KERN_NOCTX now (all the crypto drivers for example), and I've > been thinking about removing support for the !FPU_KERN_NOCTX case. > Is there a reason drm-kmod can't use FPU_KERN_NOCTX?=C2=A0 Do you reall= y > need to save FPU registers in one block of code wrapped by fpu_kern_* > and then use those register values in a future section wrapped by > fpu_kern_*? >=20 I can revert current code end use previous version. Just give me some=20 time. I will be AFK till the end of january. --=20 WBR Vladimir Kondratyev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d00e79fb-29de-4bb3-a5e4-6b79e03191e1>