search for: mtrr_bp_init

...printk(" %08lx", c->x86_capability[i]); printk("\n"); - +} + +void __init identify_boot_cpu(void) +{ + identify_cpu(&boot_cpu_data); + + /* Init Machine Check Exception if available. */ + mcheck_init(&boot_cpu_data); + + sysenter_setup(); + enable_sep_cpu(); + + mtrr_bp_init(); +} + +void __cpuinit identify_secondary_cpu(struct cpuinfo_x86 *c) +{ + int i; + + BUG_ON(c == &boot_cpu_data); + identify_cpu(c); /* * On SMP, boot_cpu_data holds the common feature set between * all CPUs; so make sure that we indicate which features are * common between the CPUs...

...printk(" %08lx", c->x86_capability[i]); printk("\n"); - +} + +void __init identify_boot_cpu(void) +{ + identify_cpu(&boot_cpu_data); + + /* Init Machine Check Exception if available. */ + mcheck_init(&boot_cpu_data); + + sysenter_setup(); + enable_sep_cpu(); + + mtrr_bp_init(); +} + +void __cpuinit identify_secondary_cpu(struct cpuinfo_x86 *c) +{ + int i; + + BUG_ON(c == &boot_cpu_data); + identify_cpu(c); /* * On SMP, boot_cpu_data holds the common feature set between * all CPUs; so make sure that we indicate which features are * common between the CPUs...

...t;] ? warn_slowpath_common+0x87/0xc0 [<ffffffff81069a86>] ? warn_slowpath_fmt+0x46/0x50 [<ffffffff8102713e>] ? generic_get_mtrr+0x11e/0x140 [<ffffffff81c2bfd1>] ? mtrr_cleanup+0x8c/0x3fd [<ffffffff81c2ae47>] ? get_mtrr_state+0x2ec/0x2fb [<ffffffff81c2a988>] ? mtrr_bp_init+0x1ab/0x1d2 [<ffffffff81c254d8>] ? setup_arch+0x4b8/0xaea [<ffffffff814ec4c5>] ? printk+0x41/0x44 [<ffffffff81c1fc2e>] ? start_kernel+0xdc/0x430 [<ffffffff81c1f33a>] ? x86_64_start_reservations+0x125/0x129 [<ffffffff81c1f438>] ? x86_64_start_kernel+0xfa/0x109...

...81069997>] ? warn_slowpath_common+0x87/0xc0 [<ffffffff81069a86>] ? warn_slowpath_fmt+0x46/0x50 [<ffffffff8102713e>] ? generic_get_mtrr+0x11e/0x140 [<ffffffff81c2bfd1>] ? mtrr_cleanup+0x8c/0x3fd [<ffffffff81c2ae47>] ? get_mtrr_state+0x2ec/0x2fb [<ffffffff81c2a988>] ? mtrr_bp_init+0x1ab/0x1d2 [<ffffffff81c254d8>] ? setup_arch+0x4b8/0xaea [<ffffffff814ec4c5>] ? printk+0x41/0x44 [<ffffffff81c1fc2e>] ? start_kernel+0xdc/0x430 [<ffffffff81c1f33a>] ? x86_64_start_reservations+0x125/0x129 [<ffffffff81c1f438>] ? x86_64_start_kernel+0xfa/0x109 time --...

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine