Displaying 3 results from an estimated 3 matches for "mp_config".
Did you mean:
mm_config
2018 Feb 09
0
retpoline mitigation and 6.0
...046a64 412 pr_warn("At line %d, gsi_base is %d\n", __LINE__,gsi_base);
1: x/i $pc
=> 0xc1046a64 <mp_register_ioapic+180>: mov %edi,0xc(%esp)
2: gsi_base = 0
(gdb) p/x 0xc+$esp
$1 = 0xc1b2fe34
(gdb) disp *(int *)0xc1b2fe34
3: *(int *)0xc1b2fe34 = 120
(gdb) ni
414 ioapics[idx].mp_config.type = MP_IOAPIC;
1: x/i $pc
=> 0xc1046a68 <mp_register_ioapic+184>: imul $0x2c,%ebx,%edi
2: gsi_base = 0
3: *(int *)0xc1b2fe34 = 0
(gdb)
0xc1046a6b 414 ioapics[idx].mp_config.type = MP_IOAPIC;
1: x/i $pc
=> 0xc1046a6b <mp_register_ioapic+187>: movb $0x2,-0x3e2cb1bc(%edi)
2:...
2018 Feb 09
2
retpoline mitigation and 6.0
On Fri, 2018-02-09 at 10:36 +0000, David Woodhouse wrote:
>
> Did you get anywhere with the function attribute? Having isolated the
> next boot failure to "it goes away if I compile io_apic.c without
> retpoline", bisecting it per-function would help to further delay the
> bit where I actually have to start *thinking*...
It's mp_register_ioapic(), and only when
2018 Feb 09
3
retpoline mitigation and 6.0
...> __LINE__,gsi_base);
> 1: x/i $pc
> => 0xc1046a64 <mp_register_ioapic+180>: mov %edi,0xc(%esp)
> 2: gsi_base = 0
> (gdb) p/x 0xc+$esp
> $1 = 0xc1b2fe34
> (gdb) disp *(int *)0xc1b2fe34
> 3: *(int *)0xc1b2fe34 = 120
> (gdb) ni
> 414 ioapics[idx].mp_config.type = MP_IOAPIC;
> 1: x/i $pc
> => 0xc1046a68 <mp_register_ioapic+184>: imul $0x2c,%ebx,%edi
> 2: gsi_base = 0
> 3: *(int *)0xc1b2fe34 = 0
> (gdb)
> 0xc1046a6b 414 ioapics[idx].mp_config.type = MP_IOAPIC;
> 1: x/i $pc
> => 0xc1046a6b <mp_re...