klange changed the topic of #osdev to: Operating System Development || Don't ask to ask---just ask! || For 3+ LoC, use a pastebin (for example https://gist.github.com/) || Stats + Old logs: http://osdev-logs.qzx.com New Logs: https://libera.irclog.whitequark.org/osdev || Visit https://wiki.osdev.org and https://forum.osdev.org || Books: https://wiki.osdev.org/Books
mahmutov has quit [Ping timeout: 272 seconds]
Arthuria has quit [Ping timeout: 244 seconds]
<geist> interesting, was just reading some benchmarks re: freebsd 13 which was just released
<geist> apparently it's a big boost
<geist> must have really fixed some doozies in there
<geist> ugh, the -Wstringop-overflow in gcc 11 is really annoying
Arthuria has joined #osdev
<geist> in this case i want to memset a region of memory that i just have a pointer to
Arthuria has quit [Read error: Connection reset by peer]
<geist> ie, memset((void *)0x1234, 0, 1024); and it's basically 'nope you have gone outside the bounds of a 0 length destination'
<geist> uh?
Arthuria has joined #osdev
<geist> app/loader/loader.c:53:5: error: ‘memset’ offset [0, 524287] is out of the bounds [0, 0] [-Werror=array-bounds]
<geist> 53 | memset(DOWNLOAD_BASE, 0, DOWNLOAD_SLOT_SIZE);
<geist> soooo. okay, yeah i get it, that's kinda dangerous, but get off my back i know what i'm doing
<gog> nanny compiler
Arthuria has quit [Read error: Connection reset by peer]
<doug16k> why does it think it is 0, 0 ?
<clever> doug16k: i think `void*` is considered an array of zero length?
<geist> doug16k: i dont know where it's supposed to get the length from in this case
<geist> well shoving it through a unsigned char doesn't really help
<geist> it still thinks it's a region of size 0
<doug16k> it wants (char(*)[1024]) then?
<geist> i dunno! i haven't figured out how to stop it
<klange> < clever> my rough understanding of AA, is to just render at 2x the normal res then blend each 2x2 pixel block back down to 1 pixel, is that right? ← In this case, I'm taking a very different approach than subsampling; with simple edge polygons you can know exactly where they cross a given scanline and use that to get much better values
<klange> this seems to be the typical approach for font glyphs
<geist> huh the #pragma GCC diagnostic stuff doesn't even stop this
<geist> ugh.
<doug16k> I'd cast it to an array that size
<geist> i can kill it at the module level by turning off the warning but this is annoying
<doug16k> it's probably __attribute__((__access__((__write_only__, 1, 3))) on memset doing it
<geist> yah going through a pointer doesn't silence it either
<geist> it's part of some new feature in 11 i think that's trying to dynamically track the size of things you're pointing at
<doug16k> cast to array you mean
<doug16k> is it easy to repro in godbolt?
<geist> yah i cast it to a 'unsigned char (*foo)[1024] = myptr;' and then memset that
<geist> same thing
<doug16k> microsoft compiler has been doing that for about 15 years now
<doug16k> mostly for security
<doug16k> their code is full of ugly macros that annotate every buffer bounds
<geist> oh also it explicitly shows up at higher optimization levels
<geist> it mentions that it's a result of object size tracking
netbsduser` has quit [Ping timeout: 258 seconds]
<geist> also feeding it through a global constant does it too: https://gcc.godbolt.org/z/WjrjzjEsn
<geist> (switched to C because that's the language i'm using here)
<geist> eep, gotta go. will be back in a few hours
Burgundy has left #osdev [#osdev]
silverwhitefish has quit [Quit: One for all, all for One (2 Corinthians 5)]
<doug16k> yeah, wow
<moon-child> geist: I did a 'nowarn' macro to just shut up the compiler whenever it pulls shit like that
<moon-child> nowarn(...) _Pragma("gcc diagnostic push") _Pragma("gcc diagnostic ignored \"-Wwhatever\"") stuff _Pragma("gcc diagnostic pop")
<doug16k> tricked it with disgusting hack: https://gcc.godbolt.org/z/xbh1fPvq7
<kingoffrance> "compiler pulls shit" -> "talk to the pragma" lol
tacco has quit []
<doug16k> I just hit the code analyzer over the head with something I am allowed to do because the language is designed to maximize memory corruption
<moon-child> haha
<doug16k> could it be argued that your define is wrong, and it should be BUFFER = 0x1000; in your linker script, and the code should say char BUFFER[] ?
<doug16k> er, extern *
<doug16k> you could make one of your source files a linker script, with just this line: BUFFER = 0x1000;
<doug16k> and treat it like an object file
mctpyt has quit [Quit: me voy yendo]
<doug16k> I think BUFFER = ABSOLUTE(0x1000); will make it not generate relocations for it
mctpyt has joined #osdev
<doug16k> hardcoded addresses belong in the link, don't you think?
Sos has quit [Quit: Leaving]
pretty_dumm_guy has joined #osdev
chartreuse has quit [Ping timeout: 258 seconds]
jeaye is now known as not-a-bot
not-a-bot is now known as jeaye
pretty_dumm_guy has quit [Quit: WeeChat 3.3-dev]
gog has quit [Ping timeout: 265 seconds]
jjuran has joined #osdev
jjuran has quit [Remote host closed the connection]
jjuran has joined #osdev
sts-q has quit [Ping timeout: 272 seconds]
sts-q has joined #osdev
skipwich has quit [Ping timeout: 258 seconds]
zoey has quit [Quit: Leaving]
ElectronApps has joined #osdev
<doug16k> hmm I guess that could cause problems with reach
<moon-child> imo hardcoded addresses belong near the code that uses them. Otherwise it's kinda opaque
<doug16k> the more I learn about toolchains, the more I am annoyed with them
<klange> write your own
<moon-child> I wrote most of an assembler, probably do linker next
<moon-child> also most of a compiler. But register allocation and instruction selection are a pita
<klange> I have most of a linker, and do plan to eventually write a C compiler similar to some of the other minimalist ones out there...
srjek_ has quit [Ping timeout: 272 seconds]
<moon-child> ye my mistake with the compiler was trying to go fancy. Have all this ssa and now you _have_ to do register allocation or it turns into kilobytes of stack space for a 5 line function
<moon-child> I did it the second way, does not work
Geertiebear has quit [Ping timeout: 272 seconds]
GeDaMo has joined #osdev
<geist> doug16k: interesting
<geist> moon-child: for soem reason that pragma thing doesn't work here
<geist> sadly it's actually more complicated in my code base, the BUFFER #define is machine/platform specific, etc
<geist> so it's harder to do
<moon-child> at the call site, not the definition. Like nowarn(memset(...))
<moon-child> https://0x0.st/-p9o.txt full def
silverwhitefish has joined #osdev
Izem has joined #osdev
vai has joined #osdev
<bslsk05> ​www.vunetfinland.com: Russian Market News | Virtualization Information Technology Start Up JTMOS Is Looking For Investors, Expanding To Russia And China - Bid Today!
<Izem> good luck
<doug16k> interesting. 11263 fps to render 3 white triangles into 640x480 window
<doug16k> sdl
<doug16k> opengl
<doug16k> ~80 microseconds per frame lol
<moon-child> jesus
<moon-child> that's 40gb/s
<doug16k> 2060 super
<moon-child> gddr is wiiild
<doug16k> yeah
<bslsk05> ​rampantgames.com: Black Triangles
<geist> though really 40GB/sec isn't much to graphics ram
<doug16k> it's the same amount of time per frame if I just clear the screen and draw zero triangles
<doug16k> the triangles are free up to a certain point
<klange> my triangles are white
<moon-child> I expect it takes very little time to get to that point though :P
<klange> which... in retrospect was a silly idea anyway, as I'm working up to text which is generally black on white...
<moon-child> no love for the rainbow triangles?
<moon-child> https://0x0.st/-p9e.png classic
<doug16k> is that a clockwise triangle?
<moon-child> klange: if you can't render rainbows, how will you do subpixel antialiasing on your text? ;o
<doug16k> I wonder what the front face of that rainbow triangle looks like :P
<moon-child> doug16k: ccw
<doug16k> the order isn't red green blue?
<moon-child> but I think usually I switch the winding mode
<doug16k> ah
<doug16k> I am brainwashed that ccw is front face :D
<moon-child> doug16k: nope, bgr
<moon-child> :P
<doug16k> looks good
<klange> yeah, just need to actually draw something real with it instead of messing around with with a mouse
<doug16k> you need to render polygons with some segments being bezier curves, right?
<klange> A typical approach is to tesselate the curves to lines by calculating midpoints and comparing to the midpoint of a line segment, tesselating until a threshold - half a pixel or so.
<doug16k> ah
<klange> But I think I'll start doing some ttf parsing first and see where that takes me...
<klange> thinking of calling this library the toaru truetype text transformer
<klange> or ttttt
mahmutov has joined #osdev
pg12 has quit [Ping timeout: 244 seconds]
pg12 has joined #osdev
Izem has quit [Quit: Connection closed]
tenshi has joined #osdev
scaleww has joined #osdev
pg12 has quit [Ping timeout: 252 seconds]
sortie has joined #osdev
dennis95 has joined #osdev
asymptotically has joined #osdev
<FireFly> or t5 for short? :p
mniip has quit [*.net *.split]
Patater has quit [*.net *.split]
meisaka has quit [*.net *.split]
f11 has joined #osdev
Yukara has joined #osdev
mniip_ has joined #osdev
Patater has joined #osdev
netbsduser` has joined #osdev
me__ has joined #osdev
netbsduser` has quit [Ping timeout: 272 seconds]
<doug16k> klange, you could add the word "tiny" and add another t
<doug16k> toaru tiny truetype text transformer
<moon-child> also do true type as two separate words
<moon-child> then you get 7 ts
<doug16k> I'm guessing your implementation will be surprisingly low line count
<GeDaMo> If will if you put all the code on one line :P
<klange> truetype was already two separate words Toaru TrueType Text Transformer = TTTTT
<moon-child> oh, then add 'the' to the beginning
<GeDaMo> Tremendous! :P
<moon-child> tremendous and tiny? Sounds a bit oxymoronic :)
<GeDaMo> Tremendously tiny :P
mniip_ is now known as mniip
tacco has joined #osdev
mahmutov has quit [Ping timeout: 244 seconds]
mahmutov has joined #osdev
me__ has quit [Ping timeout: 272 seconds]
scaleww has quit [Remote host closed the connection]
f11 has quit [Ping timeout: 268 seconds]
f11 has joined #osdev
pretty_dumm_guy has joined #osdev
ElectronApps has quit [Read error: Connection reset by peer]
ElectronApps has joined #osdev
ElectronApps has quit [Read error: Connection reset by peer]
ElectronApps has joined #osdev
mahmutov has quit [Ping timeout: 272 seconds]
Arthuria has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
f11 has quit [Ping timeout: 272 seconds]
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
f11 has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
f11 has quit [Quit: WeeChat 3.2]
mahmutov has joined #osdev
vdamewood has joined #osdev
gog has joined #osdev
me__ has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
<klange> Well, I did next to nothing with this today... just cleaned up what I already had, hopefully optimized it a bit, made sure it worked with colors and alpha blending...
<klange> ... in theory.
<klange> But I'm sure it'll occupy my evenings for the next few days. And probably my lunches.
<sortie> Today I merged the ATAPI support I did three years ago
<klange> I should probably at least get my old ATA/ATAPI drivers ported to Misaka since they're not too complicated...
shiroyasha has joined #osdev
vdamewood has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
isaacwoods has joined #osdev
vai has quit [Remote host closed the connection]
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
dormito has quit [Quit: WeeChat 3.1]
skipwich has joined #osdev
dormito has joined #osdev
vdamewood has joined #osdev
tacco has quit []
dutch has quit [Quit: WeeChat 3.0.1]
dutch has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
srjek_ has joined #osdev
mahmutov has quit [Read error: No route to host]
janemba has quit [Read error: Connection reset by peer]
janemba has joined #osdev
Deledrius has joined #osdev
ElectronApps has quit [Read error: Connection reset by peer]
Deledrius has left #osdev [Net.LinkToMyPersonalAge]
pg12 has joined #osdev
pg12 has quit [Remote host closed the connection]
zoey has joined #osdev
me__ has quit [Ping timeout: 268 seconds]
freakazoid333 has quit [Read error: Connection reset by peer]
pg12 has joined #osdev
Mooncairn has joined #osdev
freakazoid333 has joined #osdev
pretty_dumm_guy has quit [Quit: WeeChat 3.3-dev]
me__ has joined #osdev
vdamewood has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
vdamewood has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
dennis95 has quit [Ping timeout: 244 seconds]
dennis95 has joined #osdev
tacco has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
thinkpol has quit [Remote host closed the connection]
thinkpol has joined #osdev
vai has joined #osdev
vai has quit [Remote host closed the connection]
gmacd has joined #osdev
scaleww has joined #osdev
mahmutov has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
Matt|home has quit [Ping timeout: 265 seconds]
me__ is now known as JX7P`
nyah has joined #osdev
gmacd has quit [Read error: Connection reset by peer]
rodr has joined #osdev
mahmutov has quit [Ping timeout: 272 seconds]
mahmutov has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
Matt|home has joined #osdev
tenshi has quit [Quit: WeeChat 3.2]
rodr has quit [Quit: rodr]
vdamewood has quit [Read error: Connection reset by peer]
vdamewood has joined #osdev
dennis95 has quit [Quit: Leaving]
sortie has quit [Quit: Leaving]
GeDaMo has quit [Quit: Leaving.]
asymptotically has quit [Quit: Leaving]
<ZetItUp> https://gyazo.com/f326b15f24dc8d07ffd814a5deeb504f pretty happy with how far i've come :D
<bslsk05> ​gyazo.com: Screen capture - f326b15f24dc8d07ffd814a5deeb504f - Gyazo
<j`ey> ZetItUp: v cool!
<ZetItUp> not the most useful thing but w/e :D
<j`ey> very complex clock
<gog> neat :)
<ZetItUp> yeah the time was pretty hard, borrowed alot of code :P
<ZetItUp> and cheated with the shutdown since it's running in qemu
fconti has quit [Remote host closed the connection]
fconti has joined #osdev
fconti has quit [Remote host closed the connection]
fconti has joined #osdev
mahmutov has quit [Read error: No route to host]
mahmutov has joined #osdev
fconti has quit [Remote host closed the connection]
fconti has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
fconti has quit [Remote host closed the connection]
Arthuria has joined #osdev
isaacwoods has quit [Quit: WeeChat 3.2]
aquijoule_ has quit [Remote host closed the connection]
Arthuria has quit [Ping timeout: 272 seconds]
immibis has quit [Ping timeout: 272 seconds]
<NieDzejkob> is there a way to make use of BIOS disk access through trips back to real mode if I'm running in long mode?
<clever> NieDzejkob: i think win95 was doing just that, it could basically do a soft-reboot to get back into real real mode, restore some state, call the bios routine, then go back into paged mode
<clever> and thats why realmode drivers sucked, and it was recommended to get proper paging capable drivers
<gog> you could do PIO
<gog> unless there's a specific need to use the BIOS service
<NieDzejkob> well I'm using USB, I don't think there's an equivalent of PIO for that :D
<gog> ah yes that's fair lol
<NieDzejkob> clever: I don't think win95 was using long mode :P
<clever> yeah, it was using a 32bit protected mode
<gog> windows 95 x64 edition
<clever> in that case, you would have to tell the bios to stop doing usb/ata emulation, and then run your own usb drivers
<clever> and there at least 4 different usb drivers you have to deal with
<clever> ehci, ohci, xhci, and i forget
<NieDzejkob> usb/ata emulation is a thing? as in SMM port mitming emulation?
<clever> NieDzejkob: its done via the bios disk read api
<clever> so as long as you ask the bios to read the internal hdd, it can fake a drive being internal
<clever> ipxe can also hijack those routines, and make a network block device appear internal
<NieDzejkob> and there's no way to go long mode -> protected mode -> real mode -> protected mode -> long mode?
<doug16k> sure you can
<NieDzejkob> not expecting great performance or anything, just as a stopgap
<clever> i had heard that dropping back to realmode wasnt really possible, you could only hit the main cpu reset line
<doug16k> clever, wrong
<doug16k> on 80286
<clever> and then leave an entry point somewhere in ram, for the bios to return control to you
<doug16k> dude
<NieDzejkob> yeah, I've already done PM -> RM -> PM before
<clever> doug16k: ahh, a lot of these things ive heard, have long been fixed then
<NieDzejkob> it requires >=386 IIRC but tbh idgaf
<doug16k> yeah, intel thought protected mode was so good, you'd stay in it forever, and thought it would be really secure to make it stuck in pmode
<doug16k> the idiot 80286 team
<clever> and then the 386 team fixed that?
<doug16k> yes
<clever> i can kinda see similar choices done on arm, but better, with EL2/EL1
<doug16k> LMSW instruction can't clear PE
<doug16k> mov to CR0 can
<clever> once in EL1, your basically stuck, and can only regain EL2 if the code in EL2 co-operates
<doug16k> NieDzejkob, all you need to do on top of the pm->rm->pm is make the long mode code far jump to a code segment that has L=0, D=1, then turn off paging, then turn off LME, now you are in protected mode
<j`ey> clever: just do a HVC, then youre in EL2 :P
<NieDzejkob> what about interrupt setup?
<NieDzejkob> do BIOSes usually make assumptions about that?
<NieDzejkob> wrt. disk access
<clever> j`ey: but if EL2 isnt co-operating, you cant do anything useful via HVC, so it can lock you in EL1, or treat HVC as fatal
gog has quit [Quit: bye]
<doug16k> you know what is the most funny about the inability of 80286 to get out of protected mode? IBM foolishly added hardware to the motherboard to make the keyboard controller able to reset the cpu
<j`ey> clever: :)
<doug16k> this is all they needed: mov $ 1,%sp ; push $ 1
<doug16k> ^ resets cpu
<NieDzejkob> uhhhh what
<doug16k> triple fault
<doug16k> even works in real mode
<NieDzejkob> hah, do faults happen in real mode too?
<doug16k> only some
<doug16k> undefined opcode, divide error obviously, right?
<clever> doug16k: i heard something about the original xbox cpu, was changed at one point in the design, and that impacted how it behaved in tripple-fault cases
<NieDzejkob> but stack pointer rolling over includes those?
<doug16k> and there is an into instruction to raise that. and eflags.TF exists, and 0xcc breakpoint opcode
manawyrm has quit [Quit: Read error: 2.99792458 x 10^8 meters/second (Excessive speed of light)]
<doug16k> NieDzejkob, stack pointer can't wrap since 80286
scaleww has quit [Quit: Leaving]
<NieDzejkob> and it raises a stack fault instead?
<doug16k> it's a stack fault. it tries to push the frame. that causes double fault, that can't push, resets
manawyrm has joined #osdev
<doug16k> only in protected mode is it possible to escape the reset
<doug16k> in protected mode, the cpu interprets the IDT completely differently. in that case, a task gate could make it switch to a new stack
<doug16k> in real mode, it isn't possible to prevent the triple fault
<NieDzejkob> are task gates typically used for interrupt handling, then, or do you just use the ESP0 in TSS?
<doug16k> PE does two things: changes the meaning of loading a value into a segment register, changes the format of the IDT entries
<doug16k> that's about it
<NieDzejkob> also, what's the point of LMSW if mov to cr0 exists? was the latter added in 386 or something?
<doug16k> the task gate solves it because it will save the nonsensical ss:sp to the main TSS, and switch to the ss:sp in the other task
<doug16k> yeah, lmsw was the way to enable pmode on 286. 386 added control registers, and made cr0 take over what lmsw did
<doug16k> lmsw still works, but it still won't let you clear PE with it
<NieDzejkob> compatibility I guess :P
<NieDzejkob> someone may've tried setting the other bits with a word that has PE=0
<doug16k> yeah, some code might rely on exceptions to occur. they expect and rely on it
<doug16k> lmsw = load machine status word
<NieDzejkob> yeah, looked that up already. though I initially confused it with wrmsr
<doug16k> 286 was how the idt and gdt entries ended up in the mess layout they are in now
CryptoDavid has joined #osdev
CryptoDavid has quit [Excess Flood]
<doug16k> it was as if the 286 team expected to just toss the whole thing on 32 bit cpu
<NieDzejkob> oh I only now realized that 286 was the one with 16-bit PM
CryptoDavid has joined #osdev
<doug16k> yes. 64K limit max
<NieDzejkob> does the SDM document what was added when?
<doug16k> not really
<doug16k> I think the idea is, you get the manual for the year you want to support back to, and they guarantee everyting still works forever :P
<doug16k> a 286 OS would work fine on my 3950x
<doug16k> I want to run OS/2 on bare hardware just for a laugh someday
<doug16k> it's amazing for that to still work, giving how crazy aggressive modern x86 out-of-order is
<doug16k> imagine the instruction fetch bandwidth, getting 32 bytes per clock or more
<doug16k> cache hit staying perfectly at 100% forever because it hardly even needs the L2
<doug16k> I am amused by running really old software on extremely fast hardware, at a speed that the original programmers would think to be impossible
<doug16k> imagine the speed of a foxpro 2.6 query or UI update on a smartdrv 64M? probably not even one scanline of monitor scanout of delay
<doug16k> the code had to run like lightning to be good at the time
<doug16k> on a 33MHz 486, foxpro was instantaneous speed. imagine 4300MHz massively out of order with gigantic caches and crazy ram clock
<doug16k> why is all code so ridiculously slow now?
<doug16k> I'm guilty of it
<doug16k> my bootloader is all nice guy and reads the program headers and allows the content to be strewn all over the place
richbridger has joined #osdev
<doug16k> what really should be happening is, there is a memory image that is just flat contiguously stored on disk and I just single-DMA-transfer the entire "kernel load" and jump into it instantly
mahmutov has quit [Ping timeout: 265 seconds]
<doug16k> when I picture slapping the image on disk and requiring contiguous and the kernel being a bin image, I imaging those as bad things. those things make it ludicrous speed
<doug16k> it's like we're brainwashed that the slow thing is great and the instant thing is cheesy
Matt|home has quit [Quit: Leaving]
<doug16k> I am being asked to speed up python database code on AWS
<doug16k> I wish AWS was as fast as the 486DX-100 I had in the '90s
<doug16k> it's not even close
<doug16k> I guess if you stack up enough cold start delays, you can make any machine slower than a 486 in DOS with dbase B+ ISAM
<doug16k> why get one cpu to cache credentials once and reuse them million times, when you can get database credentials by making it do a request to a vm (that is likely off) every time
richbridger has quit [Remote host closed the connection]
<doug16k> it's physics. they make more money if it wastes cpu, so there is a force pushing it to waste more cpu
vai has joined #osdev
<vai> hi
<vai> Its pretty commond you do page tables in a static memory area, physically and virtually mapped alike ?
richbridger has joined #osdev
<vai> page directories e.g.
<doug16k> vai, yeah. even if you made it more elaborate, you might do that at first, and transition to the fancy one
zoey has quit [Quit: Leaving]
<vai> user and kernel page directories are seperate spaces to avoid conflicts
<vai> also global seperate
<vai> doug16k: oh yeah
<clever> vai: on arm32, there is a configurable split between the upper and lower chunk of the virtual space, and each has its own paging table
<vai> doug16k: first 4 megabytes or so is kernel code/data area for all that I mentioned + more
<vai> clever: I/O memory mapped areas same as in IA-32 ?
<clever> i think the config was just the number of bits that must all be 1 for an upper addr
<vai> 0xc000 0000 or so
<clever> vai: i dont know x86 paging that well
<vai> physically
<doug16k> the stuff below 1MB is all the same as usual yeah
<vai> clever: ARM PCs = still PCs? I think? :-)
<doug16k> ah only talking to clever. I'll stop interrupting
<doug16k> I thought you meant long mode vs 32 bit vm machine
<doug16k> you can expect I/O windows above 2GB
<doug16k> the closer you get to 4GB line, the more unlikely it is ram there
<doug16k> usually from 4GB up is all ram
<doug16k> but you need to use whatever memory map you get on that platform
<doug16k> so you don't really care to know where ram is or isn't, it's dynamic
<doug16k> my bootloader could handle every other page not being ram
<doug16k> starting at 1M line
<j`ey> lol
<j`ey> that would be an interesting machine
<doug16k> yes lol
<doug16k> I think bcos said his is that pessimistic too
<j`ey> but you couldnt dma with more than 1 page then D:
<doug16k> yes, it would be awful
<doug16k> it works because the whole kernel image expects to be at the vaddr completely ready to go, at entry
<doug16k> entry point is at fffffff....
<doug16k> it already had to use paging for the whole loading process
<doug16k> had to prepare the page tables I mean
<kc8apf> that's kinda how memory layout looks on TrustZone-M. They use a bit in the physical address to determine secure vs non-secure. SRAMs and many other devices have aliases to both so you end up with alternating blocks of secure and non-secure.
<doug16k> no problem making it handle gaps
<doug16k> x86 has that for SMM memory
<kc8apf> SMM at least takes a single range
<doug16k> there is an MTRR that strictly enforces that a certain physaddr range is inaccessible
<kc8apf> This is bit 23 or something
<doug16k> that reminds me that I should be working on my qemu patch
<doug16k> (I extended info tlb to show the memory type, considering the PTE bits, PAT, and MTRRs, and the priority rules in the SDM)
<doug16k> tells you resulting memory type, the PTE memory type (from PAT lookup) and the MTRR type
<doug16k> and yells about UB combinations
<doug16k> and UB overlaps
<doug16k> that's all done. I want to also extend it to be like a hex dump, where it omits contiguous regions if they all have the same type bits
<doug16k> klange suggestion
<klange> only the best ideas from me, of course
JX7P` has quit [Ping timeout: 252 seconds]
<doug16k> I always expand my patches to the point where they are uneasy with the size of the patch :D
<klange> my thinkpad has been booted into toaruos for four days now and I keep refreshing the weather panel widget and I'm almost surprised it keeps working
<doug16k> the gdbstub fix one was pretty funny. I drastically changed the machine description xml and they had no idea why (gdb was rejecting it silently)
<doug16k> was using builtin description and broke any time gdb asked for orig_eax
<doug16k> so register window was broken completely in a gui debugger
<doug16k> orig_eax is part of linux syscall abi
<doug16k> screwy in TUI too
<doug16k> layout regs showed empty pane
vdamewood has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]