| /linux/drivers/media/radio/ |
| 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()
|
| A D | Makefile | 20 obj-$(CONFIG_RADIO_TRUST) += radio-trust.o
|
| /linux/tools/testing/selftests/rcutorture/bin/ |
| A D | torture.sh | 342 …bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "$configs_rcutorture" --trust-make
348 …ure lock --allcpus --duration "$duration_locktorture" --configs "$configs_locktorture" --trust-make
354 …onfigs "$configs_scftorture" --kconfig "CONFIG_NR_CPUS=$HALF_ALLOTED_CPUS" --memory 1G --trust-make
378 …-torture rcuscale --allcpus --duration 5 --kconfig "CONFIG_NR_CPUS=$HALF_ALLOTED_CPUS" --trust-make
384 …cale --allcpus --duration 10 --kconfig "CONFIG_NR_CPUS=$HALF_ALLOTED_CPUS" --memory 1G --trust-make
390 …allcpus --duration 45s --configs TREE03 --kconfig "CONFIG_TEST_CLOCKSOURCE_WATCHDOG=y" --trust-make
393 …allcpus --duration 45s --configs TREE03 --kconfig "CONFIG_TEST_CLOCKSOURCE_WATCHDOG=y" --trust-make
399 …ools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 45s --configs TREE03 --trust-make
|
| A D | parse-build.sh | 24 if grep -q CC < $F || test -n "$TORTURE_TRUST_MAKE" || grep -qe --trust-make < `dirname $F`/../log
|
| A D | kvm-check-branches.sh | 76 kvm.sh --allcpus --duration 3 --trust-make > $resdir/$ds/$idir/kvm.sh.out 2>&1
|
| A D | kvm.sh | 243 --trust-make)
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| 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
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/Documentation/security/keys/ |
| 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.
90 New keys are created from random numbers generated in the trust source. They
93 access control policy within the trust source.
109 Encrypted keys do not depend on a trust source, and are faster, as they use AES
|
| /linux/Documentation/x86/ |
| 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/namespaces/ |
| 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/include/linux/qed/ |
| A D | qed_iov_if.h | 31 int (*set_trust) (struct qed_dev *cdev, int vfid, bool trust);
|
| /linux/drivers/net/ethernet/broadcom/bnxt/ |
| 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/ |
| A D | hinic_sriov.c | 352 if (vf_info->pf_set_mac && !(vf_info->trust) && in hinic_set_vf_mac_msg_handler()
566 ivi->trusted = vfinfo->trust; in hinic_get_vf_config()
792 bool trust) in hinic_set_vf_trust() argument
802 vf_infos[vf_id].trust = trust; in hinic_set_vf_trust()
821 cur_trust = nic_io->vf_infos[vf].trust; in hinic_ndo_set_vf_trust()
1132 if (vf_infos->trust) in hinic_clear_vf_infos()
|
| A D | hinic_sriov.h | 46 bool trust; member
|
| /linux/Documentation/process/ |
| 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
179 - sign other people's keys for web of trust purposes
526 trust: ultimate validity: ultimate
876 PGP incorporates a trust delegation mechanism known as the "Web of
886 "the SSH-like approach to trust." With SSH, the first time you connect
890 trust the changed key or not. Similarly, the first time you import
896 We recommend that you use the combined TOFU+PGP trust model (which is
898 ``trust-model`` setting in ``~/.gnupg/gpg.conf``::
900 trust-model tofu+pgp
[all …]
|
| 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
|
| /linux/Documentation/admin-guide/media/ |
| A D | radio-cardlist.rst | 31 radio-trust Trust FM radio card
|
| /linux/Documentation/hwmon/ |
| A D | lm63.rst | 75 is left to the BIOS, and the driver will blindly trust it. Only the original
|
| A D | dell-smm-hwmon.rst | 107 other users and you don't trust them you may want
|
| /linux/Documentation/devicetree/bindings/remoteproc/ |
| A D | st,stm32-rproc.yaml | 40 Reference to the system configuration which holds the RCC trust zone mode
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-class-cxl | 251 0 don't trust, the image may be different (default)
252 1 trust that the image will not change.
|
| /linux/Documentation/usb/ |
| A D | authorization.rst | 94 can fake descriptors and device info. Don't trust that. You are
|
| /linux/Documentation/security/tpm/ |
| A D | xen-tpmfront.rst | 21 the chain of trust rooted in the hardware TPM to virtual machines in Xen. Each
|
| /linux/Documentation/dev-tools/kunit/ |
| A D | index.rst | 85 someone sends you some code. Why trust that someone ran all their tests
|
| /linux/Documentation/i2c/ |
| A D | functionality.rst | 9 I2C specifications, a client can not trust that everything it needs
|