startcpu(2) System Calls Manual startcpu(2)Name
startcpu - start a CPU
Syntax
startcpu(cpunumber)
int cpunumber;
Description
The system call starts the CPU specified by cpunumber. Any non-boot CPU can be started using this system call. Only a superuser can exe-
cute this system call.
Return Values
The call returns 0 if the CPU was started successfully, or else it returns -1 and sets errno appropriately.
Diagnostics
[EPERM] The caller is not a superuser
[EBUSY] The CPU is already running
[ENODEV] No CPU present by the given cpunumber
[EINVAL] Invalid value for cpunumber. A valid cpunumber is between 0 and 31.
See Alsostopcpu(2), startcpu(8), stopcpu(8)startcpu(2)
Check Out this Related Man Page
unix_master(9r)unix_master(9r)NAME
unix_master - General: Forces execution onto the master CPU
SYNOPSIS
void unix_master(
void );
ARGUMENTS
None
DESCRIPTION
The unix_master routine forces execution of the kernel thread onto the master CPU (also called the boot CPU). In other words, unix_master
binds the kernel thread to the master CPU. To release the kernel thread from the bind to the master CPU, call the unix_release routine. You
can make recursive calls to unix_master as long as you make an equal number of calls to unix_release.
The unix_master routine provides another way besides the simple and complex lock routines to make a kernel module symmetric multiprocessing
(SMP) safe. Although calling unix_master is not optimal for performance on an SMP CPU, it does provide third-party kernel module writers
with an easy way to make their modules SMP safe without using the lock routines.
NOTES
Device drivers should not directly call the unix_master and unix_release routines. One exception to this recommendation is when you want a
device driver's kernel threads to run only on the master CPU. This situation occurs when your driver creates and starts its own kernel
threads and you set the d_funnel member of the associated dsent structure to the value DEV_FUNNEL. In this case, each kernel thread must
call unix_master once to ensure that the kernel thread runs only on the master CPU. Remember to make a corresponding call to unix_release.
CAUTIONS
To avoid deadlock, do not call the unix_master routine under the following circumstances: When holding a simple lock In the driver's inter-
rupt service routine
RETURN VALUES
None
SEE ALSO
routines: unix_release(9r)unix_master(9r)
<h1>A short history of UNIX</h1>
<p>In the late 1960's Ken Thompsom joined the computing-science research group at Bell
Laboratories, which is the research arm of the giant American corporation ATT. He and many
colleagues had been collaborating with MIT and GE on the development of an... (0 Replies)
We have quite a few threads about this subject. I have collected some of them and arranged them by the OS which is primarily discussed in the thread. That is because the exact procedure depends on the OS involved. What's more, since you often need to interact with the boot process, the... (0 Replies)
I'm writing a command shell, and I want to be able to detect when the user presses an arrow key (otherwise it just prints [[A, [[B, etc.). I know it's relatively easy (although somewhat more time-consuming) to detect keystrokes in noncanonical mode, but I've noticed that the bash shell detects... (4 Replies)
I'm learning off Linux (Ubuntu) right now. I want to move up to Unix, but I don't want to rush like I did when it came to Windows --> to Linux. What is the best Unix OS that fits in pretty well with Ubuntu.
In other words is there kind of an equal Linux with Unix?
Also what do I need to... (10 Replies)
I noticed my hostname is <my-full-name>s-macbook.local. I'm not sure exactly what information leaves the local network, and whether the hostname is included, but if it is, this would mean people on the Internet can look at my hostname and see who I am. Before anyone says that's not possible,... (4 Replies)