Re: why Linux kernel will update BIOS's interrupt remapping table base address ? why does Linux Kernel create a new table instead of the one that BIOS provided ?

On Mon, Jul 9, 2012 at 8:17 PM, Lin-Bao Zhang <2004.zh...@gmail.com> wrote: > for this thing , we have known that , we can append "x2apic_phys" to > tell linux kernel we support x2apic physical mode. > but I found that x2apic_phys is not enough .we still found panic info > in RHEL6.2(2.6.32)

Re: why Linux kernel will update BIOS's interrupt remapping table base address ? why does Linux Kernel create a new table instead of the one that BIOS provided ?

for this thing , we have known that , we can append "x2apic_phys" to tell linux kernel we support x2apic physical mode. but I found that x2apic_phys is not enough .we still found panic info in RHEL6.2(2.6.32) kernel,but on linux kernel-3.4.4 ,no this issue again. any comment for this bug ?

Re: why Linux kernel will update BIOS's interrupt remapping table base address ? why does Linux Kernel create a new table instead of the one that BIOS provided ?

for this thing , we have known that , we can append x2apic_phys to tell linux kernel we support x2apic physical mode. but I found that x2apic_phys is not enough .we still found panic info in RHEL6.2(2.6.32) kernel,but on linux kernel-3.4.4 ,no this issue again. any comment for this bug ?

Re: why Linux kernel will update BIOS's interrupt remapping table base address ? why does Linux Kernel create a new table instead of the one that BIOS provided ?

On Mon, Jul 9, 2012 at 8:17 PM, Lin-Bao Zhang 2004.zh...@gmail.com wrote: for this thing , we have known that , we can append x2apic_phys to tell linux kernel we support x2apic physical mode. but I found that x2apic_phys is not enough .we still found panic info in RHEL6.2(2.6.32) kernel,but on