| #
c0b8047b |
| 10-Feb-2024 |
Vladimir Kondratyev <wulf@FreeBSD.org> |
LinuxKPI: Allow kmalloc to be called when FPU protection is enabled
Amdgpu driver does a lot of memory allocations in FPU-protected sections
of code for certain display cores, e.g. for DCN30. This d
LinuxKPI: Allow kmalloc to be called when FPU protection is enabled
Amdgpu driver does a lot of memory allocations in FPU-protected sections
of code for certain display cores, e.g. for DCN30. This does not work
on FreeBSD as its malloc function can not be run within a critical
section. Check this condition and temporally exit from FPU-protected
context to workaround issue and reduce source code patching.
Sponsored by: Serenity Cyber Security, LLC
Reviewed by: manu (previous version)
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D42822
show more ...
|
| #
db65db64 |
| 10-Feb-2024 |
Vladimir Kondratyev <wulf@FreeBSD.org> |
Revert "LinuxKPI: Add explicit software context to FPU sections"
kmalloc() support within FPU sections will be redone in other way.
This reverts commit 5a3bd281672bd6bd8e18081c3928dfe76d330a5f.
Sp
Revert "LinuxKPI: Add explicit software context to FPU sections"
kmalloc() support within FPU sections will be redone in other way.
This reverts commit 5a3bd281672bd6bd8e18081c3928dfe76d330a5f.
Sponsored by: Serenity Cyber Security, LLC
Requested by: jhb
show more ...
|
| #
7f1a7506 |
| 10-Feb-2024 |
Vladimir Kondratyev <wulf@FreeBSD.org> |
Revert "LinuxKPI: Do not use explicit context in FPU sections on powerpc64"
kmalloc() support within FPU sections will be redone in other way.
This reverts commit b4efc62776344a9aaada5a0866e453e528
Revert "LinuxKPI: Do not use explicit context in FPU sections on powerpc64"
kmalloc() support within FPU sections will be redone in other way.
This reverts commit b4efc62776344a9aaada5a0866e453e528a0e977.
Sponsored by: Serenity Cyber Security, LLC
Requested by: jhb
show more ...
|
| #
b4efc627 |
| 24-Dec-2023 |
Vladimir Kondratyev <wulf@FreeBSD.org> |
LinuxKPI: Do not use explicit context in FPU sections on powerpc64
It is not supported yet.
Sponsored by: Serenity Cyber Security, LLC
Fixes: 5a3bd281672b ("LinuxKPI: Add explicit software context
LinuxKPI: Do not use explicit context in FPU sections on powerpc64
It is not supported yet.
Sponsored by: Serenity Cyber Security, LLC
Fixes: 5a3bd281672b ("LinuxKPI: Add explicit software context to FPU sections")
MFC after: 1 week
show more ...
|
| #
5a3bd281 |
| 24-Dec-2023 |
Vladimir Kondratyev <wulf@FreeBSD.org> |
LinuxKPI: Add explicit software context to FPU sections
Amdgpu driver does a lot of memory allocations in FPU-protected sections
of code for certain display cores, e.g. for DCN30. This does not work
LinuxKPI: Add explicit software context to FPU sections
Amdgpu driver does a lot of memory allocations in FPU-protected sections
of code for certain display cores, e.g. for DCN30. This does not work
currently on FreeBSD as its malloc function can not be run within a
critical section. Allocate memory for FPU context to overcome such
restriction.
Sponsored by: Serenity Cyber Security, LLC
Reviewed by: manu (previous version), markj
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D42822
show more ...
|
|
Revision tags: release/14.0.0 |
|
| #
4d846d26 |
| 10-May-2023 |
Warner Losh <imp@FreeBSD.org> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg
MFC After: 3 days
Sponsored by: Netflix
show more ...
|
|
Revision tags: release/13.2.0 |
|
| #
0b453151 |
| 06-Jan-2023 |
Val Packett <val@packett.cool> |
copyright: chase my name and email change
Reviewed by: imp, emaste
Differential Revision: https://reviews.freebsd.org/D37945
|
|
Revision tags: release/12.4.0, release/13.1.0, release/12.3.0 |
|
| #
469884cf |
| 31-Jul-2021 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
LinuxKPI: Make FPU sections thread-safe and use the NOCTX flag.
Reviewed by: kib
Submitted by: greg@unrelenting.technology
Differential Revision: https://reviews.freebsd.org/D29921
MFC after: 1 week
LinuxKPI: Make FPU sections thread-safe and use the NOCTX flag.
Reviewed by: kib
Submitted by: greg@unrelenting.technology
Differential Revision: https://reviews.freebsd.org/D29921
MFC after: 1 week
Sponsored by: NVIDIA Networking
show more ...
|
|
Revision tags: release/13.0.0 |
|
| #
11d62b6f |
| 12-Jan-2021 |
Emmanuel Vadot <manu@FreeBSD.org> |
linuxkpi: add kernel_fpu_begin/kernel_fpu_end
With newer AMD GPUs (>=Navi,Renoir) there is FPU context usage in the
amdgpu driver.
The `kernel_fpu_begin/end` implementations in drm did not even allo
linuxkpi: add kernel_fpu_begin/kernel_fpu_end
With newer AMD GPUs (>=Navi,Renoir) there is FPU context usage in the
amdgpu driver.
The `kernel_fpu_begin/end` implementations in drm did not even allow nested
begin-end blocks.
Submitted by: Greg V
Reviewed By: manu, hselasky
Differential Revision: https://reviews.freebsd.org/D28061
show more ...
|