src/sys/amd64/include/param.h, branch release/7.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2008-02-24T05:45:17+00:00

'RELENG_7_0_0_RELEASE'.

This commit was manufactured to restore the state of the 7.0-RELEASE image.

By popular demand, move __HAVE_ACPI and __PCI_REROUTE_INTERRUPT into

2006-01-09T06:05:57+00:00

param.h.  Per request, I've placed these just after the
_NO_NAMESPACE_POLLUTION ifndef.  I've not renamed anything yet, but
may since we don't need the __.

Submitted by: bde, jhb, scottl, many others.

Drop _MACHINE_ARCH and _MACHINE defines (not to be confused with

2005-12-06T13:27:21+00:00

MACHINE_ARCH and MACHINE).  Their purpose was to be able to test
in cpp(1), but cpp(1) only understands integer type expressions.
Using such unsupported expressions introduced a number of subtle
bugs, which were discovered by compiling with -Wundef.

Increase MAXCPU to 16 in SMP kernels so that APIC IDs from 0 to 15 are

2005-06-29T15:13:25+00:00

allowed for CPUs.

Tested by:	amd64 at cybernetwork dot org
Approved by:	re (scottl)
MFC after:	1 week

MFi386: whitespace, copyright header, etc updates

2005-01-21T05:56:41+00:00

Begin all license/copyright comments with /*-

2005-01-05T20:17:21+00:00

Remove UAREA_PAGES.

2004-11-20T02:29:50+00:00

Reviewed by:	arch@

Turn PREEMPTION into a kernel option. Make sure that it's defined if

2004-09-02T18:59:15+00:00

FULL_PREEMPTION is defined.  Add a runtime warning to ULE if PREEMPTION is
enabled (code inspired by the PREEMPTION warning in kern_switch.c).  This
is a possible MT5 candidate.

Turn off PREEMPTION by default while it gets debugged. It's been causing

2004-08-01T14:31:45+00:00

4 weeks of problems including deadlocks and instant panics.  Note that the
real bugs are likely in the scheduler.

Implement preemption of kernel threads natively in the scheduler rather

2004-07-02T20:21:44+00:00

than as one-off hacks in various other parts of the kernel:
- Add a function maybe_preempt() that is called from sched_add() to
  determine if a thread about to be added to a run queue should be
  preempted to directly.  If it is not safe to preempt or if the new
  thread does not have a high enough priority, then the function returns
  false and sched_add() adds the thread to the run queue.  If the thread
  should be preempted to but the current thread is in a nested critical
  section, then the flag TDF_OWEPREEMPT is set and the thread is added
  to the run queue.  Otherwise, mi_switch() is called immediately and the
  thread is never added to the run queue since it is switch to directly.
  When exiting an outermost critical section, if TDF_OWEPREEMPT is set,
  then clear it and call mi_switch() to perform the deferred preemption.
- Remove explicit preemption from ithread_schedule() as calling
  setrunqueue() now does all the correct work.  This also removes the
  do_switch argument from ithread_schedule().
- Do not use the manual preemption code in mtx_unlock if the architecture
  supports native preemption.
- Don't call mi_switch() in a loop during shutdown to give ithreads a
  chance to run if the architecture supports native preemption since
  the ithreads will just preempt DELAY().
- Don't call mi_switch() from the page zeroing idle thread for
  architectures that support native preemption as it is unnecessary.
- Native preemption is enabled on the same archs that supported ithread
  preemption, namely alpha, i386, and amd64.

This change should largely be a NOP for the default case as committed
except that we will do fewer context switches in a few cases and will
avoid the run queues completely when preempting.

Approved by:	scottl (with his re@ hat)