| /linux/drivers/media/radio/ |
| H A D | radio-trust.c | 51 struct trust { struct 58 struct trust *tr = kzalloc_obj(*tr); in trust_alloc() argument 73 static void write_i2c(struct trust *tr, int n, ...) in write_i2c() 121 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_mute_volume() 131 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_stereo() 149 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_frequency() 166 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_ctrl() 185 struct trust *tr = container_of(isa, struct trust, isa); in trust_initialize()
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | core-scheduling.rst | 8 group of tasks don't trust another), or for performance usecases (some 96 mentioned in `Usage`_, tasks with the same cookie value are assumed to trust 121 The scheduler tries its best to find tasks that trust each other such that all 151 Core scheduling maintains trust relationships amongst groups of tasks by 153 When a system with core scheduling boots, all tasks are considered to trust 155 trust relationships until userspace uses the above mentioned interfaces, to 161 within such groups are considered to trust each other, but do not trust those 162 outside. Tasks outside the group also don't trust tasks within. 187 siblings run tasks which trust each other, when the kernel is executing 188 code on behalf of a task, it cannot trust the code running in the [all …]
|
| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | torture.sh | 475 tools/testing/selftests/rcutorture/bin/kvm.sh --datestamp "$ds/results-rcutasksflavors/$flavor" --buildonly --configs "TINY01 TREE04" --kconfig "CONFIG_RCU_EXPERT=y CONFIG_RCU_SCALE_TEST=y CONFIG_KPROBES=n CONFIG_RCU_TRACE=n CONFIG_TRACING=n CONFIG_BLK_DEV_IO_TRACE=n CONFIG_UPROBE_EVENTS=n $forceflavor=y $deselectedflavors" --trust-make > $T/$flavor.out 2>&1 497 torture_set "rcutorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "$configs_rcutorture" --trust-make 503 torture_set "locktorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture lock --allcpus --duration "$duration_locktorture" --configs "$configs_locktorture" --trust-make 511 torture_set "scftorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture scf --allcpus --duration "$duration_scftorture" --configs "$configs_scftorture" --kconfig "CONFIG_NR_CPUS=$SCALE_ALLOTED_CPUS" --memory ${scfmem}G --trust-make 522 torture_set "rcurttorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "TREE03" --kconfig "CONFIG_PREEMPT_RT=y CONFIG_EXPERT=y CONFIG_HZ_PERIODIC=n CONFIG_NO_HZ_IDLE=y CONFIG_RCU_NOCB_CPU=y" --trust-make 526 torture_set "rcurttorture-exp" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "TREE03" --kconfig "CONFIG_PREEMPT_RT=y CONFIG_EXPERT=y CONFIG_HZ_PERIODIC=n CONFIG_NO_HZ_FULL=y CONFIG_RCU_NOCB_CPU=y" --trust-make 601 torture_set "refscale-$prim" tools/testing/selftests/rcutorture/bin/kvm.sh --torture refscale --allcpus --duration 5 --kconfig "CONFIG_TASKS_TRACE_RCU=y CONFIG_NR_CPUS=$SCALE_ALLOTED_CPUS" --bootargs "refscale.verbose_batched=$VERBOSE_BATCH_CPUS torture.verbose_sleep_frequency=8 torture.verbose_sleep_duration=$VERBOSE_BATCH_CPUS" --trust-make 650 torture_set "rcuscale-$prim" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --allcpus --duration 5 --kconfig "CONFIG_TASKS_TRACE_RCU=y CONFIG_NR_CPUS=$SCALE_ALLOTED_CPUS" --trust-make 688 torture_set "rcuscale-kvfree" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --allcpus --duration $duration_rcutorture --kconfig "CONFIG_NR_CPUS=$SCALE_ALLOTED_CPUS" --memory 2G --trust-make 694 torture_set "clocksourcewd-1" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 45s --configs TREE03 --kconfig "CONFIG_TEST_CLOCKSOURCE_WATCHDOG=y" --trust [all...] |
| H A D | parse-build.sh | 23 if grep -q CC < $F || test -n "$TORTURE_TRUST_MAKE" || grep -qe --trust-make < `dirname $F`/../log
|
| H A D | kvm-check-branches.sh | 76 …kvm.sh --allcpus --duration 3 --trust-make --datestamp "$ds/$idir" > $resdir/$ds/$idir/kvm.sh.out …
|
| /linux/drivers/net/ethernet/microchip/lan966x/ |
| H A D | lan966x_dcb.c | 277 const struct lan966x_dcb_apptrust *trust; in lan966x_dcb_getapptrust() local 279 trust = lan966x_port_apptrust[port->chip_port]; in lan966x_dcb_getapptrust() 281 memcpy(selectors, trust->selectors, trust->nselectors); in lan966x_dcb_getapptrust() 282 *nselectors = trust->nselectors; in lan966x_dcb_getapptrust()
|
| /linux/Documentation/arch/x86/ |
| H A D | intel_txt.rst | 13 - Provides dynamic root of trust for measurement (DRTM) 34 http://www.trust-conference.eu/downloads/Keynote-Speakers/ 67 To get trust in the initial kernel without using Intel TXT, a 68 static root of trust must be used. This bases trust in BIOS 81 By using the hardware-based root of trust that Intel TXT provides, 83 pre-launch components can be removed from the trust chain, DMA 91 almost all parts of the trust chain is available (excepting SMM and 101 processor instruction that initiates the dynamic root of trust.
|
| /linux/Documentation/gpu/nova/core/ |
| H A D | falcon.rst | 36 root of trust. For example, the FWSEC-FRTS command (see fwsec.rst) runs on the 46 root of trust. For example, in the case of an Ampere GPU, the CPU runs the "Booter" 52 Root of trust establishment 54 To establish a root of trust, the code running on a Falcon must be immutable and 70 The root of trust is therefore established as follows:
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | ipe.rst | 28 unchangeable over time. For example, IPE policies can be crafted to trust 35 integrity and trust. For example, IPE allows the definition of policies 36 that trust files from a dm-verity protected device. dm-verity ensures the 39 checks, allowing IPE to enforce policies that trust files protected by 56 requirements and trust models. 71 community as a whole tends to follow a decentralized trust model (known as 72 the web of trust), which IPE has no support for it yet. Instead, IPE 74 set of trusted entities that provide a measure of absolute trust. 91 for IPE to ensure the integrity of this code to form a trust basis. 185 can determine the trust of the resource based on the value of the property. [all …]
|
| /linux/drivers/net/ethernet/netronome/nfp/nic/ |
| H A D | dcb.c | 178 u8 trust; in nfp_nic_set_trust() local 185 trust = dcb->dscp_cnt > 0 ? NFP_DCB_TRUST_DSCP : NFP_DCB_TRUST_PCP; in nfp_nic_set_trust() 186 writeb(trust, dcb->dcbcfg_tbl + dcb->cfg_offset + in nfp_nic_set_trust() 189 dcb->trust_status = trust; in nfp_nic_set_trust()
|
| /linux/include/linux/qed/ |
| H A D | qed_iov_if.h | 31 int (*set_trust) (struct qed_dev *cdev, int vfid, bool trust);
|
| /linux/include/linux/pds/ |
| H A D | pds_core_if.h | 375 u8 trust; member 415 u8 trust; member
|
| /linux/drivers/net/ethernet/huawei/hinic/ |
| H A D | hinic_sriov.c | 353 if (vf_info->pf_set_mac && !(vf_info->trust) && in hinic_set_vf_mac_msg_handler() 585 ivi->trusted = vfinfo->trust; in hinic_get_vf_config() 811 bool trust) in hinic_set_vf_trust() argument 821 vf_infos[vf_id].trust = trust; in hinic_set_vf_trust() 840 cur_trust = nic_io->vf_infos[vf].trust; in hinic_ndo_set_vf_trust() 1145 if (vf_infos->trust) in hinic_clear_vf_infos()
|
| H A D | hinic_sriov.h | 46 bool trust; member
|
| /linux/Documentation/admin-guide/namespaces/ |
| H A D | resource-control.rst | 8 where the admins don't trust their users or their users' programs,
|
| /linux/Documentation/translations/zh_CN/process/ |
| H A D | maintainer-pgp-guide.rst | 416 trust: ultimate validity: ultimate 774 ``trust-model`` 设置:: 776 trust-model tofu+pgp
|
| /linux/Documentation/virt/coco/ |
| H A D | tdx-guest.rst | 50 https://www.intel.com/content/www/us/en/developer/articles/technical/intel-trust-domain-extensions.…
|
| /linux/Documentation/security/ |
| H A D | ipe.rst | 179 access based on the trust of the system's resources, it's policy must also be 229 compiled into the kernel will need some flexibility to express how trust 251 done via a signature chained to a trust source in the kernel. Arbitrarily, 388 the evaluation, like any other file. However, all current trust properties will 396 scenario all current trust properties will also evaluate to false.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-virtual-misc-tdx_guest | 14 …https://www.intel.com/content/www/us/en/developer/tools/trust-domain-extensions/documentation.html…
|
| /linux/Documentation/maintainer/ |
| H A D | feature-and-driver-maintainers.rst | 128 foundation of kernel maintenance and one cannot build trust with a mailing 137 together by (rarely expressed) mutual respect, trust and convenience.
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm-security.rst | 48 trust measurements. 93 we establish trust on the null seed at start of day, all sessions 212 .. _TPM Genie: https://www.nccgroup.trust/globalassets/about-us/us/documents/tpm-genie.pdf
|
| H A D | xen-tpmfront.rst | 21 the chain of trust rooted in the hardware TPM to virtual machines in Xen. Each
|
| /linux/Documentation/hwmon/ |
| H A D | lm63.rst | 75 is left to the BIOS, and the driver will blindly trust it. Only the original
|
| /linux/Documentation/usb/ |
| H A D | authorization.rst | 91 can fake descriptors and device info. Don't trust that. You are
|
| /linux/Documentation/process/ |
| H A D | management-style.rst | 95 deleting it, you may have irrevocably lost the trust of that 176 trust somebody who is so clearly hiding their true character. 236 It's part of what makes people trust you, and allow you the potential
|