OSDev.org

I personally think this category, and all the pages within this category, can be deleted. As Solar says on the talk page, this is already very well done by Intel and AMD already. I'd like to get a few opinions if I could.

JackScott wrote:I personally think this category, and all the pages within this category, can be deleted. As Solar says on the talk page, this is already very well done by Intel and AMD already. I'd like to get a few opinions if I could.

I agree. But then again, my opinions are usually deemed worthless (for good reason: I think that about 80% of the Wiki can be deleted because of sheer uselessness).


JAL

I agree with JS too - I think that where instructions are important, they should be documented within a topic. For example: the INVLPG instruction should be documented as part of the text of the Paging topic.

Why instructions like MOV and CLI are there at all is a complete mystery. I say go ahead and delete

Cheers,
Adam

Fourthdeded.

post++;

CLI/STI, MOV, XCHG, INT: delete +1

INVLPG and some general theory about TLBs should be merged into Paging

CPUID however should IMO be kept - Its more general than any of the manuals (as it has information from all of them and more)

CLI, STI, MOV, INT and XCHG have been deleted. Later on I'll edit CPUID and merge INVLPG into Paging, if nobody gets there first.

JackScott wrote:Later on I'll edit CPUID and merge INVLPG into Paging, if nobody gets there first.

I've merged INVLPG into Paging and took Category:X86 Instructions out of CPUID. Also, in the "Page Table" section of Paging, can we move the diagram to the right so that the NASM example isn't shoved over to practically the middle of the page (on a 1440x900 screen)?