TheCatgirls: TheCatgirls moved page Apic to APIC: Uppercase :)

2024-12-21T07:00:41Z

TheCatgirls moved page Apic to APIC: Uppercase :)

← Older revision

Revision as of 07:00, 21 December 2024

Caitcatto: Added Starter for APIC page.

2024-12-19T20:40:15Z

Added Starter for APIC page.

New page

==LAPIC and IOAPIC==

The Advanced Programmable Interrupter Controller(APIC) is a interrupt controller designed to replace the 8529 Intel programmable interrupt controller(PIC) that had been standard up until this point. The reason for this replacement was two fold. Multiprocessor systems where becoming more common and the old PIC was unable to control which CPU cores would be sent interrupts, Along with the APIC being capable of sending Inter-Processor-Interrupts(IPI).

This allowed for OS's to have more fine grained control over their interrupts and allowed for better hardware delegation of interrupts allowing certain CPU cores to handle certain interrupts. The design of the APIC is simple really it's split into two pieces the Local APIC(LAPIC) and the IOAPIC. With each LAPIC and IOAPIC having an ID number on their dedicated APIC bus.

The Local APIC is a CPU core local interrupt controller, each CPU core has it's own LAPIC, these can handle their own timer interrupts and external Hardware Interrupts that are sent via the IOAPIC. The IOAPIC on the other hand is connected to external devices([[PIT]],[[HPET]],[[PS/2]] Controller, etc...) and through the use of redirection tables it can be programmed with a LAPIC ID in each Interrupt redirection table entry. This ID controls which LAPIC and thus which core will service this hardware interrupt. It is quite common for a system to have one IOAPIC however plenty of systems may two or more IOAPICs you should parse the MP tables or the [[ACPI]] [[MADT]] table to ensure all IOAPICs are found.

===Please Note===
The MP specification is an old spec and though it will contain the information needed for the IOAPIC and LAPIC. It may not be present on newer systems and the ACPI tables should be preferred over the MP spec wherever possible.

==LAPIC==
Support for the local APIC can be queried using two different methods. One would be using CPUID <code>EDX=0x00000001</code>. Or you could parse the [[MP Tables]] or the [[ACPI]] [[MADT]] table(Which you would likely want to do anyway for SMP). You could also check the APIC Base MSR and assume if those exist that the LAPIC is present at the "default" physical address of <code>0xfee00000</code>. However the best way would be to check the CPUID, then parse the [[MP Tables|MP]] or the ACPI [[MADT]] table to determine both the if APIC is supported and get the LAPIC Physical address from the [[MP Tables|MP]]/[[MADT]] Table. If you wish to double check this base address you can also check the APIC Base MSR(`0x1b`).

===Register Layout===

TODO:

==IOAPIC==
The IOAPIC can be queried in multiple different ways one is to assume that if the LAPIC exists that at least one IOAPIC exists at the "default" physical address of <code>0xfec00000</code>. However again this isn't ideal and you should attempt to parse either the [[MP Tables]] or the [[ACPI]] [[MADT]] Tables. To Ensure you have the correct physical addresses and have found all IOAPICs in this system.

===Register Layout===
todo:
{| class="wikitable"
|+
|}

== Programming LAPIC/IOAPIC ==
When Programming these devices their memory addresses should always be marked as non-cacheable to ensure proper operation of the devices as caching them could produce strange and undesired results due to cached values being read rather than the actual true values of the MMIO registers. In the below code we are also going to assume that everything is at it's "default" standard physical address in memory and that if paging is active it's just a simple identity map paging i.e. Virtual Address = Physical Address.

In your kernel you are going to want to parse ACPI structures and map these physical addresses in a way that makes sense for your [[VMM]].

=== IOAPIC: ===
Below is an example of programming the IOAPIC to route GSI 2 typically ISA IRQ 0(PIT Timer) to CPU 0 with the interrupt vector set to <code>0x20</code> this is because the IOAPIC operates on register select and window model of programming meaning that <code>base + 0</code> = the register to select. and <code>base + 0x10</code> = the selected register.

Each Interrupt redirection entry is split into two 32bit registers. The lower bits contains data such as which IDT vector will be called for this interrupt, polarity, delivery mode, edge or level triggered, masked, etc...

While the upper 32bits contain the the LAPIC ID that this interrupt will be sent to. Depending on the setting of bit 11 of the lower 32bit. See <syntaxhighlight lang="c">
void ioapic_init() {
volatile uint32_t *ioapic = (uint32_t*)0xfec00000;
/*Timer Interrupt for QEMU*/
base[0] = 0x14; /*GSI Interrupt 2 Most commonly PIT/HPET timer*/
base[4] = 0x20; /*Interrupt Vector i.e. IDT vector 0x20 will be called for this*/
base[0] = 0x14; /*GSI Interrupt 2 upper 32bit*/
base[4] = 0x00;
}
</syntaxhighlight>

==Links==
[https://pdos.csail.mit.edu/6.828/2016/readings/ia32/ioapic.pdf IOAPIC datasheet from MIT.edu]

[https://uefi.org/sites/default/files/resources/ACPI%20Spec%206%205%20Aug29.pdf ACPI Spec]

[https://pdos.csail.mit.edu/6.828/2018/readings/ia32/MPspec.pdf MPspec Datasheet from MIT.edu]

[https://cdrdv2.intel.com/v1/dl/getContent/671200 Intel SDM Full(Volume 3 chapter 12 for APIC Documentation)]

[https://www.amd.com/content/dam/amd/en/documents/processor-tech-docs/programmer-references/40332.pdf AMD SDM(Volume 2 chapter 16 for APIC Documentation)]

APIC - Revision history

TheCatgirls: TheCatgirls moved page Apic to APIC: Uppercase :)

Caitcatto: Added Starter for APIC page.