linuxkpi: Define `ULL()`
It simply appends "ULL" to its argument.
The amdgpu DRM driver used it at some point in the development cycle of
Linux 6.14 but the use case was dropped later. Let's still add it to
linuxkpi because it will help if we need to do a git bisect in drm-kmod.
Reviewed by: emaste
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D57703
linuxkpi: Defined more Intel vendor/family/model constants
The i915 DRM driver started to use them in Linux 6.14.
Reviewed by: emaste
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D57699
linuxkpi: Define and fill `struct cpuinfo_x86->x86_stepping`
This will be used in a follow-up commit to implement `x86_match_cpu()`.
Reviewed by: emaste
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D57698
linuxkpi: Add <linux/cgroup_dmem.h>
In this header, we declare empty stubs for all functions, as if
`CONFIG_CGROUP_DMEM` was disabled is Linux.
The DRM TTM memory manager started to use this in Linux 6.14.
Reviewed by: emaste
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D57702
linuxkpi: Define `struct vfsmount` in <linux/mount.h>
In the context of the DRM drivers, this is used to show GEM objects in a
shmfs virtual filesystem. The new `shmem_file_setup_with_mnt()` - also
introduced in this commit as an alias to `shmem_file_setup()` - takes a
`struct vfsmount` as its first argument to indicate which shmfs mount
should be used.
For now, the structure is empty. As we don't present GEM objects in a
virtual filesystem right now, we can defer the actual implementation of
this structure once we have an actual use for it.
The DRM generic code started to use it in Linux 6.13.
Reviewed by: emaste
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D57572
[Offload] Fix ordering with RPC teardown and global destructors (#205594)
Summary:
There's a bit of a chicken and egg problem for the RPC server if we want
to do something creative with the device's image for things like DWARF
dumping. The problem was that destructors can make RPC calls, but the
RPC server also needed the images to be valid. Simple fix is to just
split the destructor calling out and do it first so we can deinitialize
RPC with valid device images.
[SBVec] Implement topDown/botUp vectorizers in unison
This patch introduces the `top-down-vec` pass to the Sandbox Vectorizer,
adding the ability to traverse use-def chains top-down to discover and
collect vectorization opportunities. Furthermore, this patch unifies
the two vectorizers into a single implementation to minimize code
duplication.
[SBVec] Implement topDown/botUp vectorizers in unison
This patch introduces the `top-down-vec` pass to the Sandbox Vectorizer,
adding the ability to traverse use-def chains top-down to discover and
collect vectorization opportunities. Furthermore, this patch unifies
the two vectorizers into a single implementation to minimize code
duplication.
NAS-141518 / 27.0.0-BETA.1 / Standardize and enforce public API method docstrings (#19182)
## Summary
Standardizes the docstrings of every public API method, migrates
per-parameter and per-return-value descriptions out of method docstrings
into the API model field definitions, and adds a unit test that enforces
both — including structural RST validity, cross-reference resolution,
and markup linting — so documentation quality is checked in CI rather
than by review. Public API method docstrings are now consistent
reStructuredText prose; field-level details live (only) in
`Field(description=...)` on the models, where they are already required.
## Enforcement
`pytest/unit/api/test_api_structure.py` collects every public API method
in a single pass over the source tree (handling
`@api_method`/`@filterable_api_method`, private decorators/services, and
the CRUD/Config methods that base classes provide implicitly) and runs
[72 lines not shown]
qat: driver updates to enhance qat infrastructure
- Updated QAT infrastructure FW version/AE mask/num_banks fields
to facilitate integration of future QAT products.
- Exposed service as sym;asym instead of cy for gen4
- Enhanced cpaGetInstances() for accurate instance retrieval
- Added 57-bit virtual address support to lac_lock_free_stack
- Minor bug fixes and improvements
Signed-off-by: Hareshx Sankar Raj <hareshx.sankar.raj at intel.com>
Reviewed by: markj
MFC after: 1 month
Differential Revision: https://reviews.freebsd.org/D57746
[lldb-dap][test] Re-enable test_by_name_waitFor on Windows (#205570)
`test_by_name_waitFor` passes with `LLDB_USE_LLDB_SERVER=1`.
`test_by_partial_name_waitFor` hangs on exit. Skip if for now.
rdar://180515488
[SBVec] Implement topDown/botUp vectorizers in unison
This patch introduces the `top-down-vec` pass to the Sandbox Vectorizer,
adding the ability to traverse use-def chains top-down to discover and
collect vectorization opportunities. Furthermore, this patch unifies
the two vectorizers into a single implementation to minimize code
duplication.
libtorrent rtorrent: updated to 0.16.15
0.16.15
Cleanup of old unused/unneeded code and commands continues, and the deprecated commands should no longer be used.
[RISCV][XCV] Relax long `cv.beqimm`/`cv.bneimm` branches (#205096)
`cv.beqimm` and `cv.bneimm` encode their target as a 13-bit signed
PC-relative offset (+/-4094 bytes). Branches beyond that range were
silently truncated by MC fixup application, producing wrong code with no
diagnostic. Add `PseudoLongCV_BEQIMM`/`PseudoLongCV_BNEIMM` and the
MC-layer relaxation flow (inverted short branch + JAL trampoline),
mirroring the standard B-type and Qualcomm Xqcibi vendor branches.
**Tests:** `xcvbi-branch-relax.ll` (uses `-filetype=obj | llvm-objdump`,
since MC-layer relaxation is only observable on object emission, not on
textual asm).
Split out of #204879 at review request (one fix per PR).
Part of a CORE-V (XCV) series; see RFC:
https://discourse.llvm.org/t/rfc-core-v-xcv-support-for-cv32e40p-clang-builtins-xcvsimd-intrinsics-and-generic-auto-selection/91111
libass: updated to 0.17.5
libass (0.17.5)
* Fix limited OOB read and write in wrap_lines_measure (GHSA-pjjp-65r7-ppgm; CVE pending)
* Fix OOB bit clears for negative Matroska ReadOrder fields (GHSA-5gf7-wjfm-vmvm; CVE pending)
* Fix \fay with glyph clusters
* Fix small alpha changes not always splitting runs when combined with fade
* Fix compilation with MSVC-mode clang
* Fades are now applied to BorderStyle=4 boxes too
* Fonts using legacy arabic Windows charmaps are now supported
* ass_render_frame no longer returns fully transparent images
* Avoid MSVC’s subpar code generation for isnan to bring performance closer to other compilers
* Avoid SSE instructions if compiler baseline already includes AVX
