summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/netdev-times.py
diff options
context:
space:
mode:
authorMatt Fleming <matt.fleming@intel.com>2014-09-30 21:58:52 +0100
committerMatt Fleming <matt.fleming@intel.com>2014-10-03 18:41:03 +0100
commit6d80dba1c9fe4316ef626980102b92fa30c7845a (patch)
tree7d2d4551430d392af7dab18ff755fab1e422fb7b /tools/perf/scripts/python/netdev-times.py
parent77e21e87acec8c857df4bfbc647ea21d0a87364d (diff)
downloadkernel-6d80dba1c9fe4316ef626980102b92fa30c7845a.tar.gz
efi: Provide a non-blocking SetVariable() operation
There are some circumstances that call for trying to write an EFI variable in a non-blocking way. One such scenario is when writing pstore data in efi_pstore_write() via the pstore_dump() kdump callback. Now that we have an EFI runtime spinlock we need a way of aborting if there is contention instead of spinning, since when writing pstore data from the kdump callback, the runtime lock may already be held by the CPU that's running the callback if we crashed in the middle of an EFI variable operation. The situation is sufficiently special that a new EFI variable operation is warranted. Introduce ->set_variable_nonblocking() for this use case. It is an optional EFI backend operation, and need only be implemented by those backends that usually acquire locks to serialize access to EFI variables, as is the case for virt_efi_set_variable() where we now grab the EFI runtime spinlock. Cc: Peter Zijlstra <peterz@infradead.org> Cc: Ingo Molnar <mingo@kernel.org> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org> Cc: Matthew Garrett <mjg59@srcf.ucam.org> Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/netdev-times.py')
0 files changed, 0 insertions, 0 deletions
7b37ba963949ffbef25'>arm64: dts: renesas: r8a779g0: Add Cortex-A76 1.8 GHz oppGeert Uytterhoeven 2023-01-10arm64: dts: renesas: r8a779g0: Add display related nodesTomi Valkeinen 2022-11-17arm64: dts: renesas: r8a779g0: Add CA76 operating pointsGeert Uytterhoeven 2022-11-17arm64: dts: renesas: r8a779g0: Add CPU core clocksGeert Uytterhoeven 2022-11-17arm64: dts: renesas: r8a779g0: Add CPUIdle supportGeert Uytterhoeven 2022-11-17arm64: dts: renesas: r8a779g0: Add secondary CA76 CPU coresGeert Uytterhoeven 2022-11-17arm64: dts: renesas: r8a779g0: Add L3 cache controllerGeert Uytterhoeven 2022-11-08arm64: dts: renesas: r8a779g0: Add CMT nodeThanh Quan 2022-11-08arm64: dts: renesas: r8a779g0: Add TMU nodesWolfram Sang 2022-10-24arm64: dts: renesas: r8a779g0: Add remaining HSCIF nodesGeert Uytterhoeven 2022-10-24arm64: dts: renesas: r8a779g0: Add SCIF nodesGeert Uytterhoeven 2022-10-17arm64: dts: renesas: r8a779g0: Add RPC nodeHai Pham 2022-10-17arm64: dts: renesas: r8a779g0: Add SDHI nodeGeert Uytterhoeven 2022-10-17arm64: dts: renesas: r8a779g0: Add TPU device nodeCongDang 2022-10-17arm64: dts: renesas: r8a779g0: Add PWM device nodesCongDang 2022-10-17arm64: dts: renesas: r8a779g0: Fix HSCIF0 "brg_int" clockGeert Uytterhoeven 2022-10-17arm64: dts: renesas: r8a779g0: Add INTC-EX nodeGeert Uytterhoeven 2022-10-17arm64: dts: renesas: r8a779g0: Add MSIOF nodesGeert Uytterhoeven 2022-10-17arm64: dts: renesas: r8a779g0: Add DMA supportGeert Uytterhoeven 2022-09-19arm64: dts: renesas: r8a779g0: Add RAVB nodesGeert Uytterhoeven 2022-09-19arm64: dts: renesas: r8a779g0: Add GPIO nodesGeert Uytterhoeven 2022-09-18arm64: dts: renesas: r8a779g0: Add I2C nodesGeert Uytterhoeven 2022-09-18arm64: dts: renesas: r8a779g0: Add pinctrl device nodeGeert Uytterhoeven 2022-09-18arm64: dts: renesas: r8a779g0: Add RWDT nodeGeert Uytterhoeven 2022-08-29arm64: dts: renesas: r8a779g0: Fix HSCIF0 interrupt numberGeert Uytterhoeven 2022-05-06arm64: dts: renesas: Add Renesas R8A779G0 SoC supportYoshihiro Shimoda