Tags

Tags give the ability to mark specific points in history as being important
  • v4.9.316

    95302ce6 · Linux 4.9.316 ·
    This is the 4.9.316 stable release
    
  • folio-5.19

    Page cache changes for 5.19
    
     - Appoint myself page cache maintainer
    
     - Fix how scsicam uses the page cache
    
     - Use the memalloc_nofs_save() API to replace AOP_FLAG_NOFS
    
     - Remove the AOP flags entirely
    
     - Remove pagecache_write_begin() and pagecache_write_end()
    
     - Documentation updates
    
     - Convert several address_space operations to use folios:
       - is_dirty_writeback
       - readpage becomes read_folio
       - releasepage becomes release_folio
       - freepage becomes free_folio
    
     - Change filler_t to require a struct file pointer be the first argument
       like ->read_folio
    
  • x86_vdso_for_v5.19_rc1

    - Get rid of CONFIG_LEGACY_VSYSCALL_EMULATE as nothing should be using it anymore
    
  • x86_microcode_for_v5.19_rc1

    - Make CPU vendor dependency explicit against random config build failures
    
  • x86_misc_for_v5.19_rc1

    - A gargen variety of fixes which don't fit any other tip bucket:
     - Remove function export
     - Correct asm constraint
     - Fix __setup handlers retval
    
  • x86_splitlock_for_v5.19_rc1

    - Add Raptor Lake to the set of CPU models which support splitlock
    
    - Make life miserable for apps using split locks by slowing them down
    considerably while the rest of the system remains responsive. The hope
    is it will hurt more and people will really fix their misaligned locks
    apps. As a result, free a TIF bit.
    
  • x86_apic_for_v5.19_rc1

    - Always do default APIC routing setup so that cpumasks are properly
    allocated and are present when later accessed ("nosmp" and x2APIC)
    
    - Clarify the bit overlap between an old APIC and a modern, integrated one
    
  • x86_kdump_for_v5.19_rc1

    - A single debug message fix
    
  • x86_platform_for_v5.19_rc1

    - A couple of changes enabling SGI UV5 support
    
  • sched-core-2022-05-23

    Scheduler changes in this cycle were:
    
     - Updates to scheduler metrics:
    
        - PELT fixes & enhancements
        - PSI fixes & enhancements
        - Refactor cpu_util_without()
    
     - Updates to instrumentation/debugging:
    
        - Remove sched_trace_*() helper functions - can be done via debug info
        - Fix double update_rq_clock() warnings
    
     - Introduce & use "preemption model accessors" to simplify some of
       the Kconfig complexity.
    
     - Make softirq handling RT-safe.
    
     - Misc smaller fixes & cleanups.
    
    Signed-off-by: Ingo Molnar <mingo@kernel.org>
    
  • perf-core-2022-05-23

    Perf events changes for this cycle were:
    
    Platform PMU changes:
    =====================
    
     - x86/intel:
        - Add new Intel Alder Lake and Raptor Lake support
    
     - x86/amd:
        - AMD Zen4 IBS extensions support
        - Add AMD PerfMonV2 support
        - Add AMD Fam19h Branch Sampling support
    
    Generic changes:
    ================
    
     - signal: Deliver SIGTRAP on perf event asynchronously if blocked
    
       Perf instrumentation can be driven via SIGTRAP, but this causes a problem
       when SIGTRAP is blocked by a task & terminate the task.
    
       Allow user-space to request these signals asynchronously (after they get
       unblocked) & also give the information to the signal handler when this
       happens:
    
         " To give user space the ability to clearly distinguish synchronous from
           asynchronous signals, introduce siginfo_t::si_perf_flags and
           TRAP_PERF_FLAG_ASYNC (opted for flags in case more binary information is
           required in future).
    
           The resolution to the problem is then to (a) no longer force the signal
           (avoiding the terminations), but (b) tell user space via si_perf_flags
           if the signal was synchronous or not, so that such signals can be
           handled differently (e.g. let user space decide to ignore or consider
           the data imprecise). "
    
     - Unify/standardize the /sys/devices/cpu/events/* output format.
    
     - Misc fixes & cleanups.
    
    Signed-off-by: Ingo Molnar <mingo@kernel.org>
    
  • objtool-core-2022-05-23

    Objtool changes for this cycle were:
    
     - Comprehensive interface overhaul:
       =================================
    
       Objtool's interface has some issues:
    
         - Several features are done unconditionally, without any way to turn
           them off.  Some of them might be surprising.  This makes objtool
           tricky to use, and prevents porting individual features to other
           arches.
    
         - The config dependencies are too coarse-grained.  Objtool enablement is
           tied to CONFIG_STACK_VALIDATION, but it has several other features
           independent of that.
    
         - The objtool subcmds ("check" and "orc") are clumsy: "check" is really
           a subset of "orc", so it has all the same options.  The subcmd model
           has never really worked for objtool, as it only has a single purpose:
           "do some combination of things on an object file".
    
         - The '--lto' and '--vmlinux' options are nonsensical and have
           surprising behavior.
    
       Overhaul the interface:
    
          - get rid of subcmds
    
          - make all features individually selectable
    
          - remove and/or clarify confusing/obsolete options
    
          - update the documentation
    
          - fix some bugs found along the way
    
     - Fix x32 regression
    
     - Fix Kbuild cleanup bugs
    
     - Add scripts/objdump-func helper script to disassemble a single function from an object file.
    
     - Rewrite scripts/faddr2line to be section-aware, by basing it on 'readelf',
       moving it away from 'nm', which doesn't handle multiple sections well,
       which can result in decoding failure.
    
     - Rewrite & fix symbol handling - which had a number of bugs wrt. object files
       that don't have global symbols - which is rare but possible. Also fix a
       bunch of symbol handling bugs found along the way.
    
    Signed-off-by: Ingo Molnar <mingo@kernel.org>
    
  • x86_fpu_for_v5.19_rc1

    - Add support for XSAVEC - the Compacted XSTATE saving variant - and
    thus allow for guests to use this compacted XSTATE variant when the
    hypervisor exports that support
    
    - A variable shadowing cleanup
    
  • locking-core-2022-05-23

    Locking changes in this cycle were:
    
     - rwsem cleanups & optimizations/fixes:
        - Conditionally wake waiters in reader/writer slowpaths
        - Always try to wake waiters in out_nolock path
    
     - Add try_cmpxchg64() implementation, with arch optimizations - and use it to
       micro-optimize sched_clock_{local,remote}()
    
     - Various force-inlining fixes to address objdump instrumentation-check warnings
    
     - Add lock contention tracepoints:
    
        lock:contention_begin
        lock:contention_end
    
     - Misc smaller fixes & cleanups
    
    Signed-off-by: Ingo Molnar <mingo@kernel.org>
    
  • x86_core_for_v5.19_rc1

    - Remove all the code around GS switching on 32-bit now that it is not
    needed anymore
    
    - Other misc improvements
    
  • Ubuntu-hwe-5.13-5.13.0-46.51_20.04.1

    Ubuntu-hwe-5.13-5.13.0-46.51~20.04.1
    
  • x86_cleanups_for_v5.19_rc1

    d936411d · x86: Remove empty files ·
    - Serious sanitization and cleanup of the whole APERF/MPERF and
    frequency invariance code along with removing the need for unnecessary IPIs
    
    - Finally remove a.out support
    
    - The usual trivial cleanups and fixes all over x86
    
  • x86_build_for_v5.19_rc1

    - Add a "make x86_debug.config" target which enables a bunch of useful
    config debug options when trying to debug an issue
    
    - A gcc12 build warnings fix