Messages in this thread | | | Date | Mon, 24 Dec 2012 20:04:18 -0800 | Subject | Re: [PATCH v7 06/27] x86, 64bit: early #PF handler set page table | From | Yinghai Lu <> |
| |
On Mon, Dec 24, 2012 at 4:16 PM, H. Peter Anvin <hpa@zytor.com> wrote: > On 12/20/2012 08:56 AM, Yinghai Lu wrote: >>> >>> >>> So in that case, kgdb is broken and will need to be fixed up. That >>> happens all the time with debugging tools. >> >> >> If there is a way that we can make all parties happy, we really should >> not break KGDB. >> >> Please reconsider to stop #PF handler in x86_64_start_kernel. in that case >> 1. microcode update still can use #PF handler to find microcode in >> ramdisk and use it. >> 2. kernel that is loaded above 4G, could set mapping in C instead of >> set that in head_64.S >> and use ioremap to access zero_page >> 3. KGDB still can call early_trap_init early before init_mem_mapping. >> > > Yinghai, this is total and utter bullshit. > > We should *fix* kgdb, not pave around it. I refuse to have kgdb be yet > another Xen turning random kernel internals into ABIs.
well, I updated for-x86-boot-v7 that stop #PF handler after init_mem_mapping.
it has fix for AMD system aka reverting far jmp to ret.
Yinghai
| |