Searched hist:182689 (Results 1 - 9 of 9) sorted by relevance
| /freebsd-10.2-release/sys/sparc64/include/ | ||
| H A D | cache.h | diff 182689 Tue Sep 02 21:14:24 MDT 2008 marius - USIII-based machines can consist of CPUs having different cache sizes (and running at different frequencies) so move the cacheinfo to the PCPU data. While at it, remove some redundant and/or unused members from struct cacheinfo. - In sparc64_init don't assume the first CPU node we find in the OFW device tree is the BSP. |
| H A D | pcpu.h | diff 182689 Tue Sep 02 21:14:24 MDT 2008 marius - USIII-based machines can consist of CPUs having different cache sizes (and running at different frequencies) so move the cacheinfo to the PCPU data. While at it, remove some redundant and/or unused members from struct cacheinfo. - In sparc64_init don't assume the first CPU node we find in the OFW device tree is the BSP. |
| /freebsd-10.2-release/sys/sparc64/sparc64/ | ||
| H A D | spitfire.c | diff 182689 Tue Sep 02 21:14:24 MDT 2008 marius - USIII-based machines can consist of CPUs having different cache sizes (and running at different frequencies) so move the cacheinfo to the PCPU data. While at it, remove some redundant and/or unused members from struct cacheinfo. - In sparc64_init don't assume the first CPU node we find in the OFW device tree is the BSP. |
| H A D | cache.c | diff 182689 Tue Sep 02 21:14:24 MDT 2008 marius - USIII-based machines can consist of CPUs having different cache sizes (and running at different frequencies) so move the cacheinfo to the PCPU data. While at it, remove some redundant and/or unused members from struct cacheinfo. - In sparc64_init don't assume the first CPU node we find in the OFW device tree is the BSP. |
| H A D | cheetah.c | diff 182689 Tue Sep 02 21:14:24 MDT 2008 marius - USIII-based machines can consist of CPUs having different cache sizes (and running at different frequencies) so move the cacheinfo to the PCPU data. While at it, remove some redundant and/or unused members from struct cacheinfo. - In sparc64_init don't assume the first CPU node we find in the OFW device tree is the BSP. |
| H A D | mp_exception.S | diff 182689 Tue Sep 02 21:14:24 MDT 2008 marius - USIII-based machines can consist of CPUs having different cache sizes (and running at different frequencies) so move the cacheinfo to the PCPU data. While at it, remove some redundant and/or unused members from struct cacheinfo. - In sparc64_init don't assume the first CPU node we find in the OFW device tree is the BSP. |
| H A D | genassym.c | diff 182689 Tue Sep 02 21:14:24 MDT 2008 marius - USIII-based machines can consist of CPUs having different cache sizes (and running at different frequencies) so move the cacheinfo to the PCPU data. While at it, remove some redundant and/or unused members from struct cacheinfo. - In sparc64_init don't assume the first CPU node we find in the OFW device tree is the BSP. |
| H A D | mp_machdep.c | diff 182689 Tue Sep 02 21:14:24 MDT 2008 marius - USIII-based machines can consist of CPUs having different cache sizes (and running at different frequencies) so move the cacheinfo to the PCPU data. While at it, remove some redundant and/or unused members from struct cacheinfo. - In sparc64_init don't assume the first CPU node we find in the OFW device tree is the BSP. |
| H A D | machdep.c | diff 182689 Tue Sep 02 21:14:24 MDT 2008 marius - USIII-based machines can consist of CPUs having different cache sizes (and running at different frequencies) so move the cacheinfo to the PCPU data. While at it, remove some redundant and/or unused members from struct cacheinfo. - In sparc64_init don't assume the first CPU node we find in the OFW device tree is the BSP. |
Completed in 192 milliseconds