Searched hist:"84525 e55c1cda9ca873094342410f3bd22d983b4" (Results 1 – 6 of 6) sorted by relevance
| /freebsd/sys/x86/include/ |
| H A D | x86_smp.h | diff 84525e55c1cda9ca873094342410f3bd22d983b4 Thu Aug 10 11:16:03 CEST 2017 Roger Pau Monné <royger@FreeBSD.org> x86: make the arrays that depend on MAX_APIC_ID dynamic
So that MAX_APIC_ID can be bumped without wasting memory.
Note that the usage of MAX_APIC_ID in the SRAT parsing forces the
parser to allocate memory directly from the phys_avail physical memory
array, which is not the best approach probably, but I haven't found
any other way to allocate memory so early in boot. This memory is not
returned to the system afterwards, but at least it's sized according
to the maximum APIC ID found in the MADT table.
Sponsored by: Citrix Systems R&D
MFC after: 1 month
Reviewed by: kib
Differential revision: https://reviews.freebsd.org/D11912
|
| H A D | apicvar.h | diff 84525e55c1cda9ca873094342410f3bd22d983b4 Thu Aug 10 11:16:03 CEST 2017 Roger Pau Monné <royger@FreeBSD.org> x86: make the arrays that depend on MAX_APIC_ID dynamic
So that MAX_APIC_ID can be bumped without wasting memory.
Note that the usage of MAX_APIC_ID in the SRAT parsing forces the
parser to allocate memory directly from the phys_avail physical memory
array, which is not the best approach probably, but I haven't found
any other way to allocate memory so early in boot. This memory is not
returned to the system afterwards, but at least it's sized according
to the maximum APIC ID found in the MADT table.
Sponsored by: Citrix Systems R&D
MFC after: 1 month
Reviewed by: kib
Differential revision: https://reviews.freebsd.org/D11912
|
| /freebsd/sys/x86/acpica/ |
| H A D | srat.c | diff 84525e55c1cda9ca873094342410f3bd22d983b4 Thu Aug 10 11:16:03 CEST 2017 Roger Pau Monné <royger@FreeBSD.org> x86: make the arrays that depend on MAX_APIC_ID dynamic
So that MAX_APIC_ID can be bumped without wasting memory.
Note that the usage of MAX_APIC_ID in the SRAT parsing forces the
parser to allocate memory directly from the phys_avail physical memory
array, which is not the best approach probably, but I haven't found
any other way to allocate memory so early in boot. This memory is not
returned to the system afterwards, but at least it's sized according
to the maximum APIC ID found in the MADT table.
Sponsored by: Citrix Systems R&D
MFC after: 1 month
Reviewed by: kib
Differential revision: https://reviews.freebsd.org/D11912
|
| H A D | madt.c | diff 84525e55c1cda9ca873094342410f3bd22d983b4 Thu Aug 10 11:16:03 CEST 2017 Roger Pau Monné <royger@FreeBSD.org> x86: make the arrays that depend on MAX_APIC_ID dynamic
So that MAX_APIC_ID can be bumped without wasting memory.
Note that the usage of MAX_APIC_ID in the SRAT parsing forces the
parser to allocate memory directly from the phys_avail physical memory
array, which is not the best approach probably, but I haven't found
any other way to allocate memory so early in boot. This memory is not
returned to the system afterwards, but at least it's sized according
to the maximum APIC ID found in the MADT table.
Sponsored by: Citrix Systems R&D
MFC after: 1 month
Reviewed by: kib
Differential revision: https://reviews.freebsd.org/D11912
|
| /freebsd/sys/x86/x86/ |
| H A D | mp_x86.c | diff 84525e55c1cda9ca873094342410f3bd22d983b4 Thu Aug 10 11:16:03 CEST 2017 Roger Pau Monné <royger@FreeBSD.org> x86: make the arrays that depend on MAX_APIC_ID dynamic
So that MAX_APIC_ID can be bumped without wasting memory.
Note that the usage of MAX_APIC_ID in the SRAT parsing forces the
parser to allocate memory directly from the phys_avail physical memory
array, which is not the best approach probably, but I haven't found
any other way to allocate memory so early in boot. This memory is not
returned to the system afterwards, but at least it's sized according
to the maximum APIC ID found in the MADT table.
Sponsored by: Citrix Systems R&D
MFC after: 1 month
Reviewed by: kib
Differential revision: https://reviews.freebsd.org/D11912
|
| H A D | local_apic.c | diff 84525e55c1cda9ca873094342410f3bd22d983b4 Thu Aug 10 11:16:03 CEST 2017 Roger Pau Monné <royger@FreeBSD.org> x86: make the arrays that depend on MAX_APIC_ID dynamic
So that MAX_APIC_ID can be bumped without wasting memory.
Note that the usage of MAX_APIC_ID in the SRAT parsing forces the
parser to allocate memory directly from the phys_avail physical memory
array, which is not the best approach probably, but I haven't found
any other way to allocate memory so early in boot. This memory is not
returned to the system afterwards, but at least it's sized according
to the maximum APIC ID found in the MADT table.
Sponsored by: Citrix Systems R&D
MFC after: 1 month
Reviewed by: kib
Differential revision: https://reviews.freebsd.org/D11912
|