src/sys/ia64/include/kdb.h, branch main

Remove ia64.

2014-07-07T00:27:09Z

This includes: o All directories named *ia64* o All files named *ia64* o All ia64-specific code guarded by __ia64__ o All ia64-specific makefile logic o Mention of ia64 in comments and documentation This excludes: o Everything under contrib/ o Everything under crypto/ o sys/xen/interface o sys/sys/elf_common.h Discussed at: BSDcan

Move the implementation of kdb_cpu_trap() from to

2014-03-16T22:56:22Z

machdep.c. This makes it easier to add conditional code based on options.

Define struct pcpu_md as the only MD field of struct pcpu (pc_acpi_id

2009-12-07T06:41:27Z

excluded, as it's used by MI code) and mode the sysctl variables from pcpu_stats to pcpu_md. Adjust all references accordingly. While nearby, change the PCPU sysctl tree so that they match the CPU device sysctl tree -- they are now children of a static node called "machdep.cpu" and are named only with their cpu ID.

Add kdb_cpu_sync_icache(), intended to synchronize instruction

2007-06-09T21:55:17Z

caches with data caches after writing to memory. This typically is required to make breakpoints work on ia64 and powerpc. For those architectures the function is implemented.

Now that printf() needs the PCPU, set it up before we call printf().

2006-11-18T21:52:26Z

Change the pc_pcb field from a pointer to struct pcb to struct pcb so that sizeof(struct pcb) includes the PCB we use for IPI_STOP. Statically declare early_pcb so that we don't have to allocate the PCB for thread0. This way we can setup the PCPU before cninit() and thus before we use printf().

Eliminate HAVE_STOPPEDPCBS. On ia64 the PCPU holds a pointer to the

2006-04-03T22:51:47Z

PCB in which the context of stopped CPUs is stored. To access this PCB from KDB, we introduce a new define, called KDB_STOPPEDPCB. The definition, when present, lives in and abstracts where MD code saves the context. Define KDB_STOPPEDPCB on i386, amd64, alpha and sparc64 in accordance to previous code.

/* -> /*- for copyright notices, minor format tweaks as necessary

2005-01-06T22:18:23Z

Introduce the KDB debugger frontend. The frontend provides a framework

2004-07-10T18:40:12Z

in which multiple (presumably different) debugger backends can be configured and which provides basic services to those backends. Besides providing services to backends, it also serves as the single point of contact for any and all code that wants to make use of the debugger functions, such as entering the debugger or handling of the alternate break sequence. For this purpose, the frontend has been made non-optional. All debugger requests are forwarded or handed over to the current backend, if applicable. Selection of the current backend is done by the debug.kdb.current sysctl. A list of configured backends can be obtained with the debug.kdb.available sysctl. One can enter the debugger by writing to the debug.kdb.enter sysctl.