Searched refs:why (Results 1 – 7 of 7) sorted by relevance
| /xnu-11417.140.69/tests/ |
| H A D | user_msrs.c | 47 typedef void (*msr_op)(enum msr_op_reason why, void *param);
61 …msr_test_S ## _op0 ## _ ## _op1 ## _C ## _n ## _C ## _m ## _ ## _op2 (enum msr_op_reason why, void…
63 …switch (why) { …
|
| /xnu-11417.140.69/bsd/netinet/ |
| H A D | in_arp.c | 468 const char *why = NULL; in arp_llreach_reachable() local
509 why = "has alias(es) and hasn't been used in a while"; in arp_llreach_reachable()
511 why = "haven't heard from it in a while"; in arp_llreach_reachable()
521 &SIN(rt_key(la->la_rt))->sin_addr, tmp, sizeof(tmp)), why, in arp_llreach_reachable()
546 const char *why = NULL, *type = ""; in arp_llreach_alloc() local
564 why = " for different target HW address; " in arp_llreach_alloc()
579 why = " for same target HW address; " in arp_llreach_alloc()
590 if (why == NULL) { in arp_llreach_alloc()
591 why = "creating new llreach record"; in arp_llreach_alloc()
597 if (arp_verbose > 1 && lr != NULL && why != NULL) { in arp_llreach_alloc()
[all …]
|
| /xnu-11417.140.69/bsd/netinet6/ |
| H A D | nd6_nbr.c | 193 const char *why = NULL, *type = ""; in nd6_llreach_alloc() local
212 why = " for different target HW address; " in nd6_llreach_alloc()
218 why = " for same target HW address; " in nd6_llreach_alloc()
229 if (why == NULL) { in nd6_llreach_alloc()
230 why = "creating new llreach record"; in nd6_llreach_alloc()
235 if (nd6_debug && lr != NULL && why != NULL) { in nd6_llreach_alloc()
239 type, why, inet_ntop(AF_INET6, in nd6_llreach_alloc()
|
| /xnu-11417.140.69/osfmk/i386/ |
| H A D | mp.c | 1083 NMIPI_panic(cpumask_t cpu_mask, NMI_reason_t why) in NMIPI_panic() argument
1090 NMI_panic_reason = why; in NMIPI_panic()
|
| /xnu-11417.140.69/doc/vm/ |
| H A D | memorystatus.md | 67 Notice that the memorystatus thread does not explicitly check why it was woken up.
|
| /xnu-11417.140.69/tools/lldbmacros/ |
| H A D | README.md | 200 why your changes are not reflected in the command.
|
| /xnu-11417.140.69/doc/scheduler/ |
| H A D | sched_clutch_edge.md | 170 …th workload threads to a single cluster as much as possible. A few reasons why this property is es…
|