aboutsummaryrefslogtreecommitdiff
path: root/sys/dev/dcons
Commit message (Collapse)AuthorAgeFilesLines
* MFC r347422:Ian Lepore2019-05-151-0/+18
| | | | | | | | | | | | | | | | | Allow dcons(4) to be unloaded when loaded as a module. When the module is unloaded, the tty devices are destroyed. That requires implementing the tsw_free callback to avoid a panic. This driver requires no particular cleanup to be done from the callback, but the module itself must remain in memory until the deferred tsw_free callbacks are invoked. These changes implement that by incrementing a reference count variable in the detach routine, and decrementing it in the tsw_free callback. The MOD_UNLOAD event handler doesn't return until the count drops to zero. PR: 237758 Notes: svn path=/stable/12/; revision=347624
* i386 4/4G split.Konstantin Belousov2018-04-132-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The change makes the user and kernel address spaces on i386 independent, giving each almost the full 4G of usable virtual addresses except for one PDE at top used for trampoline and per-CPU trampoline stacks, and system structures that must be always mapped, namely IDT, GDT, common TSS and LDT, and process-private TSS and LDT if allocated. By using 1:1 mapping for the kernel text and data, it appeared possible to eliminate assembler part of the locore.S which bootstraps initial page table and KPTmap. The code is rewritten in C and moved into the pmap_cold(). The comment in vmparam.h explains the KVA layout. There is no PCID mechanism available in protected mode, so each kernel/user switch forth and back completely flushes the TLB, except for the trampoline PTD region. The TLB invalidations for userspace becomes trivial, because IPI handlers switch page tables. On the other hand, context switches no longer need to reload %cr3. copyout(9) was rewritten to use vm_fault_quick_hold(). An issue for new copyout(9) is compatibility with wiring user buffers around sysctl handlers. This explains two kind of locks for copyout ptes and accounting of the vslock() calls. The vm_fault_quick_hold() AKA slow path, is only tried after the 'fast path' failed, which temporary changes mapping to the userspace and copies the data to/from small per-cpu buffer in the trampoline. If a page fault occurs during the copy, it is short-circuit by exception.s to not even reach C code. The change was motivated by the need to implement the Meltdown mitigation, but instead of KPTI the full split is done. The i386 architecture already shows the sizing problems, in particular, it is impossible to link clang and lld with debugging. I expect that the issues due to the virtual address space limits would only exaggerate and the split gives more liveness to the platform. Tested by: pho Discussed with: bde Sponsored by: The FreeBSD Foundation MFC after: 1 month Differential revision: https://reviews.freebsd.org/D14633 Notes: svn path=/head/; revision=332489
* spdx: initial adoption of licensing ID tags.Pedro F. Giffuni2017-11-185-0/+10
| | | | | | | | | | | | | | | | | | | | The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts. Special thanks to Wind River for providing access to "The Duke of Highlander" tool: an older (2014) run over FreeBSD tree was useful as a starting point. Initially, only tag files that use BSD 4-Clause "Original" license. RelNotes: yes Differential Revision: https://reviews.freebsd.org/D13133 Notes: svn path=/head/; revision=325966
* CALLOUT_MPSAFE has lost its meaning since r141428, i.e., for more than tenJung-uk Kim2015-05-221-1/+1
| | | | | | | | | | | | | years for head. However, it is continuously misused as the mpsafe argument for callout_init(9). Deprecate the flag and clean up callout_init() calls to make them more consistent. Differential Revision: https://reviews.freebsd.org/D2613 Reviewed by: jhb MFC after: 2 weeks Notes: svn path=/head/; revision=283291
* Garbage collect dragonfly and legacy FreeBSD system support from dcons(4).Will Andrews2015-01-213-38/+6
| | | | | | | | | | Submitted by: gibbs MFC after: 1 week Sponsored by: Spectra Logic MFSpectraBSD: 1110990 on 2015/01/06 Notes: svn path=/head/; revision=277505
* MFcalloutng:Alexander Motin2013-02-191-6/+12
| | | | | | | | | Make dcons input polling adaptive, reducing poll rate to 1Hz after several minutes of inactivty to reduce global interrupt rate. Most of users never used FireWire debugging, so it is not very useful to consume power by it. Notes: svn path=/head/; revision=247005
* kern cons: introduce infrastructure for console grabbing by kernelAndriy Gapon2011-12-171-0/+12
| | | | | | | | | | | | | | | At the moment grab and ungrab methods of all console drivers are no-ops. Current intended meaning of the calls is that the kernel takes control of console input. In the future the semantics may be extended to mean that the calling thread takes full ownership of the console (e.g. console output from other threads could be suspended). Inspired by: bde MFC after: 2 months Notes: svn path=/head/; revision=228631
* Mark all SYSCTL_NODEs static that have no corresponding SYSCTL_DECLs.Ed Schouten2011-11-071-1/+1
| | | | | | | | | The SYSCTL_NODE macro defines a list that stores all child-elements of that node. If there's no SYSCTL_DECL macro anywhere else, there's no reason why it shouldn't be static. Notes: svn path=/head/; revision=227309
* Follow up to r225203 refining break-to-debugger run-time configurationRobert Watson2011-08-271-1/+0
| | | | | | | | | | | | | | | improvements: (1) Implement new model in previously missed at91 UART driver (2) Move BREAK_TO_DEBUGGER and ALT_BREAK_TO_DEBUGGER from opt_comconsole.h to opt_kdb.h (spotted by np) (3) Garbage collect now-unused opt_comconsole.h MFC after: 3 weeks Approved by: re (bz) Notes: svn path=/head/; revision=225214
* Attempt to make break-to-debugger and alternative break-to-debugger moreRobert Watson2011-08-261-23/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | accessible: (1) Always compile in support for breaking into the debugger if options KDB is present in the kernel. (2) Disable both by default, but allow them to be enabled via tunables and sysctls debug.kdb.break_to_debugger and debug.kdb.alt_break_to_debugger. (3) options BREAK_TO_DEBUGGER and options ALT_BREAK_TO_DEBUGGER continue to behave as before -- only now instead of compiling in break-to-debugger support, they change the default values of the above sysctls to enable those features by default. Current kernel configurations should, therefore, continue to behave as expected. (4) Migrate alternative break-to-debugger state machine logic out of individual device drivers into centralised KDB code. This has a number of upsides, but also one downside: it's now tricky to release sio spin locks when entering the debugger, so we don't. However, similar logic does not exist in other device drivers, including uart. (5) dcons requires some special handling; unlike other console types, it allows overriding KDB's own debugger selection, so we need a new interface to KDB to allow that to work. GENERIC kernels in -CURRENT will now support break-to-debugger as long as appropriate boot/run-time options are set, which should improve the debuggability of BETA kernels significantly. MFC after: 3 weeks Reviewed by: kib, nwhitehorn Approved by: re (bz) Notes: svn path=/head/; revision=225203
* Last minute TTY API change: remove mutex argument from tty_alloc().Ed Schouten2009-05-291-1/+1
| | | | | | | | | | | | | I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. Notes: svn path=/head/; revision=193018
* Reduce the dcons polling frequency to 25 Hz.Ed Schouten2009-04-061-1/+1
| | | | | | | | | | | | | It makes little sense to use 100 Hz polling in dcons. We cannot live without polling, because that's just how dcons works. It polls the buffer filled by the firewire hardware. 25 Hz is probably enough for most use cases. Discussed with: rwatson Tested by: kan Notes: svn path=/head/; revision=190771
* Fix logic in MOD_LOAD handler to call dcons_attach after all successfulAlexander Kabaev2009-04-061-1/+2
| | | | | | | | | dcons_drv_init invocations. Testing return value for 0 does not work for cases where dcons_drv_init was called already as part of low level console initialization. Notes: svn path=/head/; revision=190756
* We need to initialize the console for dcons to work.Warner Losh2009-03-131-0/+1
| | | | | | | Submitted by: nork@ Notes: svn path=/head/; revision=189752
* Check the return values of contigmalloc(9) as well as bus_dma(9)Marius Strobl2009-01-072-11/+24
| | | | | | | | | | | | | | | | | functions and stop attaching of dcons(4) and dcons_crom(4) if they indicate failure. This fixes a panic seen on sparc64 machines with no free physical memory in the requested 32-bit region but still doesn't make dcons(4)/dcons_crom(4) these work. I think the latter can be fixed by simply specifying ~0UL as the upper limit for contigmalloc(9) and letting the bounce pages and the IOMMU respectively handle limitations of the DMA engine. I didn't want to change that without the consensus of simokawa@ though, who unfortunately didn't reply so far. MFC after: 1 week Notes: svn path=/head/; revision=186876
* Given that the buffer dcons_crom(4) exposes is used for both inputMarius Strobl2008-11-191-1/+1
| | | | | | | | | | | | | | and output, set BUS_DMA_COHERENT when creating the DMA map used for loading the buffer. As a side-effect this solves locking issues on sparc64 when dcons(4) calls bus_dmamap_sync(9) while in an interrupt filter, which are executed in a critical section, and iommu(4) has to use a sleep lock when taking advantage of the streaming buffer. Reported and tested by: kensmith Approved by: simokawa Notes: svn path=/head/; revision=185108
* Also make dcons(4) use MPSAFE callouts.Ed Schouten2008-11-191-1/+1
| | | | | | | | The callout locks the TTY layer the way it should, so there is no reason why its callout shouldn't set this flag. Notes: svn path=/head/; revision=185107
* Integrate the new MPSAFE TTY layer to the FreeBSD operating system.Ed Schouten2008-08-202-346/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The last half year I've been working on a replacement TTY layer for the FreeBSD kernel. The new TTY layer was designed to improve the following: - Improved driver model: The old TTY layer has a driver model that is not abstract enough to make it friendly to use. A good example is the output path, where the device drivers directly access the output buffers. This means that an in-kernel PPP implementation must always convert network buffers into TTY buffers. If a PPP implementation would be built on top of the new TTY layer (still needs a hooks layer, though), it would allow the PPP implementation to directly hand the data to the TTY driver. - Improved hotplugging: With the old TTY layer, it isn't entirely safe to destroy TTY's from the system. This implementation has a two-step destructing design, where the driver first abandons the TTY. After all threads have left the TTY, the TTY layer calls a routine in the driver, which can be used to free resources (unit numbers, etc). The pts(4) driver also implements this feature, which means posix_openpt() will now return PTY's that are created on the fly. - Improved performance: One of the major improvements is the per-TTY mutex, which is expected to improve scalability when compared to the old Giant locking. Another change is the unbuffered copying to userspace, which is both used on TTY device nodes and PTY masters. Upgrading should be quite straightforward. Unlike previous versions, existing kernel configuration files do not need to be changed, except when they reference device drivers that are listed in UPDATING. Obtained from: //depot/projects/mpsafetty/... Approved by: philip (ex-mentor) Discussed: on the lists, at BSDCan, at the DevSummit Sponsored by: Snow B.V., the Netherlands dcons(4) fixed by: kan Notes: svn path=/head/; revision=181905
* Spell KDB_REQ_REBOOT correctly.Peter Wemm2008-05-051-1/+1
| | | | Notes: svn path=/head/; revision=178771
* Expand kdb_alt_break a little, most commonly used with the optionPeter Wemm2008-05-041-10/+24
| | | | | | | | | | | | | | | | | | | | | | ALT_BREAK_TO_DEBUGGER. In addition to "Enter ~ ctrl-B" (to enter the debugger), there is now "Enter ~ ctrl-P" (force panic) and "Enter ~ ctrl-R" (request clean reboot, ala ctrl-alt-del on syscons). We've used variations of this at work. The force panic sequence is best used with KDB_UNATTENDED for when you just want it to dump and get on with it. The reboot request is a safer way of getting into single user than a power cycle. eg: you've hosed the ability to log in (pam, rtld, etc). It gives init the reboot signal, which causes an orderly reboot. I've taken my best guess at what the !x86 and non-sio code changes should be. This also makes sio release its spinlock before calling KDB/DDB. Notes: svn path=/head/; revision=178766
* Add a new 'why' argument to kdb_enter(), and a set of constants to useRobert Watson2007-12-251-2/+4
| | | | | | | | | | | | for that argument. This will allow DDB to detect the broad category of reason why the debugger has been entered, which it can use for the purposes of deciding which DDB script to run. Assign approximate why values to all current consumers of the kdb_enter() interface. Notes: svn path=/head/; revision=174898
* We don't need to call dcons_poll event handlers if KDB is not active.Hidetoshi Shimokawa2007-08-171-3/+9
| | | | | | | Approved by: re (kensmith) Notes: svn path=/head/; revision=171867
* - Don't force to be the GDB port since dcons(4) is in GENERIC now.Hidetoshi Shimokawa2007-06-111-1/+5
| | | | | | | | | To enable the GDB port of dcons(4), you need to put dcons_gdb=1 in /boot/loader.conf. Notes: svn path=/head/; revision=170537
* Don't invalidate dcons buffer on shutdown.Hidetoshi Shimokawa2007-06-081-0/+2
| | | | | | | We would like to keep connection after halt. Notes: svn path=/head/; revision=170426
* Add the address of IDT in the configuration ROM. (i386/amd64 only)Hidetoshi Shimokawa2007-06-082-0/+27
| | | | | | | | | | | | | | | A change to dconschat(8) will follow so that it can bomb this address over FireWire to reset a wedged system. Though this method is just a hack and far from perfection, it should be useful if you don't want to go machine room just to reset or to power-cycle a machine without remote-managed power supply. And much better than doing: # fwcontrol -m target-eui64 # dd if=/dev/zero of=/dev/fwmem0.2 bs=1m Notes: svn path=/head/; revision=170420
* Replace breakpoint() with kdb_enter().Hidetoshi Shimokawa2007-06-081-2/+2
| | | | Notes: svn path=/head/; revision=170418
* Poll bus resets on FireWire while kdb/gdb is active.Hidetoshi Shimokawa2007-06-083-0/+19
| | | | | | | | | | | | | | | | | | Now, it's safe to call the fwohci interrupt(polling) routine while ddb/gdb is active. After this change, a dcons connnection over FireWire can survive bus resets even in kernel debugger. This means that it is not too late to plug a FireWire cable after a panic to investigate the problem. Actually there is a small window(between a jump to kernel from loader and initialization of dcons_crom) in which no one can take care of a bus reset. Except that window, firewire console should keep working from loader to reboot even with a panic and a bus reset. (as far as you enable LOADER_FIREWIRE_SUPPORT) Notes: svn path=/head/; revision=170408
* We should better ignore a break on gdb port if gdb is not enabled.Hidetoshi Shimokawa2007-05-281-2/+2
| | | | Notes: svn path=/head/; revision=170043
* Change default value of hw.firewire.dcons_crom.force_console to 0Hidetoshi Shimokawa2007-05-271-1/+1
| | | | | | | | | for least astonishment. MFC after: 3 days Notes: svn path=/head/; revision=170018
* Make compile without GDB option.Hidetoshi Shimokawa2007-05-271-4/+11
| | | | | | | MFC after: 3 days Notes: svn path=/head/; revision=170017
* Include stand.h for loader.Hidetoshi Shimokawa2007-05-251-0/+3
| | | | | | | MFC after: 3 days Notes: svn path=/head/; revision=169972
* Sweep kernel replacing suser(9) calls with priv(9) calls, assigningRobert Watson2006-11-061-1/+3
| | | | | | | | | | | | | | | | specific privilege names to a broad range of privileges. These may require some future tweaking. Sponsored by: nCircle Network Security, Inc. Obtained from: TrustedBSD Project Discussed on: arch@ Reviewed (at least in part) by: mlaier, jmg, pjd, bde, ceri, Alex Lyashkov <umka at sevcity dot net>, Skip Ford <skip dot ford at verizon dot net>, Antoine Brodin <antoine dot brodin at laposte dot net> Notes: svn path=/head/; revision=164033
* Convert to new console interface.Poul-Henning Kamp2006-05-261-9/+7
| | | | Notes: svn path=/head/; revision=158959
* Eliminate gdb_checkc member from GDB_DBGPORT(), it is never used.Poul-Henning Kamp2006-05-261-9/+1
| | | | | | | | Use polling behaviour for gdb_getc() where convenient, this edges us closer to the console code. Notes: svn path=/head/; revision=158950
* Use ttyalloc() instead of ttymalloc()Poul-Henning Kamp2006-01-041-2/+2
| | | | Notes: svn path=/head/; revision=154016
* Fix -Wundef warnings found when compiling i386 LINT, GENERIC andRuslan Ermilov2005-12-051-3/+3
| | | | | | | custom kernels. Notes: svn path=/head/; revision=153110
* Make ttyconsolemode() call ttsetwater() so that drivers don't have to.Poul-Henning Kamp2005-10-161-1/+0
| | | | Notes: svn path=/head/; revision=151388
* Start each of the license/copyright comments with /*-, minor shuffle of linesWarner Losh2005-01-065-5/+5
| | | | Notes: svn path=/head/; revision=139749
* Use dcons buffer passed by loader on amd64.Hidetoshi Shimokawa2004-10-281-2/+4
| | | | Notes: svn path=/head/; revision=137013
* - Use quad_t for dcons buffer address and size.Hidetoshi Shimokawa2004-10-241-4/+11
| | | | | | | - Allow read/write access to dcons buffer passed by loader(8). Notes: svn path=/head/; revision=136898
* Check _BOOT flag.Hidetoshi Shimokawa2004-10-221-3/+3
| | | | Notes: svn path=/head/; revision=136781
* Add new function ttyinitmode() which sets our systemwide defaultPoul-Henning Kamp2004-10-181-6/+1
| | | | | | | | | | | | | | | | | modes on a tty structure. Both the ".init" and the current settings are initialized allowing the function to be used both at attach and open time. The function takes an argument to decide if echoing should be enabled. Echoing should not be enabled for regular physical serial ports unless they are consoles, in which case they should be configured by ttyconsolemode() instead. Use the new function throughout. Notes: svn path=/head/; revision=136680
* Fix warnings on non-i386 arch.Hidetoshi Shimokawa2004-10-141-0/+2
| | | | | | | Submitted by: keramida Notes: svn path=/head/; revision=136498
* - Split dcons core code and OS dependent code.Hidetoshi Shimokawa2004-10-135-650/+883
| | | | | | | | | - Implement dcons_ischar() and dcons_load_buffer(). - If loader passed a dcons buffer address, keep using it. (We still need a patch to cheat memory management system.) Notes: svn path=/head/; revision=136467
* Invalidate dcons buffer on shutdown.Hidetoshi Shimokawa2004-09-261-0/+1
| | | | Notes: svn path=/head/; revision=135799
* Sync with DragonFly BSD.Hidetoshi Shimokawa2004-09-241-17/+93
| | | | Notes: svn path=/head/; revision=135733
* Preparation commit for the tty cleanups that will follow in the nearPoul-Henning Kamp2004-07-151-2/+2
| | | | | | | | | | | | future: rename ttyopen() -> tty_open() and ttyclose() -> tty_close(). We need the ttyopen() and ttyclose() for the new generic cdevsw functions for tty devices in order to have consistent naming. Notes: svn path=/head/; revision=132226
* Do a pass over all modules in the kernel and make them return EOPNOTSUPPPoul-Henning Kamp2004-07-151-0/+3
| | | | | | | | | | | for unknown events. A number of modules return EINVAL in this instance, and I have left those alone for now and instead taught MOD_QUIESCE to accept this as "didn't do anything". Notes: svn path=/head/; revision=132199
* Re-enable debugger port.Hidetoshi Shimokawa2004-07-131-3/+124
| | | | Notes: svn path=/head/; revision=132092
* Update for the KDB framework:Marcel Moolenaar2004-07-101-49/+4
| | | | | | | | | | | | | | | o Use kdb_alt_break() to handle the alternate break sequence instead of handcoding it here. o Remove GDB kluges to make this driver work with the pre-KDB remote GDB code. o Call kdb_enter() instead of Debugger(). Note that with this commit the dcons(4) driver cannot be used for remote debugging anymore. This driver has to use the new GDB debug port interface instead. Such has not been done yet. Notes: svn path=/head/; revision=131912
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-07 21:56:23 +0000