Home
last modified time | relevance | path

Searched refs:problem (Results 1 – 25 of 387) sorted by relevance

12345678910>>...16

/Linux-v4.19/arch/powerpc/platforms/cell/spufs/
Dhw_ops.c40 struct spu_problem __iomem *prob = spu->problem; in spu_hw_mbox_read()
56 return in_be32(&ctx->spu->problem->mb_stat_R); in spu_hw_mbox_stat_read()
66 stat = in_be32(&spu->problem->mb_stat_R); in spu_hw_mbox_stat_poll()
98 struct spu_problem __iomem *prob = spu->problem; in spu_hw_ibox_read()
119 struct spu_problem __iomem *prob = spu->problem; in spu_hw_wbox_write()
139 out_be32(&ctx->spu->problem->signal_notify1, data); in spu_hw_signal1_write()
144 out_be32(&ctx->spu->problem->signal_notify2, data); in spu_hw_signal2_write()
191 return in_be32(&ctx->spu->problem->spu_npc_RW); in spu_hw_npc_read()
196 out_be32(&ctx->spu->problem->spu_npc_RW, val); in spu_hw_npc_write()
201 return in_be32(&ctx->spu->problem->spu_status_R); in spu_hw_status_read()
[all …]
Dswitch.c97 struct spu_problem __iomem *prob = spu->problem; in check_spu_isolate()
217 struct spu_problem __iomem *prob = spu->problem; in save_spu_runcntl()
236 struct spu_problem __iomem *prob = spu->problem; in save_spu_status()
310 struct spu_problem __iomem *prob = spu->problem; in do_mfc_mssync()
382 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querymask()
393 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querytype()
404 struct spu_problem __iomem *prob = spu->problem; in save_ppu_tagstatus()
517 struct spu_problem __iomem *prob = spu->problem; in save_spu_npc()
601 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb_stat()
611 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb()
[all …]
/Linux-v4.19/Documentation/translations/zh_CN/
DSecurityBugs4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
DIRQ.txt4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
Dstable_kernel_rules.txt4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
Dstable_api_nonsense.txt4 original document maintainer directly. However, if you have problem
7 is problem with translation.
Dbasic_profiling.txt4 However, if you have problem communicating in English you can also ask the
6 translation is outdated or there is problem with translation.
Dio_ordering.txt4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
Dsparse.txt4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
Dvolatile-considered-harmful.txt4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
Demail-clients.txt4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
/Linux-v4.19/Documentation/process/
D3.Early-stage.rst13 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 …]
/Linux-v4.19/Documentation/networking/
Dvortex.txt198 decision. If you think that Tx checksums are causing a problem, you
217 "Variables to work-around the Compaq PCI BIOS32 problem"....
320 On a side note, adding HAS_NWAY seems to share a problem with the
335 If autonegotiation is a problem, you may need to specify "speed
345 Maintainers find that accurate and complete problem reports are
348 the bottom of the problem.
350 If you believe you have a driver problem here are some of the
353 - Is it really a driver problem?
359 - OK, it's a driver problem.
366 problem. If it's a kernel crash then you should refer to the
[all …]
Dskfp.txt90 is not there, then you may have a hardware problem or PCI
95 Some COMPAQ machines have a problem with PCI under
104 forwarding or there is a problem with the routing table
108 If your problem is not listed here, please contact our
217 document for details about this problem.
/Linux-v4.19/Documentation/translations/zh_CN/arm64/
Dtagged-pointers.txt4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
Dlegacy_instructions.txt4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
Dmemory.txt4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
Dsilicon-errata.txt4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
/Linux-v4.19/arch/powerpc/platforms/cell/
Dspu_manage.c75 iounmap(spu->problem); in spu_unmap()
158 spu->problem = spu_map_prop_old(spu, node, "problem"); in spu_map_device_old()
159 if (!spu->problem) in spu_map_device_old()
250 ret = spu_map_resource(spu, 1, (void __iomem**)&spu->problem, in spu_map_device()
275 spu->problem_phys, spu->problem); in spu_map_device()
357 spu->local_store, spu->problem, spu->priv1, in of_create_spu()
/Linux-v4.19/arch/powerpc/platforms/ps3/
Dspu.c136 unsigned long problem, unsigned long ls, unsigned long shadow, in _dump_areas() argument
141 pr_debug("%s:%d: problem: %lxh\n", func, line, problem); in _dump_areas()
190 iounmap(spu->problem); in spu_unmap()
227 spu->problem = ioremap(spu->problem_phys, in setup_areas()
230 if (!spu->problem) { in setup_areas()
247 (unsigned long)spu->problem, (unsigned long)spu->local_store, in setup_areas()
/Linux-v4.19/Documentation/core-api/
Ddebug-objects.rst78 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-v4.19/Documentation/kbuild/
DKconfig.recursion-issue-0129 # 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-v4.19/Documentation/translations/zh_CN/arm/
DBooting4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
/Linux-v4.19/Documentation/power/
Dbasic-pm-debugging.txt104 that there is a problem with the tasks freezer subsystem that should be
119 make sure to report the problem with the driver.
127 If the "platform" test fails, there is a problem with the handling of the
133 work (of course, this only may be an issue on SMP systems) and the problem
140 the problem is most probably hardware-related and serious, so it should be
145 indicates a serious problem that very well may be related to the hardware, but
153 probably is a problem with a driver statically compiled into the kernel and you
155 individually. Otherwise, there is a problem with a modular driver and you can
165 before hibernation, and please report the problem with it(them).
197 techniques to find the problem. First, if there is a serial port in your box,
/Linux-v4.19/Documentation/arm/nwfpe/
DNOTES1 There seems to be a problem with exp(double) and our emulator. I haven't
22 This code will cause this problem:

12345678910>>...16