IA32-doc

IA32-doc is a project which aims to put as many definitions from the Intel Manual into machine-processable format (in this case: yaml) as possible.

Why?

Because such thing, as far as I know, does not exist. You can try to cherry-pick definitions from Linux source code, ReactOS, VirtualBox source code or EDK-II source code, but you can expect limited set of definitions which are often poorly documented as a bonus.

What is this good for?

For this. For your hobby OS. For your hobby hypervisor. For your experiments with APIC, various MSRs, SGX, performance counters, you name it.

Usage

$ python3 main.py -c conf/default.yml -f yaml/Intel/index.yml

FAQ

Are there definitions for 32-bit or 64-bit CPU?

Hopefully, both.

Are there definitions for AMD-specific stuff?

No, just Intel-specific stuff.

What sources did you use?

Mainly: Intel® 64 and IA-32 architectures software developer’s manual combined volumes: 1, 2A, 2B, 2C, 2D, 3A, 3B, 3C, 3D, and 4 (May 2018).

I've also took inspiration of various names/descriptions from other projects (VirtualBox, TianoCore).

Is any other output than C-header available?

No. Although, it shouldn't be that hard to extend the Python code to generate source code in other programming languages.

What Python packages do I need?

Just PyYAML. And Python >= 3.7.

Who is going to maintain it?

Nobody. Maybe miracle happens and someone (or group of people) decide to fork this repo and maintain it. Don't expect me to keep up with each release of Intel Manual, though. Although I may add whatever I'm interested into at any moment.

What's in there?

Look into yaml/Intel directory. Currently there are transcribed:

• Control registers (CR0, CR3, CR4, CR8)
• CPUID for every EAX/ECX function found in current Intel Manual
• MSRs (Model Specific Registers)
• Paging related stuff (PML4E/PDPTE/PDE/PTE, both 32/64 bit)
• Segment descriptors (GDT/LDT/IDT/TSS)
• VMX-related definitions (EPT/VMCS)
• APIC
• EFLAGS
• Memory types (UC/WC/WT/WP/WB)

I don't like the use of UINT*/CamelCase/Doxygen, what should I do?

To change naming of integers, change int_type_* values in conf/default.yml.

To change anything related to the output file, you have to modify DocCProcessor class.

To create new "yaml document processor" (e.g. for Rust), derive DocProcessor class.

I'd like to add new yaml definitions, what should I do?

Look at yaml/template.yml to better understand the format. Also, by looking at other yaml files, you should get the idea.

Notes and remarks

• First of all - at the end of the day, you should ALWAYS consult the holy Intel Manual anyway. Unconditionally. Seriously, once you get past Hello world and decide to write your OS or hypervisor, there is no way you'll succeed without reading Intel Manual.
• There may be errors, typos, copy-paste errors in these yaml transcriptions.
• I'm aware that there is lot of stuff missing here. I've mainly tried to transcribe what I personally desired.

TODO

• ? OriginalNames - preserve case-sensitivity (BIOS, x2APIC, ToPA, ...)
• ? Possibility to split into multiple .h
• ?? Add doxygen main page
• ??? Add AMD
• Find what else is missing
• Fix 32/64 bitfields for MSR registers
• Add possibility for bitfields to have both UINT32/UINT64 members
• Add CPUID subleaf definitions

License

All the code in this repository is open-source under the MIT license. see the LICENSE.txt file in this repository.

If you find this project interesting, you can buy me a coffee

  BTC 3GwZMNGvLCZMi7mjL8K6iyj6qGbhkVMNMF
  LTC MQn5YC7bZd4KSsaj8snSg4TetmdKDkeCYk