The multiboot specification says: If bit 16 in the ‘flags’ word is set,
then the fields at offsets 12-28 in the Multiboot header are valid, and the
boot loader should use them instead of the fields in the actual executable
header to calculate where to load the OS image.
I believe they are valid in
Do you have a stack for the assert, from the ktrace?
On Tue, Jan 28, 2025 at 6:09 AM wrote:
> After fixing problems leading to compiler warnings---legitimate
> warnings, but even the too short binary negated unsigned 32bits values
> promoted to 64 bits with leading bits hence 0 as mask were ha
On Tue, Jan 28, 2025 at 07:45:02AM -0800, Paul Lalonde wrote:
> The multiboot specification says: If bit 16 in the ?flags? word is set,
> then the fields at offsets 12-28 in the Multiboot header are valid, and the
> boot loader should use them instead of the fields in the actual executable
> header
On Tue, Jan 28, 2025 at 07:49:02AM -0800, Paul Lalonde wrote:
> Do you have a stack for the assert, from the ktrace?
>
Yes, and I was wrong: it fails relatively "late" in main.c: at
mpsinit.
Here is the info (I added a bunch of print() before each function call
to know where it stumbled upon an
On Tue, Jan 28, 2025 at 09:18:29AM -0800, Paul Lalonde wrote:
> ktrace can generate a stack for you from that dump. The line starting with
> "ktrace" is the command line (you might change 9k8cpu to the path to the
> kernel file in you're not in the directory where you built it).
> Then the followi
Ah, that's the code path that sent me to QEMU.
Vmx doesn't have any MP tables, which leads to this fault in mpsinit.
Ron provided this minimal one for me, which I think we could learn from to
adapt into vmx. The hacky version of pointing the code directly at
something like this baked in didn't exc
I'd be happier to remove the mps dependency actually. the mps is long dead.
But that's a bigger story.
On Tue, Jan 28, 2025 at 11:24 AM Paul Lalonde
wrote:
> Ah, that's the code path that sent me to QEMU.
> Vmx doesn't have any MP tables, which leads to this fault in mpsinit.
> Ron provided thi
I stumbled onto this today and it made me chuckle. Performance isn't bad at all.
https://copy.sh/v86/?profile=9front
It might be interesting to have a Plan 9 server on the backend to
import the '#l' from and to boot the term with user credentials in
that domain.
-
yeah, there's a reason it is fe, and not 8, but memory fails me.
See this for details of the address hole:
https://en.wikipedia.org/wiki/X86-64
Charles may remember, but it goes back to the port they did in 2005.
On Tue, Jan 28, 2025 at 5:08 PM Ron Minnich wrote:
> btw, if you
> acid 9p
btw, if you
acid 9pc64
you can paste this right into acid
src(0xf011cdee); // dumpstack+0x10
src(0xf013d50f); // panic+0x133
src(0xf0116a3b); // KADDR+0x55
src(0xf012fe55); // sigsearch+0xc8
src(0xf012fec9); // mpsinit+0x14
src(0xf011622a); // main+0x
now, if you have the ktrace, you can get a stack trace, using the
first command printed in your ktrace:
ktrace 9k8cpu 0xf011cdee 0xf0105d58
and then pasting in the numbers.
see ktrace(1) for details.
Quoth tlaro...@kergis.com:
> On Tue, Jan 28, 2025 at 07:49:02AM -0800,
ktrace can generate a stack for you from that dump. The line starting with
"ktrace" is the command line (you might change 9k8cpu to the path to the
kernel file in you're not in the directory where you built it).
Then the following lines up to but not including the "cpu0: exiting" can be
dropped in
After fixing problems leading to compiler warnings---legitimate
warnings, but even the too short binary negated unsigned 32bits values
promoted to 64 bits with leading bits hence 0 as mask were harmless---
now I want to look at the stumbing block.
For me, under vmx, this is the assert in map.c:17:
In l32p.s, the multiboot flags in the the mbi are set as
$0x00010007
but I don't find flags definitions relative to the higher word,
neither in the multiboot v1 spec, nor in the enum in multiboot.c. They
are all limited to the two lowest bytes.
What is the purpose of the:
$0x00010007
^
T
vmx understands multiboot.
I really dislike asserts. That assert is not helpful: what is the
value of pa? What is the value of KSEG2? So if you want to start
somewhere, turn that into
if (pa>=KSEG2) panic("blah %p blah %p bla bl", pa, KSEG2); // still
one line, but actually useful output!
note th
all that does is set the lowest two bytes, which is fine.
On Tue, Jan 28, 2025 at 6:09 AM wrote:
>
> In l32p.s, the multiboot flags in the the mbi are set as
>
> $0x00010007
>
> but I don't find flags definitions relative to the higher word,
> neither in the multiboot v1 spec, nor in the enum
On Mon, Jan 27, 2025 at 07:10:36PM -0800, Bakul Shah via 9fans wrote:
> 9front came up fine under bhyve (uses efi). Last install from
> 9front-10522.amd64.iso
and once anyone starts shipping laptops with ed2k, we'll all breath a
sigh of relief.
khm
--
9fa
Maybe offtopic.
Found this - https://github.com/OpenPrograms/Plan9k/ wile surfing
"Internet"
Onecan run Plan9 like in minecraft :)
ср, 29 янв. 2025 г. в 01:51, Skip Tavakkolian :
> I stumbled onto this today and it made me chuckle. Performance isn't bad
> at all.
>
> https://copy.sh/v86/?profi
18 matches
Mail list logo
