Changes in ap.h

cc4adab164b772a34b3340d644b7c4728498581e - Merge tag 'v6.19-rc1' into msm-next

Tue, 20 Jan 2026 22:06:55 +0000

Merge tag 'v6.19-rc1' into msm-nextMerge Linux 6.19-rc1 in order to catch up with other changes (e.g. UBWCconfig database defining UBWC_6).Signed-off-by: Dmitry Baryshkov List of files: /linux/arch/s390/include/asm/trace/ap.h

5add3c3c280a35f7e258e9cef7607db5a2e56fdc - Merge drm/drm-next into drm-xe-next

Fri, 19 Dec 2025 10:51:22 +0000

Merge drm/drm-next into drm-xe-nextBackmerging to bring in 6.19-rc1. An important upstream bugfix andto help unblock PTL CI.Signed-off-by: Thomas Hellström List of files: /linux/arch/s390/include/asm/trace/ap.h

b8304863a3990d0f18c38e5b94191830a63ee1af - Merge drm/drm-next into drm-intel-next

Mon, 15 Dec 2025 13:24:02 +0000

Merge drm/drm-next into drm-intel-nextSync-up some display code needed for Async flips refactor.Signed-off-by: Rodrigo Vivi List of files: /linux/arch/s390/include/asm/trace/ap.h

7f790dd21a931c61167f7bdc327aecf2cebad327 - Merge drm/drm-next into drm-misc-next

Mon, 15 Dec 2025 08:27:39 +0000

Merge drm/drm-next into drm-misc-nextLet's kickstart the v6.20 (7.0?) release cycle.Signed-off-by: Maxime Ripard List of files: /linux/arch/s390/include/asm/trace/ap.h

24f171c7e145f43b9f187578e89b0982ce87e54c - Merge tag 'asoc-fix-v6.19-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus

Sun, 21 Dec 2025 10:11:11 +0000

Merge tag 'asoc-fix-v6.19-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linusASoC: Fixes for v6.19We've been quite busy with fixes since the merge window, though not inany particularly exciting ways - the standout thing is the fix for _SXcontrols which were broken by a change to how we do clamping, otherwiseit's all fairly run of the mill fixes and quirks. List of files: /linux/arch/s390/include/asm/trace/ap.h

84318277d6334c6981ab326d4acc87c6a6ddc9b8 - Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixes

Mon, 15 Dec 2025 11:53:27 +0000

Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixesPull in rc1 to include all changes since the merge window closed,and grab all fixes and changes from drm/drm-next.Signed-off-by: Maarten Lankhorst List of files: /linux/arch/s390/include/asm/trace/ap.h

2547f79b0b0cd969ae6f736890af4ebd9368cda5 - Merge tag 's390-6.19-1' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux

Wed, 03 Dec 2025 00:37:00 +0000

Merge tag 's390-6.19-1' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linuxPull s390 updates from Heiko Carstens: - Provide a new interface for dynamic configuration and deconfiguration of hotplug memory, allowing with and without memmap_on_memory support. This makes the way memory hotplug is handled on s390 much more similar to other architectures - Remove compat support. There shouldn't be any compat user space around anymore, therefore get rid of a lot of code which also doesn't need to be tested anymore - Add stackprotector support. GCC 16 will get new compiler options, which allow to generate code required for kernel stackprotector support - Merge pai_crypto and pai_ext PMU drivers into a new driver. This removes a lot of duplicated code. The new driver is also extendable and allows to support new PMUs - Add driver override support for AP queues - Rework and extend zcrypt and AP trace events to allow for tracing of crypto requests - Support block sizes larger than 65535 bytes for CCW tape devices - Since the rework of the virtual kernel address space the module area and the kernel image are within the same 4GB area. This eliminates the need of weak per cpu variables. Get rid of ARCH_MODULE_NEEDS_WEAK_PER_CPU - Various other small improvements and fixes* tag 's390-6.19-1' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux: (92 commits) watchdog: diag288_wdt: Remove KMSG_COMPONENT macro s390/entry: Use lay instead of aghik s390/vdso: Get rid of -m64 flag handling s390/vdso: Rename vdso64 to vdso s390: Rename head64.S to head.S s390/vdso: Use common STABS_DEBUG and DWARF_DEBUG macros s390: Add stackprotector support s390/modules: Simplify module_finalize() slightly s390: Remove KMSG_COMPONENT macro s390/percpu: Get rid of ARCH_MODULE_NEEDS_WEAK_PER_CPU s390/ap: Restrict driver_override versus apmask and aqmask use s390/ap: Rename mutex ap_perms_mutex to ap_attr_mutex s390/ap: Support driver_override for AP queue devices s390/ap: Use all-bits-one apmask/aqmask for vfio in_use() checks s390/debug: Update description of resize operation s390/syscalls: Switch to generic system call table generation s390/syscalls: Remove system call table pointer from thread_struct s390/uapi: Remove 31 bit support from uapi header files s390: Remove compat support tools: Remove s390 compat support ... List of files: /linux/arch/s390/include/asm/trace/ap.h

5c02c74dd482e0fb6c303a7e781812c26f06bcb8 - Merge branch 'ap-bus-trace-events'

Tue, 21 Oct 2025 09:10:55 +0000

Merge branch 'ap-bus-trace-events'Harald Freudenberger says:====================Investigations related to runtime of crypto requests has revealed a lack ofperformance or runtime information with crypto requests. There are the twozcrypt ioctl trace events covering the entry and exit of an ioctl withcrypto requests giving the overall runtime within the kernel. However,there is no way to figure out the time where a request is enqueued into theAP bus queue but not pushed into the firmware queue. Then there is noinformation about the runtime of an request during processing in thefirmware. And finally some info about pulling the reply from the firmwareand delivering it into user space is missing.This series is aiming to provide a way to collect measurements which can beused to cover these runtime information for each crypto request/reply.====================Signed-off-by: Heiko Carstens List of files: /linux/arch/s390/include/asm/trace/ap.h

9c11918040d6aa19c407ead4dc86b65e664f401f - s390/ap: Introduce new AP nqap and dqap trace events

Fri, 17 Oct 2025 10:14:15 +0000

s390/ap: Introduce new AP nqap and dqap trace eventsIntroduce two new AP bus related tracepoint events:- There is a tracepoint s390_ap_nqap event immediately after a request has been pushed into the AP firmware queue with the NQAP AP command.- The other tracepoint s390_ap_dqap event fires immediately after a reply has been pulled out of the AP firmware queue via DQAP AP command.Both events are triggered unconditional and may need filtering.Filtering can be done based on the status value which is part ofthe nqap and dqap trace. So for example a echo "!(status & 0x00ff0000)" >.../s390_ap_dqap/filterfilters out all trace events which have a response_code != 0leaving just the successful nqap and dqap invocations.The idea of these two trace events focuses on performance to measurethe runtime of a crypto request/reply as close as possible at thefirmware level. In combination with the two zcrypt tracepoints (seethe zcrypt.h trace event definition file) this gives measurement dataabout the runtime of a request/reply within the zcrpyt and AP buslayer. However, with having the status of these AP commands in handalso other usage may be possible.Signed-off-by: Harald Freudenberger Reviewed-by: Holger Dengler Signed-off-by: Heiko Carstens List of files: /linux/arch/s390/include/asm/trace/ap.h