| /linux-6.6.21/arch/powerpc/platforms/cell/spufs/ |
| D | hw_ops.c | 27 struct spu_problem __iomem *prob = spu->problem; in spu_hw_mbox_read()
43 return in_be32(&ctx->spu->problem->mb_stat_R); in spu_hw_mbox_stat_read()
53 stat = in_be32(&spu->problem->mb_stat_R); in spu_hw_mbox_stat_poll()
85 struct spu_problem __iomem *prob = spu->problem; in spu_hw_ibox_read()
106 struct spu_problem __iomem *prob = spu->problem; in spu_hw_wbox_write()
126 out_be32(&ctx->spu->problem->signal_notify1, data); in spu_hw_signal1_write()
131 out_be32(&ctx->spu->problem->signal_notify2, data); in spu_hw_signal2_write()
178 return in_be32(&ctx->spu->problem->spu_npc_RW); in spu_hw_npc_read()
183 out_be32(&ctx->spu->problem->spu_npc_RW, val); in spu_hw_npc_write()
188 return in_be32(&ctx->spu->problem->spu_status_R); in spu_hw_status_read()
[all …]
|
| D | switch.c | 83 struct spu_problem __iomem *prob = spu->problem; in check_spu_isolate()
203 struct spu_problem __iomem *prob = spu->problem; in save_spu_runcntl()
222 struct spu_problem __iomem *prob = spu->problem; in save_spu_status()
296 struct spu_problem __iomem *prob = spu->problem; in do_mfc_mssync()
368 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querymask()
379 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querytype()
390 struct spu_problem __iomem *prob = spu->problem; in save_ppu_tagstatus()
503 struct spu_problem __iomem *prob = spu->problem; in save_spu_npc()
587 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb_stat()
597 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb()
[all …]
|
| /linux-6.6.21/fs/afs/ |
| D | addr_list.c | 72 const char *problem; in afs_parse_text_addrs() local
90 problem = "nul"; in afs_parse_text_addrs()
99 problem = "brace1"; in afs_parse_text_addrs()
104 problem = "brace2"; in afs_parse_text_addrs()
160 problem = "family"; in afs_parse_text_addrs()
166 problem = "nostop"; in afs_parse_text_addrs()
179 problem = "port"; in afs_parse_text_addrs()
186 problem = "pval"; in afs_parse_text_addrs()
194 problem = "weird"; in afs_parse_text_addrs()
212 problem, p - text, (int)len, (int)len, text); in afs_parse_text_addrs()
[all …]
|
| /linux-6.6.21/Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 13 sysadmin, start recovery) when a file system problem is detected.
16 for a monitoring tool to know a problem in the file system has happened.
20 early file system problem detection and reporting recovery tools.
25 problem. For this reason, FAN_FS_ERROR tries to report only the first
53 agnostic tool to learn about a problem in the file system, without
54 providing any additional details about the problem. This record is
|
| /linux-6.6.21/arch/powerpc/platforms/cell/ |
| D | spu_manage.c | 65 iounmap(spu->problem); in spu_unmap()
148 spu->problem = spu_map_prop_old(spu, node, "problem"); in spu_map_device_old()
149 if (!spu->problem) in spu_map_device_old()
227 ret = spu_map_resource(spu, 1, (void __iomem**)&spu->problem, in spu_map_device()
252 spu->problem_phys, spu->problem); in spu_map_device()
334 spu->local_store, spu->problem, spu->priv1, in of_create_spu()
|
| /linux-6.6.21/Documentation/process/ |
| D | 3.Early-stage.rst | 13 Specifying the problem
17 clear description of the problem to be solved. In some cases, this step is
19 example. In others, though, it is tempting to confuse the real problem
31 immediate problem. To the wider kernel community, though, it was seen as a
53 the right solution to the problem than they were with a specific module.
54 The moral of the story is to focus on the problem - not a specific solution
61 - What, exactly, is the problem which needs to be solved?
63 - Who are the users affected by this problem? Which use cases should the
66 - How does the kernel fall short in addressing that problem now?
78 - It may well be that the problem is addressed by the kernel in ways which
[all …]
|
| D | researcher-guidelines.rst | 107 * What is the specific problem that has been found?
108 * How could the problem be reached on a running system?
109 * What effect would encountering the problem have on the system?
110 * How was the problem found? Specifically include details about any
113 * Which version of Linux was the problem found on? Using the most recent
116 * What was changed to fix the problem, and why it is believed to be correct?
|
| /linux-6.6.21/Documentation/networking/device_drivers/ethernet/3com/ |
| D | vortex.rst | 209 decision. If you think that Tx checksums are causing a problem, you
228 "Variables to work-around the Compaq PCI BIOS32 problem"....
331 On a side note, adding HAS_NWAY seems to share a problem with the
346 If autonegotiation is a problem, you may need to specify "speed
356 Maintainers find that accurate and complete problem reports are
359 the bottom of the problem.
361 If you believe you have a driver problem here are some of the
364 - Is it really a driver problem?
370 - OK, it's a driver problem.
377 problem. If it's a kernel crash then you should refer to
[all …]
|
| /linux-6.6.21/arch/powerpc/platforms/ps3/ |
| D | spu.c | 124 unsigned long problem, unsigned long ls, unsigned long shadow, in _dump_areas() argument
129 pr_debug("%s:%d: problem: %lxh\n", func, line, problem); in _dump_areas()
178 iounmap(spu->problem); in spu_unmap()
210 spu->problem = ioremap(spu->problem_phys, in setup_areas()
213 if (!spu->problem) { in setup_areas()
230 (unsigned long)spu->problem, (unsigned long)spu->local_store, in setup_areas()
|
| /linux-6.6.21/Documentation/translations/zh_TW/ |
| D | IRQ.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | io_ordering.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /linux-6.6.21/Documentation/translations/zh_CN/arch/arm64/ |
| D | tagged-pointers.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | legacy_instructions.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | memory.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | silicon-errata.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /linux-6.6.21/Documentation/core-api/ |
| D | debug-objects.rst | 78 problem before the real initialization of the object happens. E.g. it
101 problem before the real initialization of the object happens. E.g. it
125 problem before the real activation of the object happens. E.g. it can
164 provided by the caller. The fixup function can correct the problem
180 fixup function can correct the problem before the real free of the
196 fixup function can correct the problem by calling debug_object_init
213 This function is called from the debug code whenever a problem in
231 This function is called from the debug code whenever a problem in
259 This function is called from the debug code whenever a problem in
272 This function is called from the debug code whenever a problem in
[all …]
|
| /linux-6.6.21/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 29 # But that is a problem, because this means that in order to determine
37 # obvious that an easy to solution to this problem should just be the removal
43 # CORE also consist of a solution to this recursive problem.
|
| /linux-6.6.21/Documentation/translations/zh_TW/arch/arm64/ |
| D | tagged-pointers.txt | 6 original document maintainer directly. However, if you have a problem
9 or if there is a problem with the translation.
|
| D | legacy_instructions.txt | 6 original document maintainer directly. However, if you have a problem
9 or if there is a problem with the translation.
|
| D | memory.txt | 6 original document maintainer directly. However, if you have a problem
9 or if there is a problem with the translation.
|
| D | silicon-errata.txt | 6 original document maintainer directly. However, if you have a problem
9 or if there is a problem with the translation.
|
| /linux-6.6.21/Documentation/networking/device_drivers/fddi/ |
| D | skfp.rst | 102 is not there, then you may have a hardware problem or PCI
110 Some COMPAQ machines have a problem with PCI under
122 forwarding or there is a problem with the routing table
126 If your problem is not listed here, please contact our
252 document for details about this problem.
|
| /linux-6.6.21/Documentation/translations/zh_TW/dev-tools/ |
| D | sparse.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /linux-6.6.21/Documentation/power/ |
| D | basic-pm-debugging.rst | 112 that there is a problem with the tasks freezer subsystem that should be
128 make sure to report the problem with the driver.
136 If the "platform" test fails, there is a problem with the handling of the
142 work (of course, this only may be an issue on SMP systems) and the problem
149 the problem is most probably hardware-related and serious, so it should be
154 indicates a serious problem that very well may be related to the hardware, but
163 probably is a problem with a driver statically compiled into the kernel and you
165 individually. Otherwise, there is a problem with a modular driver and you can
175 before hibernation, and please report the problem with it(them).
209 techniques to find the problem. First, if there is a serial port in your box,
|
| /linux-6.6.21/Documentation/translations/zh_CN/arch/arm/ |
| D | Booting | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|