ea2abd110b
ROUNDUP to use '*' and '/' -- the compiler will optimize that for powers of two anyway and this implementation works for other numbers as well. * The thread::fault_handler use in C[++] code was broken with gcc 4. At least when other functions were invoked. Trying to trick the compiler wasn't a particularly good idea anyway, since the next compiler version could break the trick again. So the general policy is to use the fault handlers only in assembly code where we have full control. Changed that for x86 (save for the vm86 mode, which has a similar mechanism), but not for the other architectures. * Introduced fault_handler, fault_handler_stack_pointer, and fault_jump_buffer fields in the cpu_ent structure, which must be used instead of thread::fault_handler in the kernel debugger. Consequently user_memcpy() must not be used in the kernel debugger either. Introduced a debug_memcpy() instead. * Introduced debug_call_with_fault_handler() function which calls a function in a setjmp() and fault handler context. The architecture specific backend arch_debug_call_with_fault_handler() has only been implemented for x86 yet. * Introduced debug_is_kernel_memory_accessible() for use in the kernel debugger. It determines whether a range of memory can be accessed in the way specified. The architecture specific back end arch_vm_translation_map_is_kernel_page_accessible() has only been implemented for x86 yet. * Added arch_debug_unset_current_thread() (only implemented for x86) to unset the current thread pointer in the kernel debugger. When entering the kernel debugger we do some basic sanity checks of the currently set thread structure and unset it, if they fail. This allows certain commands (most importantly the stack trace command) to avoid accessing the thread structure. * x86: When handling a double fault, we do now install a special handler for page faults. This allows us to gracefully catch faulting commands, even if e.g. the thread structure is toast. We are now in much better shape to deal with double faults. Hopefully avoiding the triple faults that some people have been experiencing on their hardware and ideally even allowing to use the kernel debugger normally. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@32073 a95241bf-73f2-0310-859d-f6bbb57e9c96
42 lines
1.3 KiB
C
42 lines
1.3 KiB
C
/*
|
|
** Copyright 2002-2004, The Haiku Team. All rights reserved.
|
|
** Distributed under the terms of the Haiku License.
|
|
**
|
|
** Copyright 2001-2002, Travis Geiselbrecht. All rights reserved.
|
|
** Distributed under the terms of the NewOS License.
|
|
*/
|
|
#ifndef KERNEL_ARCH_VM_TRANSLATION_MAP_H
|
|
#define KERNEL_ARCH_VM_TRANSLATION_MAP_H
|
|
|
|
|
|
#include <vm_translation_map.h>
|
|
|
|
|
|
#ifdef __cplusplus
|
|
extern "C" {
|
|
#endif
|
|
|
|
status_t arch_vm_translation_map_init_map(vm_translation_map *map, bool kernel);
|
|
status_t arch_vm_translation_map_init_kernel_map_post_sem(vm_translation_map *map);
|
|
|
|
status_t arch_vm_translation_map_init(struct kernel_args *args);
|
|
status_t arch_vm_translation_map_init_post_area(struct kernel_args *args);
|
|
status_t arch_vm_translation_map_init_post_sem(struct kernel_args *args);
|
|
|
|
// Quick function to map a page in regardless of map context. Used in VM
|
|
// initialization before most vm data structures exist.
|
|
status_t arch_vm_translation_map_early_map(struct kernel_args *args, addr_t va, addr_t pa,
|
|
uint8 attributes, addr_t (*get_free_page)(struct kernel_args *));
|
|
|
|
bool arch_vm_translation_map_is_kernel_page_accessible(addr_t virtualAddress,
|
|
uint32 protection);
|
|
|
|
#ifdef __cplusplus
|
|
}
|
|
#endif
|
|
|
|
#include <arch_vm_translation_map.h>
|
|
|
|
#endif /* KERNEL_ARCH_VM_TRANSLATION_MAP_H */
|
|
|