/linux/drivers/media/radio/ |
H A D | radio-trust.c | 51 struct trust { struct 58 struct trust *tr = kzalloc(sizeof(*tr), GFP_KERNEL); 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/tools/testing/selftests/rcutorture/bin/ |
H A D | torture.sh | 410 …EV_IO_TRACE=n CONFIG_UPROBE_EVENTS=n $forceflavor=y $deselectedflavors" --trust-make > $T/$flavor.… 432 …bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "$configs_rcutorture" --trust-make 438 …ure lock --allcpus --duration "$duration_locktorture" --configs "$configs_locktorture" --trust-make 446 …configs_scftorture" --kconfig "CONFIG_NR_CPUS=$SCALE_ALLOTED_CPUS" --memory ${scfmem}G --trust-make 453 …s/rcutorture/bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "TREE03" --trust-make 457 …s/rcutorture/bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "TREE03" --trust-make 540 …s --duration 5 --kconfig "CONFIG_TASKS_TRACE_RCU=y CONFIG_NR_CPUS=$SCALE_ALLOTED_CPUS" --trust-make 578 …ration $duration_rcutorture --kconfig "CONFIG_NR_CPUS=$SCALE_ALLOTED_CPUS" --memory 2G --trust-make 584 …allcpus --duration 45s --configs TREE03 --kconfig "CONFIG_TEST_CLOCKSOURCE_WATCHDOG=y" --trust-make 587 …allcpus --duration 45s --configs TREE03 --kconfig "CONFIG_TEST_CLOCKSOURCE_WATCHDOG=y" --trust-make [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 | srcu_lockdep.sh | 52 …on 5s --configs "SRCU-P" --bootargs "rcutorture.test_srcu_lockdep=$val" --trust-make --datestamp "…
|
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/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/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/admin-guide/namespaces/ |
H A D | resource-control.rst | 8 enabled in a kernel for people who don't trust their users or their 14 memory user's they don't trust to play nice can use.
|
/linux/Documentation/security/keys/ |
H A D | trusted-encrypted.rst | 17 A trust source provides the source of security for Trusted Keys. This 18 section lists currently supported trust sources, along with their security 19 considerations. Whether or not a trust source is sufficiently safe depends 22 environment is, and there is no metric of trust, it is dependent on the 23 consumer of the Trusted Keys to determine if the trust source is sufficiently 26 * Root of trust for storage 31 provides crypto operation to establish root of trust for storage. 41 mode, trust is rooted to the OTPMK, a never-disclosed 256-bit key 49 DCP provides two keys that can be used as root of trust: the OTP key 123 The strength and appropriateness of a particular trust source for a given [all …]
|
/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/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. 172 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/broadcom/bnxt/ |
H A D | bnxt_sriov.h | 38 int bnxt_set_vf_trust(struct net_device *dev, int vf_id, bool trust);
|
/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/security/ipe/ |
H A D | Kconfig | 17 allowing users to define a policy to enforce a trust-based access 19 admins to reconfigure trust requirements on the fly.
|
/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/security/keys/trusted-keys/ |
H A D | Kconfig | 51 comment "No trust source selected!"
|
/linux/Documentation/process/ |
H A D | maintainer-pgp-guide.rst | 47 that trust must always be placed with developers and never with the code 52 want to make sure that by placing trust into developers we do not simply 160 - sign other people's keys for web of trust purposes 485 trust: ultimate validity: ultimate 848 delegated trust technologies, namely DNSSEC and TLS, to get you going if 880 PGP incorporates a trust delegation mechanism known as the "Web of 890 "the SSH-like approach to trust." With SSH, the first time you connect 894 trust the changed key or not. Similarly, the first time you import 900 We recommend that you use the combined TOFU+PGP trust model (which is 902 ``trust-model`` setting in ``~/.gnupg/gpg.conf``:: [all …]
|
/linux/Documentation/admin-guide/media/ |
H A D | radio-cardlist.rst | 31 radio-trust Trust FM radio card
|
/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/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.
|