Home
last modified time | relevance | path

Searched refs:trust (Results 1 – 25 of 87) sorted by relevance

1234

/linux-6.15/drivers/media/radio/
H A Dradio-trust.c51 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()
H A DMakefile31 obj-$(CONFIG_RADIO_TRUST) += radio-trust.o
/linux-6.15/tools/testing/selftests/rcutorture/bin/
H A Dtorture.sh410 …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 Dparse-build.sh23 if grep -q CC < $F || test -n "$TORTURE_TRUST_MAKE" || grep -qe --trust-make < `dirname $F`/../log
H A Dsrcu_lockdep.sh52 …otargs "rcutorture.test_srcu_lockdep=$val rcutorture.reader_flavor=0x2" --trust-make --datestamp "…
H A Dkvm-check-branches.sh76 …kvm.sh --allcpus --duration 3 --trust-make --datestamp "$ds/$idir" > $resdir/$ds/$idir/kvm.sh.out …
/linux-6.15/drivers/net/ethernet/microchip/lan966x/
H A Dlan966x_dcb.c277 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-6.15/Documentation/admin-guide/hw-vuln/
H A Dcore-scheduling.rst8 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
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
199 For both MDS and L1TF, if the guest vCPU is configured to not trust each
[all …]
/linux-6.15/drivers/net/ethernet/microchip/sparx5/
H A Dsparx5_dcb.c319 const struct sparx5_dcb_apptrust *trust; in sparx5_dcb_getapptrust() local
321 trust = sparx5_port_apptrust[port->portno]; in sparx5_dcb_getapptrust()
323 memcpy(selectors, trust->selectors, trust->nselectors); in sparx5_dcb_getapptrust()
324 *nselectors = trust->nselectors; in sparx5_dcb_getapptrust()
/linux-6.15/Documentation/admin-guide/namespaces/
H A Dresource-control.rst8 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-6.15/Documentation/security/keys/
H A Dtrusted-encrypted.rst17 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
136 trust source. The random number generator in use differs according to the
[all …]
/linux-6.15/Documentation/arch/x86/
H A Dintel_txt.rst13 - 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-6.15/Documentation/admin-guide/LSM/
H A Dipe.rst28 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.
758 trust-based access control?
[all …]
/linux-6.15/include/linux/qed/
H A Dqed_iov_if.h31 int (*set_trust) (struct qed_dev *cdev, int vfid, bool trust);
/linux-6.15/drivers/net/ethernet/netronome/nfp/nic/
H A Ddcb.c178 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-6.15/Documentation/devicetree/bindings/remoteproc/
H A Dst,stm32-rproc.yaml49 Reference to the system configuration which holds the RCC trust zone mode
54 - description: The offset of the trust zone setting register
55 - description: The field mask of the trust zone state
/linux-6.15/drivers/net/ethernet/broadcom/bnxt/
H A Dbnxt_sriov.h38 int bnxt_set_vf_trust(struct net_device *dev, int vf_id, bool trust);
/linux-6.15/include/linux/pds/
H A Dpds_core_if.h375 u8 trust; member
415 u8 trust; member
/linux-6.15/drivers/net/ethernet/huawei/hinic/
H A Dhinic_sriov.c353 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 Dhinic_sriov.h46 bool trust; member
/linux-6.15/security/ipe/
H A DKconfig17 allowing users to define a policy to enforce a trust-based access
19 admins to reconfigure trust requirements on the fly.
/linux-6.15/security/keys/trusted-keys/
H A DKconfig51 comment "No trust source selected!"
/linux-6.15/Documentation/translations/zh_CN/process/
H A Dmaintainer-pgp-guide.rst416 trust: ultimate validity: ultimate
774 ``trust-model`` 设置::
776 trust-model tofu+pgp
/linux-6.15/Documentation/translations/zh_CN/security/tpm/
H A Dtpm-security.rst147 .. _TPM Genie: https://www.nccgroup.trust/globalassets/about-us/us/documents/tpm-genie.pdf
/linux-6.15/Documentation/process/
H A Dmaintainer-pgp-guide.rst47 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
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``::
904 trust-model tofu+pgp
[all …]

1234