christoph/interrupt-handling-using-the-x86-apic
1
Fork 0
Code Actions Activity

Sync with BSuSP

Browse Source
This commit is contained in:
Christoph Urlacher
2023-03-02 22:10:11 +01:00
parent daf0161df5
commit 9a62332d70
4 changed files with 8 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
chap/figures.tex
View File

@ -1,7 +1,9 @@
\chapter{Figures}
\label{ch:figures}
\begin{figure}[h]
\clearpage
\begin{figure}[H]
\centering
\begin{subfigure}[b]{0.85\textwidth}
\includesvg[width=1.0\linewidth]{diagrams/apic_enable_seq.svg}
@ -10,7 +12,7 @@
\label{fig:apicenable}
\end{figure}
\begin{figure}[h]
\begin{figure}[H]
\centering
\begin{subfigure}[b]{0.85\textwidth}
\includesvg[width=1.0\linewidth]{diagrams/apic_smp_enable_seq.svg}

4
chap/verification.tex
View File

@ -38,7 +38,7 @@ Specifically, QEMU provides the current register state of all local and I/O APIC
\end{itemize}
Although hhuOS is developed mainly for learning purposes, every OS' core task remains to be the management of computer hardware.
For this reason, this implementation was additionally tested on a \textquote{ThinkPad T60s} with an Intel \textquote{Core 2 Duo} processor.
For this reason, this implementation was additionally tested on a \textquote{ThinkPad X60s} with an Intel \textquote{Core 2 Duo} processor.
By providing internal status data through the virtual file system, implemented features (including booting additional APs) were verified on this very specific set of hardware.
More specifically, information about detected and enabled local APICs and the I/O APIC, register values from the BSP's LVT and the REDTBL, the contents of the PIC's \textbf{\gls{imr}}, and the number of occurred interrupts by core (similar to \code{/proc/interrupts} in Linux~\autocite{linux}) are exposed on the path \code{/device/apic/}.
@ -54,7 +54,7 @@ This way, the following things could be verified on real hardware:
Interestingly, this was easier to verify on real hardware than in QEMU, because QEMU usually instantly crashes when interrupts are enabled on an AP beside the BSP\@.
Also, redirecting the keyboard interrupt in QEMU significantly changes the behavior of any key press and renders the keyboard unusable.
This is expected, as hhuOS' paging is not designed for multiple processors.
On the ThinkPad T60s though, it was possible (surprisingly) to use the redirected keyboard interrupt to \code{cat} the \code{/device/apic/irqs} file to observe the interrupt statistics, which showed the keyboard interrupts indeed arriving at a different core than the BSP\@.
On the ThinkPad X60s though, it was possible (surprisingly) to use the redirected keyboard interrupt to \code{cat} the \code{/device/apic/irqs} file to observe the interrupt statistics, which showed the keyboard interrupts indeed arriving at a different core than the BSP\@.
After a certain time, the system crashes on the ThinkPad as well.}.
\end{itemize}