Changeset View
Changeset View
Standalone View
Standalone View
sys/x86/include/x86_var.h
Show First 20 Lines • Show All 92 Lines • ▼ Show 20 Lines | |||||
void nmi_call_kdb_smp(u_int type, struct trapframe *frame); | void nmi_call_kdb_smp(u_int type, struct trapframe *frame); | ||||
void nmi_handle_intr(u_int type, struct trapframe *frame); | void nmi_handle_intr(u_int type, struct trapframe *frame); | ||||
void pagecopy(void *from, void *to); | void pagecopy(void *from, void *to); | ||||
void printcpuinfo(void); | void printcpuinfo(void); | ||||
int pti_get_default(void); | int pti_get_default(void); | ||||
int user_dbreg_trap(register_t dr6); | int user_dbreg_trap(register_t dr6); | ||||
int minidumpsys(struct dumperinfo *); | int minidumpsys(struct dumperinfo *); | ||||
struct pcb *get_pcb_td(struct thread *td); | struct pcb *get_pcb_td(struct thread *td); | ||||
void phys_avail_reserve(vm_paddr_t start, vm_paddr_t end); | |||||
imp: Is this a MI interface we want all our MD code to use to cope with similar issues that we're… | |||||
kibUnsubmitted Not Done Inline ActionsI believe this is highly MD code and interface. Early manipulations with phys_avail[] cannot be anything else. kib: I believe this is highly MD code and interface. Early manipulations with phys_avail[] cannot… | |||||
johalun0_gmail.comAuthorUnsubmitted Not Done Inline ActionsYes. The question is, do we want this function for 32bit as well (I left this open for discussion)? For graphics I can't think of a future we're will need it for i386. If we keep it amd64 only, what would be the correct header for it? johalun0_gmail.com: Yes. The question is, do we want this function for 32bit as well (I left this open for… | |||||
kibUnsubmitted Not Done Inline ActionsWe have amd64/include/md_var.h and i386/include/md_var.h. x86_var.h is just a common extract. But I do not see why i386 should be excluded. kib: We have amd64/include/md_var.h and i386/include/md_var.h. x86_var.h is just a common extract. | |||||
johalun0_gmail.comAuthorUnsubmitted Not Done Inline ActionsIs there a common source file for i386/amd64 that make sense to put phys_avail() in (since the implementations would be the same) or should we duplicate it in machdep.c? johalun0_gmail.com: Is there a common source file for i386/amd64 that make sense to put phys_avail() in (since the… | |||||
kibUnsubmitted Not Done Inline ActionsI believe a new source file in x86/x86 is the best. kib: I believe a new source file in x86/x86 is the best. | |||||
#endif | #endif | ||||
Context not available. |
Is this a MI interface we want all our MD code to use to cope with similar issues that we're currently coping with in other, ad-hoc ways?