(file:) ⋅ search

be remote or local nodes. Operations on a /dev/fw* file have different scope: - The 1394 node which is associated with the file: - Asynchronous request transmission - Get the Configuration ROM

stored in a circular buffer of size 3. These values are then used to calculate the minimum, maximum and average for each counter. After enabling, counters can be retrieved through the ``device_data`` file:: echo 3 > /sys/kernel/debug/qat_4xxx_0000:6b:00.0/telemetry/control

echo 32 > /sys/kernel/debug/qat_4xxx_0000:6b:00.0/telemetry/rp_C_data Once a ring pair is selected, statistics can be read accessing the file:: cat /sys/kernel/debug/qat_4xxx_0000:6b:00.0/telemetry/rp_C_data

Internal error types: 0x14 in fpu_etc.c 0x1nn in a *.c file: 0x101 in reg_add_sub.c 0x102 in reg_mul.c 0x104 in poly_atan.c

0x171 in fpu_tags.c 0x172 in fpu_tags.c 0x180 in reg_convert.c 0x2nn in an *.S file: 0x201 in reg_u_add.S 0x202 in reg_u_div.S 0x203 in reg_u_div.S

Example of the special SETXATTR_CHECK appraise rule, that restricts the hash algorithms allowed when writing to the security.ima xattr of a file: appraise func=SETXATTR_CHECK appraise_algos=sha256,sha384,sha512

Pss: 385 kB Pss_Dirty: 68 kB Pss_Anon: 301 kB Pss_File: 80 kB Pss_Shmem: 4 kB Shared_Clean: 696 kB Shared_Dirty: 0 kB

-r--r----- 1 root root 0 Jun 28 11:54 9553f55d-3da2-43ee-ab5d-ff17f78864d2 -r--r----- 1 root root 0 Jun 28 11:54 e6f5a162-d67f-4750-a67c-5d065f2a9910 Reading the secret data by reading a file:: # cat /sys/kernel/security/secrets/coco/e6f5a162-d67f-4750-a67c-5d065f2a9910

the-content-of-the-secret-data Wiping a secret by unlinking a file:: # rm /sys/kernel/security/secrets/coco/e6f5a162-d67f-4750-a67c-5d065f2a9910 # ls -l /sys/kernel/security/secrets/coco

* The end user reading this sysfs file must decode the content as per underlying platform/firmware. Possible error codes while reading this sysfs file: * "-EPERM" : Partition is not permitted to retrieve performance information, required to set "Enable Performance Information Collection" option.

response to H_SCM_HEALTH hcall. The details of the bit flags returned in response to this hcall is available at 'Documentation/arch/powerpc/papr_hcalls.rst' . Below are the flags reported in this sysfs file: * "not_armed" Indicates that NVDIMM contents will not

Some devices support "wakeup" events, which are hardware signals used to activate the system from a sleep state. Such devices have one of the following two values for the sysfs power/wakeup file: + "enabled\n" to issue the events; + "disabled\n" not to do so;

space to control the run-time power management of the device. All devices have one of the following two values for the power/control file: + "auto\n" to allow the device to be power managed at run time; + "on\n" to prevent the device from being power managed;

transitions (eg. suspend to RAM, hibernation). All devices have one of the following two values for the power/async file: + "enabled\n" to permit the asynchronous suspend/resume; + "disabled\n" to forbid it;

static LIST_HEAD(trace_list); /* struct remap_trace *//* * Locking in this file: * - mmiotrace_mutex enforces enable/disable_mmiotrace() critical sections. * - mmiotrace_enabled may be modified only when holding mmiotrace_mutex * and trace_lock.

of /sys/firmware/acpi/hotplug/. The following setting is available to user space for each hotplug profile: ======== ======================================================= enabled: If set, the ACPI core will handle notifications of

* @mode: open mode (BLK_OPEN_*) * @holder: exclusive holder identifier * @hops: holder operations * @bdev_file: file for the block device * * Open the block device. If @holder is not %NULL, the block device is opened * with exclusive access. Exclusive opens may nest for the same @holder.

/** * bdev_fput - yield claim to the block device and put the file * @bdev_file: open block device * * Yield claim on the block device and put the file. Ensure that the * block device can be reclaimed before the file is closed which is a

Description: This write-only file enables or disables periodic outputs. To enable a periodic output, write five integers into the file: channel index, start time seconds, start time nanoseconds, period seconds, and period nanoseconds. To disable a periodic output, set all the seconds and nanoseconds values to zero.

hwmgr->default_gfx_power_profile.type = AMD_PP_GFX_PROFILE; hwmgr->default_compute_power_profile.type = AMD_PP_COMPUTE_PROFILE; /* Optimize compute power profile: Use only highest * 2 power levels (if more than 2 are available) */ if (dpm_table->count > 2)

name gains ``SYNTH_ARG_`` prefix to avoid possible collisions with existing variables. Example of valid sequence written to the uevent file:: add fe4d7c9d-b8c6-4a70-9ef1-3d8a58d18eed A=1 B=abc

# $5 reST source folder relative to $(src),# e.g. "userspace-api/media" for the linux-tv book-set at ./Documentation/userspace-api/mediaquiet_cmd_sphinx = SPHINX $@ --> file://$(abspath $(BUILDDIR)/$3/$4) cmd_sphinx = $(MAKE) BUILDDIR=$(abspath $(BUILDDIR)) $(build)=Documentation/userspace-api/media $2 && \ PYTHONDONTWRITEBYTECODE=1 \ BUILDDIR=$(abspath $(BUILDDIR)) SPHINX_CONF=$(abspath $(src)/$5/$(SPHINX_CONF)) \

Use the Smack label in this attribute for access control decisions on packets coming from this socket.There are multiple ways to set a Smack label on a file:: # attr -S -s SMACK64 -V "value" path # chsmack -a value path

If you want Smack auditing of security events, you need to set CONFIG_AUDITin your kernel configuration.By default, all denied events will be audited. You can change this behavior bywriting a single character to the /sys/fs/smackfs/logging file:: 0 : no logging 1 : log denied (default)

return 0;err_file: device_remove_file(&client->dev, &dev_attr_priv_mem); return rval;

help Support for BT848 based frame grabber boards. This includes the Miro, Hauppauge and STB boards. Please read the material in <file:Documentation/admin-guide/media/bttv.rst> for more information. To compile this driver as a module, choose M here: the module will be called bttv.

kfree(blk_crypto_keyslots);fail_free_wq: destroy_workqueue(blk_crypto_wq);fail_destroy_profile:

blk_crypto_profile_destroy(blk_crypto_fallback_profile);fail_free_profile: kfree(blk_crypto_fallback_profile);fail_free_bioset: bioset_exit(&crypto_bio_split);

operation.For example, you can use the following bash script to create/update an EFIvariable with the content from a given file:: #!/bin/sh -e

/** * vidioc_querycap - return capabilities of device * @file: descriptor of device * @cap: contains return values * @priv: unused *

/** * vidioc_s_std - set video standard * @file: descriptor of device * @std: contains standard to be set * @priv: unused *

/** * vidioc_g_std - get video standard * @file: descriptor of device * @priv: unused * @std: contains return values *

/** * vidioc_querystd - get possible video standards * @file: descriptor of device * @priv: unused * @std: contains return values *

/** * vidioc_s_input - set input line * @file: descriptor of device * @priv: unused * @i: new input line number *

/** * vidioc_g_input - return input line * @file: descriptor of device * @priv: unused * @i: returned input line number *

/** * vidioc_enum_fmt_vid_cap - return video capture format * @file: descriptor of device * @priv: unused * @f: returned format information *

/** * vidioc_try_fmt_vid_cap - set video capture format * @file: descriptor of device * @priv: unused * @f: new format *

/** * vidioc_s_fmt_vid_cap - set current video format parameters * @file: descriptor of device * @priv: unused * @f: returned format information *

/** * vidioc_g_fmt_vid_cap - get current video format parameters * @file: descriptor of device * @priv: unused * @f: contains format information *

Each bit represents one pixel. If the bit is high, the pixel willturn on. If the pixel is low, the pixel will turn off.You can use the framebuffer as a file: fopen, fwrite, fclose...Although the LCD won't get updated until the next refresh time arrives.Also, you can mmap the framebuffer: open & mmap, munmap & close...

bash download-git-cache.sh rm download-git-cache.sh set +o xtrace S3_JWT_FILE: /s3_jwt S3_HOST: s3.freedesktop.org # This bucket is used to fetch the kernel image S3_KERNEL_BUCKET: mesa-rootfs

include: - project: 'freedesktop/ci-templates' ref: 16bc29078de5e0a067ff84a1a199a3760d3b3811 file: - '/templates/ci-fairy.yml'

- project: 'freedesktop/ci-templates' ref: *ci-templates-commit file: - '/templates/alpine.yml' - '/templates/debian.yml'

- '/templates/fedora.yml' - project: *drm-ci-project-path ref: *drm-ci-commit-sha file: - '/.gitlab-ci/container/gitlab-ci.yml' - '/.gitlab-ci/farm-rules.yml' - '/.gitlab-ci/lava/lava-gitlab-ci.yml'

we'll refer to "Oops" for all kinds of stack traces that need to be analyzed.If the kernel is compiled with ``CONFIG_DEBUG_INFO``, you can enhance thequality of the stack trace by using file:`scripts/decode_stacktrace.sh`.Modules linked in-----------------

Modules that are tainted or are being loaded or unloaded are marked with"(...)", where the taint flags are described infile:`Documentation/admin-guide/tainted-kernels.rst`, "being loaded" isannotated with "+", and "being unloaded" is annotated with "-".

`path:`	Only include results from matching files.	example
`-path:`	Exclude results from matching files.	example
`repo:`	Only include results from matching repositories.	example
`-repo:`	Exclude results from matching repositories.	example
`max_matches:`	Adjust the limit on number of matching lines returned.	example
`(special-term:)`	Escape one of the above terms by wrapping it in parentheses (with regex enabled).	example

Special query terms

Regular Expressions