x86_64
                                
                                 x86_64 copied to clipboard
                                
                                    x86_64 copied to clipboard
                            
                            
                            
                        Library to program x86_64 hardware.
There is a divergence in confidential computing technology for AMD's SEV-SNP system (AMD's original https://github.com/AMDESE/linux-svsm, SUSE's COCONUT https://github.com/coconut-svsm/svsm) due to issues claimed by SUSE engineers that I wanted to bring...
…t on stable rust.
I would like the ability to create a GlobalDescriptorTable with a const fn. I am writing a kernel and need to ensure that no 64-bit code runs before I jump...
This PR fixes some warnings that are currently blocking CI.
Add a way to clear page table entries that don't have the present flag set. See #481 for an explanation fixes: #481
I'm playing around with adding guard pages to my kernel. The idea is that I add a guard page, before and after used pages to catch buffer overflows, etc. I'd...
> > > > I noticed that `unmap` and now `clear` are both safe functions. Shouldn't they be marked as unsafe? After all using `unmap` or `clear` can invalidate any...
There is currently no way to create an instance of idt::ExceptionVector having an interrupt number. At the same time it would be convenient for the user to use this enum...
rustc is phasing out allowing the "x86-interrupt" ABI on non-x86 targets. Using "x86-interrupt" on a non-x86 target currently causes a warning, but this will become a hard error in a...