chicago.c revision 986fd29a0dc13f7608ef7f508f6e700bd7bc2720
1N/A * The contents of this file are subject to the terms of the 1N/A * Common Development and Distribution License (the "License"). 1N/A * You may not use this file except in compliance with the License. 1N/A * See the License for the specific language governing permissions 1N/A * and limitations under the License. 1N/A * When distributing Covered Code, include this CDDL HEADER in each 1N/A * If applicable, add the following below this CDDL HEADER, with the 1N/A * fields enclosed by brackets "[]" replaced with your own identifying 1N/A * information: Portions Copyright [yyyy] [name of copyright owner] 1N/A * Copyright 2007 Sun Microsystems, Inc. All rights reserved. 1N/A * Use is subject to license terms. 1N/A#
pragma ident "%Z%%M% %I% %E% SMI" 1N/A * External variables 1N/A * We need to set tod_module_name explicitly because there is a 1N/A * well known South bridge RTC node on chicago and tod_module_name 1N/A /* Work-around for Chicago platform */ 1N/A * Definitions for accessing the pci config space of the isa node 1N/A * Install power driver which handles the power button. 1N/A * It is OK to return error because 'us' driver is not available 1N/A * in all clusters (e.g. missing in Core cluster). 1N/A * mc-us3i must stay loaded for plat_get_mem_unum() 1N/A * Figure out which mi2cv dip is shared with OBP for the nvram 1N/A * device, so the lock can be acquired. 1N/A return (
ENOTSUP);
/* not supported on this platform */ 1N/A return (
ENOTSUP);
/* not supported on this platform */ 1N/A * Fiesta support for lgroups. 1N/A * On fiesta platform, an lgroup platform handle == CPU id 1N/A * Macro for extracting the CPU number from the CPU id 1N/A * Return the platform handle for the lgroup containing the given CPU 1N/A * Platform specific lgroup initialization * Count the number of CPUs installed to determine if * NUMA optimization should be enabled or not. * All CPU nodes reside in the root node and have a * Set tuneables for fiesta architecture * lgrp_expand_proc_thresh is the minimum load on the lgroups * this process is currently running on before considering * expanding threads to another lgroup. * lgrp_expand_proc_diff determines how much less the remote lgroup * must be loaded before expanding to it. * Optimize for memory bandwidth by spreading multi-threaded * program to different lgroups. * Return latency between "from" and "to" lgroups * This latency number can only be used for relative comparison * between lgroups on the running system, cannot be used across platforms, * and may not reflect the actual latency. It is platform and implementation * specific, so platform gets to decide its value. It would be nice if the * number was at least proportional to make comparisons more meaningful though. * NOTE: The numbers below are supposed to be load latencies for uncached * Return remote latency when there are more than two lgroups * (root and child) and getting latency between two different * lgroups or root is involved * Assign memnode to lgroups * Chicago memory controller portid == global CPU id * Common locking enter code * Common locking exit code * Work-around for the Chicago platform. * There are two RTCs in the Chicago platform, one on the Southbridge * returns address of the first rtc it sees. In this case, it's the SB RTC. * get_ebus_rtc_vaddr() looks for the EBUS RTC and setup the right address. * If there is no EBUS RTC node or the RTC node does not have the valid * address property, get_ebus_rtc_vaddr() will fail. /* Make sure the ebus RTC address property is valid */ " expected = %lu found =%d\n",
sizeof (
eaddr),
size);
* Does this rtc have watchdog support?