aboutsummaryrefslogtreecommitdiff
path: root/sys/conf/options.i386
Commit message (Collapse)AuthorAgeFilesLines
* Remove SVR4 (System V Release 4) binary compatibility support.Gleb Smirnoff2017-02-281-2/+0
| | | | | | | | UNIX System V Release 4 is operating system released in 1988. It ceased to exist in early 2000-s. Notes: svn path=/head/; revision=314373
* For i386, remove config options CPU_DISABLE_CMPXCHG, CPU_DISABLE_SSEKonstantin Belousov2017-02-031-3/+0
| | | | | | | | | | | | | | | | | | | | and device npx. This means that FPU is always initialized and handled when available, and SSE+ register file and exception are handled when available. This makes the kernel FPU code much easier to maintain by the cost of slight bloat for CPUs older than 25 years. CPU_DISABLE_CMPXCHG outlived its usefulness, see the removed comment explaining the original purpose. Suggested by and discussed with: bde Tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 3 weeks Notes: svn path=/head/; revision=313154
* hyperv: Deprecate HYPERV option by moving Hyper-V IDT vector into vmbusSepherosa Ziehau2016-04-151-2/+0
| | | | | | | | | | Submitted by: Jun Su <junsu microsoft com> Reviewed by: jhb, kib, sephe Sponsored by: Microsoft OSTC Differential Revision: https://reviews.freebsd.org/D5910 Notes: svn path=/head/; revision=298022
* Remove support for Xen PV domU kernels. Support for HVM domU kernelsJohn Baldwin2015-04-301-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | remains. Xen is planning to phase out support for PV upstream since it is harder to maintain and has more overhead. Modern x86 CPUs include virtualization extensions that support HVM guests instead of PV guests. In addition, the PV code was i386 only and not as well maintained recently as the HVM code. - Remove the i386-only NATIVE option that was used to disable certain components for PV kernels. These components are now standard as they are on amd64. - Remove !XENHVM bits from PV drivers. - Remove various shims required for XEN (e.g. PT_UPDATES_FLUSH, LOAD_CR3, etc.) - Remove duplicate copy of <xen/features.h>. - Remove unused, i386-only xenstored.h. Differential Revision: https://reviews.freebsd.org/D2362 Reviewed by: royger Tested by: royger (i386/amd64 HVM domU and amd64 PVH dom0) Relnotes: yes Notes: svn path=/head/; revision=282274
* Microsoft vmbus, storage and other related driver enhancements for HyperV.Wei Hu2015-04-291-0/+2
| | | | | | | | | | | | | | | | | | | | | | | - Vmbus multi channel support. - Vector interrupt support. - Signal optimization. - Storvsc driver performance improvement. - Scatter and gather support for storvsc driver. - Minor bug fix for KVP driver. Thanks royger, jhb and delphij from FreeBSD community for the reviews and comments. Also thanks Hovy Xu from NetApp for the contributions to the storvsc driver. PR: 195238 Submitted by: whu Reviewed by: royger, jhb, delphij Approved by: royger MFC after: 2 weeks Relnotes: yes Sponsored by: Microsoft OSTC Notes: svn path=/head/; revision=282212
* Add config option PAE_TABLES for the i386 kernel. It switches pmap toKonstantin Belousov2015-04-131-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | use PAE format for the page tables, but does not incur other consequences of the full PAE config. In particular, vm_paddr_t and bus_addr_t are left 32bit, and max supported memory is still limited by 4GB. The option allows to have nx permissions for memory mappings on i386 kernel, while keeping the usual i386 KBI and avoiding the kernel data sizing problems typical for the PAE config. Intel documented that the PAE format for page tables is available starting with the Pentium Pro, but it is possible that the plain Pentium CPUs have the required support (Appendix H). The goal is to enable the option and non-exec mappings on i386 for the GENERIC kernel. Anybody wanting a useful system on 486, have to reconfigure the modern i386 kernel anyway. Discussed with: alc, jhb Sponsored by: The FreeBSD Foundation MFC after: 2 weeks Notes: svn path=/head/; revision=281495
* Garbage collect the asr driver. Hardware for it has not been produced inScott Long2015-01-021-1/+0
| | | | | | | | | | | | roughly 10 years, and the driver has not enjoyed any significant maintenance since long before that. Despite well-meaning efforts from a number of people, myself included, it never made the jump to 64-bit and was relegated to the back-corners of i386. Now its frailty is hampering forward progress with Clang. Any renewed engineering efforts are of course welcome and can happen outside of the tree. No MFC of this is planned. Notes: svn path=/head/; revision=276526
* imagact_binmisc builds for all supported architectures, so enable it for all.Justin Hibbits2014-05-221-1/+0
| | | | | | | | | | Any bugs in execution will be dealt with as they crop up. MFC after: 3 weeks Relnotes: Yes Notes: svn path=/head/; revision=266531
* Actually, since this is what I thought I was doing, only allow theSean Bruno2014-04-081-0/+1
| | | | | | | | | | | | | binmisc code to be build on amd64/i386 for the kernel. Update NOTES with some indication of what this code is used for. Pointed out by jhb@ ... thanks! Submitted by: jhb@ Notes: svn path=/head/; revision=264280
* The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.David E. O'Brien2013-08-211-4/+0
| | | | | | | | | | | | Thus "device padlock_rng" and "device rdrand_rng" should be used instead of "options PADLOCK_RNG" & "options RDRAND_RNG". Requested by: so@ (des) Submitted by: obrien, arthurmesh@gmail.com Obtained from: Juniper Networks Notes: svn path=/head/; revision=254624
* Rename the IVY_RNG option to RDRAND_RNG.Konstantin Belousov2012-09-131-1/+1
| | | | | | | | Based on submission by: Arthur Mesh <arthurmesh@gmail.com> MFC after: 2 weeks Notes: svn path=/head/; revision=240455
* Add support for new Intel on-CPU Bull Mountain random numberKonstantin Belousov2012-09-051-0/+4
| | | | | | | | | | | | | | | | | | | | | | generator, found on IvyBridge and supposedly later CPUs, accessible with RDRAND instruction. From the Intel whitepapers and articles about Bull Mountain, it seems that we do not need to perform post-processing of RDRAND results, like AES-encryption of the data with random IV and keys, which was done for Padlock. Intel claims that sanitization is performed in hardware. Make both Padlock and Bull Mountain random generators support code covered by kernel config options, for the benefit of people who prefer minimal kernels. Also add the tunables to disable hardware generator even if detected. Reviewed by: markm, secteam (simon) Tested by: bapt, Michael Moll <kvedulv@kvedulv.de> MFC after: 3 weeks Notes: svn path=/head/; revision=240135
* Disable detailed PV entry accounting by default. Add a config optionAlan Cox2012-03-241-0/+1
| | | | | | | | | to enable it. MFC after: 1 week Notes: svn path=/head/; revision=233433
* Add isci(4) driver for amd64 and i386 targets.Jim Harris2012-01-311-0/+3
| | | | | | | | | | | | | | | | | | | | | | The isci driver is for the integrated SAS controller in the Intel C600 (Patsburg) chipset. Source files in sys/dev/isci directory are FreeBSD-specific, and sys/dev/isci/scil subdirectory contains an OS-agnostic library (SCIL) published by Intel to control the SAS controller. This library is used primarily as-is in this driver, with some post-processing to better integrate into the kernel build environment. isci.4 and a README in the sys/dev/isci directory contain a few additional details. This driver is only built for amd64 and i386 targets. Sponsored by: Intel Reviewed by: scottl Approved by: scottl Notes: svn path=/head/; revision=230843
* Make "options XENHVM" compile for i386, not just amd64 -- a largelyRobert Watson2011-01-041-0/+1
| | | | | | | | | | | | mechanical change. This opens the door for using PV device drivers under Xen HVM on i386, as well as more general harmonisation of i386 and amd64 Xen support in FreeBSD. Reviewed by: cperciva MFC after: 3 weeks Notes: svn path=/head/; revision=216956
* Make NKPT a kernel option on i386 so that it can be set to a non-defaultJohn Baldwin2010-03-101-0/+1
| | | | | | | | | | value from kernel config files. Tested by: Charles Sprickman spork of bway net MFC after: 2 weeks Notes: svn path=/head/; revision=204972
* Handling all the three clocks (hardclock, softclock, profclock) with theAttilio Rao2010-01-151-0/+1
| | | | | | | | | | | | | | | | | | | | | LAPIC may lead to aliasing for softclock and profclock because frequencies are sized in order to fit mainly hardclock. atrtc used to take care of the softclock and profclock and it does still do, if the LAPIC can't handle the clocks properly. Revert the change when the LAPIC started taking charge of all three of them and let atrtc handle softclock and profclock if not explicitly requested. Such request can be made setting != 0 the new tunable machdep.lapic_allclocks or if the new device ATPIC is not present within the i386 kernel config (atrtc is linked to atpic presence). Diagnosed by: Sandvine Incorporated Reviewed by: jhb, emaste Sponsored by: Sandvine Incorporated MFC: 3 weeks Notes: svn path=/head/; revision=202387
* * Completely Remove the option STOP_NMI from the kernel. This optionAttilio Rao2009-08-131-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | has proven to have a good effect when entering KDB by using a NMI, but it completely violates all the good rules about interrupts disabled while holding a spinlock in other occasions. This can be the cause of deadlocks on events where a normal IPI_STOP is expected. * Adds an new IPI called IPI_STOP_HARD on all the supported architectures. This IPI is responsible for sending a stop message among CPUs using a privileged channel when disponible. In other cases it just does match a normal IPI_STOP. Right now the IPI_STOP_HARD functionality uses a NMI on ia32 and amd64 architectures, while on the other has a normal IPI_STOP effect. It is responsibility of maintainers to eventually implement an hard stop when necessary and possible. * Use the new IPI facility in order to implement a new userend SMP kernel function called stop_cpus_hard(). That is specular to stop_cpu() but it does use the privileged channel for the stopping facility. * Let KDB use the newly introduced function stop_cpus_hard() and leave stop_cpus() for all the other cases * Disable interrupts on CPU0 when starting the process of APs suspension. * Style cleanup and comments adding This patch should fix the reboot/shutdown deadlocks many users are constantly reporting on mailing lists. Please don't forget to update your config file with the STOP_NMI option removal Reviewed by: jhb Tested by: pho, bz, rink Approved by: re (kib) Notes: svn path=/head/; revision=196196
* Fix AGP debugging code:Wojciech A. Koszek2009-02-061-0/+3
| | | | | | | | | | | | | | | - correct format strings - fill opt_agp.h if AGP_DEBUG is defined - bring AGP_DEBUG to LINT by mentioning it in NOTES This should hopefully fix a warning that was... Found by: Coverity Prevent(tm) CID: 3676 Tested on: amd64, i386 Notes: svn path=/head/; revision=188247
* Integrate configuration bits for compling xen.Kip Macy2008-08-151-0/+3
| | | | | | | MFC after: 1 month Notes: svn path=/head/; revision=181776
* Remove obselete PECOFF image activator support.Wojciech A. Koszek2008-06-141-2/+0
| | | | | | | | | | | PRs assigned at the time of removal: kern/80742 Discussed on: freebsd-current (silence), IRC Tested by: make universe Approved by: cognet (mentor) Notes: svn path=/head/; revision=179785
* Remove ISDN4BSD (I4B) from HEAD as it is not MPSAFE andBjoern A. Zeeb2008-05-261-36/+0
| | | | | | | | | | | | | | | | | | | | | parts relied on the now removed NET_NEEDS_GIANT. Most of I4B has been disconnected from the build since July 2007 in HEAD/RELENG_7. This is what was removed: - configuration in /etc/isdn - examples - man pages - kernel configuration - sys/i4b (drivers, layers, include files) - user space tools - i4b support from ppp - further documentation Discussed with: rwatson, re Notes: svn path=/head/; revision=179315
* Back in the good old days, PC's had random pieces of rock forPoul-Henning Kamp2008-03-261-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | frequency generation and what frequency the generated was anyones guess. In general the 32.768kHz RTC clock x-tal was the best, because that was a regular wrist-watch Xtal, whereas the X-tal generating the ISA bus frequency was much lower quality, often costing as much as several cents a piece, so it made good sense to check the ISA bus frequency against the RTC clock. The other relevant property of those machines, is that they typically had no more than 16MB RAM. These days, CPU chips croak if their clocks are not tightly within specs and all necessary frequencies are derived from the master crystal by means if PLL's. Considering that it takes on average 1.5 second to calibrate the frequency of the i8254 counter, that more likely than not, we will not actually use the result of the calibration, and as the final clincher, we seldom use the i8254 for anything besides BEL in syscons anyway, it has become time to drop the calibration code. If you need to tell the system what frequency your i8254 runs, you can do so from the loader using hw.i8254.freq or using the sysctl kern.timecounter.tc.i8254.frequency. Notes: svn path=/head/; revision=177651
* Allow the sio acpi attachment to be disabled (ie: use hints only). ThisPeter Wemm2007-11-301-0/+1
| | | | | | | | | | | | | hack means you can get the units and flags to match up more easily with serial consoles on machines with acpi tables that cause the com ports to be probed in the wrong order (and hence get the wrong sio unit number). This replaces the common alternative hack of editing the code to comment out the acpi attachment. This could go away entirely when device wiring patches are committed. Notes: svn path=/head/; revision=174116
* Temporary disconnect i4bing, i4bisppp and i4bipr from the build forBjoern A. Zeeb2007-07-041-2/+2
| | | | | | | | | | | | | the 7.0 timeframe. This is needed because I4B is not locked and NET_NEEDS_GIANT goes away. The plan is to lock I4B and bring everything back for 7.1. Approved by: re (kensmith) Notes: svn path=/head/; revision=171196
* Remove sio(4) and related options from MI files to amd64, i386Marcel Moolenaar2006-07-291-0/+6
| | | | | | | | | | | | and pc98 MD files. Remove nodevice and nooption lines specific to sio(4) from ia64, powerpc and sparc64 NOTES. There were no such lines for arm yet. sio(4) is usable on less than half the platforms, not counting a future mips platform. Its presence in MI files is therefore increasingly becoming a burden. Notes: svn path=/head/; revision=160813
* Send the pcvt(4) driver off to retirement.Poul-Henning Kamp2006-05-171-24/+0
| | | | Notes: svn path=/head/; revision=158687
* Fix LINSYSFS in the platform options files that I missed from the platformDoug Ambrisko2006-05-101-0/+1
| | | | | | | split out change. Notes: svn path=/head/; revision=158384
* - change the example of compiling only specific modules to not containAlexander Leidinger2006-05-071-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | the linux module, since it is not cross-platform - move linprocfs from "files" and "options" to architecture specific files, since it only makes sense to build this for those architectures, where we also have a linuxolator - disable the build of the linuxolator on our tier-2 architecture "Alpha": * we don't have a linux_base port which supports Alpha and at the same time is not outdated/obsoleted upstream/in a good condition/ currently working * the upcomming new default linux base port is based upon Fedora Core 3 (security support via http://www.fedoralegacy.org), which isn't available for Alpha (like the current default linux base port which is based upon Red Hat 8) * nobody answered my request for testing it ~1 month ago on current@ and alpha@ (it doesn't surprises me, see above) * a SoC student wouldn't have to waste time on something which nobody is willing to test This does not remove the alpha specific MD files of the linuxolator yet. Discussed on: arch (mostly silence) Spiritual support by: scottl Notes: svn path=/head/; revision=158349
* o Move ISA specific code from ppc.c to ppc_isa.c -- a bus front-Marcel Moolenaar2006-04-241-2/+0
| | | | | | | | | | | | | | | | | end for isa(4). o Add a seperate bus frontend for acpi(4) and allow ISA DMA for it when ISA is configured in the kernel. This allows acpi(4) attachments in non-ISA configurations, as is possible for ia64. o Add a seperate bus frontend for pci(4) and detect known single port parallel cards. o Merge PC98 specific changes under pc98/cbus into the MI driver. The changes are minor enough for conditional compilation and in this form invites better abstraction. o Have ppc(4) usabled on all platforms, now that ISA specifics are untangled enough. Notes: svn path=/head/; revision=158005
* Move XBOX option to options. While it is only valid on i386,Warner Losh2006-03-031-3/+0
| | | | | | | syscons_isa is shared with other machines. Notes: svn path=/head/; revision=156247
* Remove all redundant option file names that don't hurt readability.Ruslan Ermilov2005-12-121-2/+2
| | | | Notes: svn path=/head/; revision=153335
* Add experimental BPF Just-In-Time compiler for amd64 and i386.Jung-uk Kim2005-12-061-0/+3
| | | | | | | | | | | | | | | | | | | | Use the following kernel configuration option to enable: options BPF_JITTER If you want to use bpf_filter() instead (e. g., debugging), do: sysctl net.bpf.jitter.enable=0 to turn it off. Currently BIOCSETWF and bpf_mtap2() are unsupported, and bpf_mtap() is partially supported because 1) no need, 2) avoid expensive m_copydata(9). Obtained from: WinPcap 3.1 (for i386) Notes: svn path=/head/; revision=153151
* Sort.John Baldwin2005-11-231-4/+4
| | | | Notes: svn path=/head/; revision=152725
* Make COUNT_IPIS and COUNT_XINVLTLB_HITS real kernel options and takeJohn Baldwin2005-11-221-0/+2
| | | | | | | them out of machine/smptests.h. Notes: svn path=/head/; revision=152701
* Add support for XBOX to the FreeBSD port. The xbox architecture isWarner Losh2005-11-091-0/+3
| | | | | | | | | | | | | | | | | | | | | | | nearly identical to wintel/ia32, with a couple of tweaks. Since it is so similar to ia32, it is optionally added to a i386 kernel. This port is preliminary, but seems to work well. Further improvements will improve the interaction with syscons(4), port Linux nforce driver and future versions of the xbox. This supports the 64MB and 128MB boxes. You'll need the most recent CVS version of Cromwell (the Linux BIOS for the XBOX) to boot. Rink will be maintaining this port, and is interested in feedback. He's setup a website http://xbox-bsd.nl to report the latest developments. Any silly mistakes are my fault. Submitted by: Rink P.W. Springer rink at stack dot nl and Ed Schouten ed at fxq dot nl Notes: svn path=/head/; revision=152219
* Rename the KDB_STOP_NMI kernel option to STOP_NMI and make it apply to allJohn Baldwin2005-10-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | IPI_STOP IPIs. - Change the i386 and amd64 MD IPI code to send an NMI if STOP_NMI is enabled if an attempt is made to send an IPI_STOP IPI. If the kernel option is enabled, there is also a sysctl to change the behavior at runtime (debug.stop_cpus_with_nmi which defaults to enabled). This includes removing stop_cpus_nmi() and making ipi_nmi_selected() a private function for i386 and amd64. - Fix ipi_all(), ipi_all_but_self(), and ipi_self() on i386 and amd64 to properly handle bitmapped IPIs as well as IPI_STOP IPIs when STOP_NMI is enabled. - Fix ipi_nmi_handler() to execute the restart function on the first CPU that is restarted making use of atomic_readandclear() rather than assuming that the BSP is always included in the set of restarted CPUs. Also, the NMI handler didn't clear the function pointer meaning that subsequent stop and restarts could execute the function again. - Define a new macro HAVE_STOPPEDPCBS on i386 and amd64 to control the use of stoppedpcbs[] and always enable it for i386 and amd64 instead of being dependent on KDB_STOP_NMI. It works fine in both the NMI and non-NMI cases. Notes: svn path=/head/; revision=151634
* Remove the CPU_ENABLE_SSE option from the i386 and pc98 architectures,Xin LI2005-07-021-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | as they are already default for I686_CPU for almost 3 years, and CPU_DISABLE_SSE always disables it. On the other hand, CPU_ENABLE_SSE does not work for I486_CPU and I586_CPU. This commit has: - Removed the option from conf/options.* - Removed the option and comments from MD NOTES files - Simplified the CPU_ENABLE_SSE ifdef's so they don't deal with CPU_ENABLE_SSE from kernel configuration. (*) For most users, this commit should be largely no-op. If you used to place CPU_ENABLE_SSE into your kernel configuration for some reason, it is time to remove it. (*) The ifdef's of CPU_ENABLE_SSE are not removed at this point, since we need to change it to !defined(CPU_DISABLE_SSE) && defined(I686_CPU), not just !defined(CPU_DISABLE_SSE), if we really want to do so. Discussed on: -arch Approved by: re (scottl) Notes: svn path=/head/; revision=147741
* Move the KDB_STOP_NMI option from opt_global.h to opt_kdb.hPeter Wemm2005-06-291-1/+1
| | | | | | | Approved by: re Notes: svn path=/head/; revision=147674
* Connect reiserfs build to every platforms, not only i386 and pc98.Jean-Sébastien Pédron2005-06-211-3/+0
| | | | | | | | Reviewed by: mux (mentor) Approved by: re (dougb) Notes: svn path=/head/; revision=147513
* Connect the ReiserFS filesystem to the build (i386 only).Jean-Sébastien Pédron2005-05-241-0/+3
| | | | | | | Approved by: mux (mentor) Notes: svn path=/head/; revision=146565
* - Move the NPX_DEBUG option to options.{i386,pc98} and use opt_npx.h.Yoshihiro Takahashi2005-05-121-0/+1
| | | | | | | | - Move npx related defines to {i386,pc98}/include/npx.h to remove #include {isa,cbus}.h. Notes: svn path=/head/; revision=146137
* Implement an alternate method to stop CPUs when entering DDB. Normally we useDoug White2005-04-301-0/+3
| | | | | | | | | | | | | | | | | a regular IPI vector, but this vector is blocked when interrupts are disabled. With "options KDB_STOP_NMI" and debug.kdb.stop_cpus_with_nmi set, KDB will send an NMI to each CPU instead. The code also has a context-stuffing feature which helps ddb extract the state of processes running on the stopped CPUs. KDB_STOP_NMI is only useful with SMP and complains if SMP is not defined. This feature only applies to i386 and amd64 at the moment, but could be used on other architectures with the appropriate MD bits. Submitted by: ups Notes: svn path=/head/; revision=145727
* Remove support for mixed mode altogether now that we no longer use IRQ 0John Baldwin2005-04-141-1/+0
| | | | | | | | | when using an APIC. This simplifies the APIC code somewhat and also allows us to be pedantically more compliant with ACPI which mandates no use of mixed mode. Notes: svn path=/head/; revision=145080
* Bring back some of the ioctl junk that was removed in rev 1.59 as aOlivier Houchard2005-03-171-0/+1
| | | | | | | | | | i386-only kernel option, ASR_COMPAT, and under BURN_BRIDGES. It is really ugly, but raidutils depends on it. Discussed with: scottl Notes: svn path=/head/; revision=143729
* Remove CPU_ENABLE_TCC and hook the cpufreq p4tcc up to the build.Nate Lawson2005-02-231-1/+0
| | | | Notes: svn path=/head/; revision=142309
* Initiate deorbit burn sequence for 80386 support in FreeBSD: RemoveJohn Baldwin2004-11-161-1/+0
| | | | | | | 80386 (I386_CPU) support from the kernel. Notes: svn path=/head/; revision=137784
* Unconditionally support the AMD64 GART HW.David E. O'Brien2004-08-191-3/+0
| | | | Notes: svn path=/head/; revision=134043
* AMD64 on-CPU GART support.David E. O'Brien2004-08-161-0/+3
| | | | | | | | | | This also applies to AMD64 HW running 'i386' OS. Submitted by: Jung-uk Kim <jkim@niksun.com> Integration by: obrien Notes: svn path=/head/; revision=133852
* Add an "options MP_WATCHDOG" to i386. This option allows one of theRobert Watson2004-08-151-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | logical CPUs on a system to be used as a dedicated watchdog to cause a drop to the debugger and/or generate an NMI to the boot processor if the kernel ceases to respond. A sysctl enables the watchdog running out of the processor's idle thread; a callout is launched to reset a timer in the watchdog. If the callout fails to reset the timer for ten seconds, the watchdog will fire. The sysctl allows you to select which CPU will run the watchdog. A sample "debug.leak_schedlock" is included, which causes a sysctl to spin holding sched_lock in order to trigger the watchdog. On my Xeons, the watchdog is able to detect this failure mode and break into the debugger, which cannot otherwise be done without an NMI button. This option does not currently work with sched_ule due to ule's push notion of scheduling, similar to machdep.hlt_logical_cpus failing to work with that scheduler. On face value, this might seem somewhat inefficient, but there are a lot of dual-processor Xeons with HTT around, so using one as a watchdog for testing is not as inefficient as one might fear. Notes: svn path=/head/; revision=133759
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-11 19:57:52 +0000