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.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
