<geist>
oh bummer. i thought vzeroall *also* zeroed out zmm state
<geist>
but alas, it only zeros out through ymm15
<geist>
pretty dumb, why didn't they extend it to get zmm16-zmm31?
<geist>
hmm, i guess the point is it's only explicitly used to handle transitioning between SSE and AVX, so it explicitly only covers ymm/zmm registers that are aliased with SSE regs
srjek has joined #osdev
andydude has joined #osdev
andydude has quit [Client Quit]
qookie has quit [Ping timeout: 252 seconds]
diamondbond has joined #osdev
Arthuria has quit [Ping timeout: 245 seconds]
diamondbond has quit [Client Quit]
diamondbond has joined #osdev
dude12312414 has quit [Remote host closed the connection]
dude12312414 has joined #osdev
diamondbond has quit [Quit: Leaving]
gog has quit [Ping timeout: 265 seconds]
diamondbond has joined #osdev
diamondbond has quit [Read error: Connection reset by peer]
<geist>
well, just spent the last hour trying to finally grok the layout and use of xsave/xsaveop/xsavec/xsaves and what the format is
<geist>
think i finally get it now. a lot of it has to deal with how the cpu tracks initial and modified state
[itchyjunk] has quit [Ping timeout: 252 seconds]
[itchyjunk] has joined #osdev
srjek has quit [Ping timeout: 264 seconds]
dude12312414 has quit [Quit: THE RAM IS TOO DAMN HIGH]
nyah has quit [Quit: leaving]
geist has quit [Ping timeout: 245 seconds]
__sen has joined #osdev
Benjojo has joined #osdev
paulbarker has joined #osdev
theruran has joined #osdev
geist has joined #osdev
nohit has joined #osdev
sts-q has quit [Ping timeout: 252 seconds]
eremitah has quit [Quit: quit]
eremitah has joined #osdev
vai has joined #osdev
<vai>
my library malloc needs thread-safety
<vai>
hi /dev/*
<vai>
lock to module or function? depends on... surprised actually
<vai>
-O4 basically crashes because all the operating systems are doing too many thread safety violations - they say it is mature (O4 opt.)
<vai>
also: planning to make it CP/M (single-task), and now everything works out of sudden
<vai>
no bugs, just thread violations :: multitasking suks :::
Oli has quit [Quit: leaving]
_whitelogger has joined #osdev
ElectronApps has joined #osdev
wleslie has joined #osdev
vdamewood has joined #osdev
<vai>
client, server, and queues -- a big TODO on paper
<vai>
low level talk :: buffers
[itchyjunk] has quit [Remote host closed the connection]
<geist>
what compiler are you talking about? -O4 doesnt' do anything on gcc or clang
<Mondenkind>
I think some ibm compiler goes up to -O5
gdown has quit [Remote host closed the connection]
<jason1234>
how much minimum of RAM requirement is needed for the Raspberry PI model 4, (PI model four), 1gb, 2gb,...8gb to play well Sony PS2 and GameCube games on it?
<vdamewood>
More than 12 bytes.
<vdamewood>
probably
<bradd>
the ps2 had 32mb ram, so probably 1gb would be enough no?
<vdamewood>
Oh,if the PS2 had 32 MB, then you probably need well over 12 bytes. Maybe more than 24 bytes.
<bradd>
25?
<bradd>
jason1234: I googled ps2 emulator memory usage -> '...pcsx2... pentuim 4 processor with 512mb of ram...'
<jason1234>
i use RETROPIE and i would like to buy a PI model 4, but it is expensive, i know need to know how much min RAM requirements...
<bradd>
just google it. 'retropie memory usage'
dude12312414 has quit [Quit: THE RAM IS TOO DAMN HIGH]
<jason1234>
Which OS would possible work on this amazing (old) machine: on Intel Pentium® processor, 16KB cache on chip, 133 MHz Pentium® processor, 16MB EDO RAM, 1.44 billion byte capacity (1.35 GB) ?
<jason1234>
Which OS would possible work on this amazing (old) machine: on Intel Pentium® processor, 16KB cache on chip, 133 MHz Pentium® processor, 16MB EDO RAM, IDE harddisk with 1.44 billion byte capacity (1.35 GB) ?
anon16_ has quit [Ping timeout: 252 seconds]
<kazinsal>
Windows NT 3.51
mahmutov_ has joined #osdev
<Ermine>
OS/2?
zacque has joined #osdev
zacque has quit [Quit: Client closed]
Arsen has quit [Quit: Quit.]
Arsen has joined #osdev
Vercas has quit [Quit: Ping timeout (120 seconds)]
Vercas has joined #osdev
blueops has joined #osdev
<blueops>
Hello
<blueops>
I have made a simple uefi program
<blueops>
It boots in qemu
<blueops>
However it does not boot in vmware hyper v or virtualbox
<blueops>
Or real hardware for that matter
<blueops>
Even with secure boot disabled
GeDaMo has joined #osdev
<zid>
rip
blueops has quit [Remote host closed the connection]
<zid>
but you should get an output window if you built qemu with a method to
<zid>
like with SDL or X support etc
<henistein>
alright
<henistein>
well it seems like doing -kernel file or don't is the same. do I need rootfs?
<j`ey>
you shouldnt do, it should print stuff out
<henistein>
I am new on this, my goal is running this kernel
<j`ey>
it'll fail, but at least print stuff out
<j`ey>
ohh
<j`ey>
henistein: also add: -cpu cortex-a72 -nographic
<henistein>
alright it is doing something now I think
<henistein>
and my terminal crashed, well I am happy I got something
<j`ey>
the terminal crashed? or you mean the kernel printed the panic message..
<henistein>
no it was like running forever and I couldn't do nothing (write, ctr-d, ctr-c)-
<henistein>
but no error message
<j`ey>
so did the kernel print anything at all?
<henistein>
I will try the same without using kernel and see if it happens too, if yes then the kernel was not executed
<henistein>
no
<j`ey>
without the kernel, qemu will just close
<henistein>
it is happening the same thing without the kernel, I think the kernel is not being executed
<j`ey>
what's the exact command youre running?
<henistein>
running: qemu-system-aarch64 -M virt -cpu cortex-a72 -nographic is doing the same as running qemu-system-aarch64 -M virt -cpu cortex-a72 -nographic -kernel file
<j`ey>
oh weird, anyway use: ctrl-a x, to kill qemu
<HeTo>
well, if this is some random Android kernel intended for some real device somewhere maybe it lacks all the drivers to do I/O in a QEmu "virt" device
<henistein>
HeTo yes it is probably that, I can't just grab a random kernel and expect it to run on qemu
<henistein>
thank you all anyway
<zid>
well, run on a random -machine
<j`ey>
I think it should do, gimme a sec
<zid>
there might be an androidy one
<henistein>
j`ey sure
<j`ey>
hm, I'd just be surprised if it didnt have a PL011 uart driver.. but maybe not
<j`ey>
henistein: whats your goal anyway?
<henistein>
my goal is just trying to run this kernel, it could be just a error message or something else
<j`ey>
but why this kernel in particular?
<j`ey>
you could try add -append "console=ttyAMA0"
<j`ey>
it's funny cos the first kernel I tried locally doesnt actually have PL011 built in
<henistein>
this is the "comma three" (https://comma.ai/) kernel, I was just exploring and decided to check if I could run it into qemu
<zid>
would that need a monitor or anything command on the qemu side j`ey?
<henistein>
it's saturday I have nothing more to do
<j`ey>
zid: no
<j`ey>
henistein: try adding 'earlycon' to the -append ".." too