headers: Move B_KERNEL_{EXECUTE,STACK}_AREA into KernelExport.h.
There is no good reason to put them in a private header. No functional change (but drivers now have access to these constants.) Change-Id: I7ac00a120ab44fbc110bc858dfd87d69d0061135 Reviewed-on: https://review.haiku-os.org/c/haiku/+/2294 Reviewed-by: Adrien Destugues <pulkomandy@gmail.com> Reviewed-by: John Scipione <jscipione@gmail.com>
This commit is contained in:
parent
0d312fea71
commit
dda8e77b8e
@ -113,6 +113,8 @@ typedef struct {
|
||||
/* area protection flags for the kernel */
|
||||
#define B_KERNEL_READ_AREA (1 << 4)
|
||||
#define B_KERNEL_WRITE_AREA (1 << 5)
|
||||
#define B_KERNEL_EXECUTE_AREA (1 << 6)
|
||||
#define B_KERNEL_STACK_AREA (1 << 7)
|
||||
|
||||
/* MTR attributes for mapping physical memory (Intel Architecture only) */
|
||||
// TODO: rename those to something more meaningful
|
||||
|
@ -11,14 +11,6 @@
|
||||
#include <OS.h>
|
||||
|
||||
|
||||
// additional protection flags
|
||||
// Note: the VM probably won't support all combinations - it will try
|
||||
// its best, but create_area() will fail if it has to.
|
||||
// Of course, the exact behaviour will be documented somewhere...
|
||||
|
||||
#define B_KERNEL_EXECUTE_AREA 0x40
|
||||
#define B_KERNEL_STACK_AREA 0x80
|
||||
|
||||
#define B_USER_PROTECTION \
|
||||
(B_READ_AREA | B_WRITE_AREA | B_EXECUTE_AREA | B_STACK_AREA)
|
||||
#define B_KERNEL_PROTECTION \
|
||||
|
Loading…
Reference in New Issue
Block a user