Home
last modified time | relevance | path

Searched refs:topic (Results 1 – 25 of 41) sorted by relevance

12

/linux/tools/perf/tests/
H A Dpmu-events.c51 .topic = "branch",
63 .topic = "branch",
75 .topic = "other",
87 .topic = "other",
99 .topic = "other",
112 .topic = "cache",
133 .topic = "uncore",
147 .topic = "uncore",
161 .topic = "uncore",
175 .topic = "uncore",
[all …]
/linux/drivers/accel/habanalabs/common/
H A Dmemory_mgr.c165 behavior->topic, rc); in hl_mmap_mem_buf_alloc()
177 behavior->topic, rc); in hl_mmap_mem_buf_alloc()
257 buf->behavior->topic, user_mem_size, buf->mappable_size);
270 buf->behavior->topic, vma->vm_start);
279 buf->behavior->topic);
359 const char *topic; local
368 topic = buf->behavior->topic;
373 topic, id);
H A Dcommand_buffer.c259 .topic = "CB",
/linux/Documentation/process/
H A Dmaintainer-kvm-x86.rst38 The KVM x86 tree is organized into multiple topic branches. The purpose of
39 using finer-grained topic branches is to make it easier to keep tabs on an area
41 commits, e.g. dropping the HEAD commit of a topic branch has no impact on other
43 delays only that topic branch.
45 All topic branches, except for ``next`` and ``fixes``, are rolled into ``next``
46 via a Cthulhu merge on an as-needed basis, i.e. when a topic branch is updated.
55 requests (from KVM x86 to main KVM) are sent for each KVM x86 topic branch,
57 following rc7 for "normal" releases. If all goes well, the topic branches are
94 select a specific topic branch as the base. If there are conflicts and/or
95 dependencies across topic branches, it is the maintainer's job to sort them
[all …]
H A D7.AdvancedTopics.rst61 of development can be separated into a separate "topic branch" and
118 thing happening; putting up a git tree with unreviewed or off-topic patches
131 branch stick closely to the associated topic; a "driver fixes" branch
H A Dstable-api-nonsense.rst104 This is a much more "volatile" topic if you talk to people who try to
/linux/Documentation/hwmon/
H A Dvexpress.rst15 - http://infocenter.arm.com/help/topic/com.arm.doc.subset.boards.express/index.html
19 - http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0447-/index.html
H A Dscpi-hwmon.rst10 Datasheet: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/index.html
H A Dltc2990.rst19 - Mike Looijmans <mike.looijmans@topic.nl>
/linux/tools/perf/pmu-events/
H A DREADME26 such as Pipelining, Cache, Memory, Floating-point etc. All events for a topic
28 the topic. Eg: "Floating-point.json".
30 All the topic JSON files for a CPU model/family should be in a separate
/linux/Documentation/admin-guide/hw-vuln/
H A Dreg-file-data-sampling.rst104 …https://www.intel.com/content/www/us/en/developer/topic-technology/software-security-guidance/proc…
H A Dprocessor_mmio_stale_data.rst271 …https://www.intel.com/content/www/us/en/developer/topic-technology/software-security-guidance/proc…
/linux/Documentation/filesystems/
H A Dbefs.rst70 reference on this topic. http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-4.html
/linux/Documentation/arch/arm/
H A Dmicrochip.rst225 When collecting nodes for a particular peripheral or topic, the identifier have to
/linux/Documentation/kbuild/
H A Dreproducible-builds.rst13 general topic. This document covers the various reasons why building
/linux/Documentation/maintainer/
H A Drebasing-and-merging.rst100 which may contain multiple topic branches; each branch is usually developed
200 creating a topic branch dedicated to the prerequisite commits that can be
/linux/Documentation/tee/
H A Dop-tee.rst157 [2] http://infocenter.arm.com/help/topic/com.arm.doc.den0028a/index.html
/linux/Documentation/gpu/amdgpu/display/
H A Ddisplay-contributing.rst162 concise ToDos. If you are interested in this topic, we recommend checking some
/linux/Documentation/trace/
H A Dstm.rst143 * [2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0444b/index.html
/linux/tools/memory-model/Documentation/
H A Dlocking.txt223 please read up on that topic in litmus-tests.txt.
/linux/tools/perf/util/
H A Dhwmon_pmu.c522 .topic = "hwmon", in hwmon_pmu__for_each_event()
/linux/Documentation/gpu/
H A Ddrm-kms-helpers.rst389 But it nicely fits into the overall topic of mode setting helper
/linux/tools/power/pm-graph/
H A DREADME11 …Home Page: https://www.intel.com/content/www/us/en/developer/topic-technology/open/pm-graph/overvi…
21 https://www.intel.com/content/www/us/en/developer/topic-technology/open/pm-graph/features.html
/linux/Documentation/core-api/
H A Dunaligned-memory-access.rst114 On a related topic, with the above considerations in mind you may observe
/linux/Documentation/translations/sp_SP/process/
H A Dmaintainer-kvm-x86.rst184 El formato de prefijo más recomendable es ``KVM: <topic>:``, donde
185 ``<topic>`` es uno de los siguientes::

12