Correct markdown
ステータスチェックはすべて成功しました
ci/woodpecker/push/build Pipeline was successful

このコミットが含まれているのは:
Rafal Kupiec 2023-01-26 16:55:34 +01:00
コミット 6613fdd32c
署名者: belliash
GPGキーID: 4E829243E0CFE6B4
2個のファイルの変更10行の追加9行の削除

ファイルの表示

@ -1,8 +1,8 @@
# ExectOS Ideas
This is a list of ideas that migh but not must be realized.
[ ] Move processor context initialization (GDT, IDT, LDT, PCR, TSS) from XTLDR to XTOSKRNL to simplify the XTOS boot
protocol.
[ ] Rewrite memory mapping and paging support in bootloader to make it more flexible and architecture independent.
This should support paging levels, thus allowing to make a use of PML5 on modern AMD64 processors and increasing
the addressable virtual memory from 256TB to 128PB.
- [ ] Move processor context initialization (GDT, IDT, LDT, PCR, TSS) from XTLDR to XTOSKRNL to simplify the XTOS boot
protocol.
- [ ] Rewrite memory mapping and paging support in bootloader to make it more flexible and architecture independent.
This should support paging levels, thus allowing to make a use of PML5 on modern AMD64 processors and increasing
the addressable virtual memory from 256TB to 128PB.

ファイルの表示

@ -2,7 +2,8 @@
This is a list of well known bugs that exists in all master branch builds.
## XTLDR
[ ] In some specific scenarios (most probably EFI by Insyde) XTLDR cannot load modules. Calling BootServices->LoadImage()
fails with STATUS_EFI_NOT_FOUND status code. Possibly this is a bug in BlFindVolumeDevicePath() routine.
[ ] EFI Runtime Services are not mapped properly into higher half. They are mapped itself, but all pointers inside that
structure point to some physical address that is unavailable after paging is enabled.
- [ ] In some specific scenarios (most probably EFI by Insyde) XTLDR cannot load modules. Calling the EFI's
BootServices->LoadImage() fails with STATUS_EFI_NOT_FOUND (0x800000000000000E) status code. Possibly this is
a bug in BlFindVolumeDevicePath() routine.
- [ ] EFI Runtime Services are not mapped properly into higher half. They are mapped itself, but all pointers inside
that structure point to some physical address that is unavailable after paging is enabled.