9vx on x86-64

9vx on x86-64

[Russ Cox]

9vx now builds and runs on Ubuntu Linux x86-64,
and hopefully other Linuxes as well.
It also runs gs and ape/psh correctly.
I haven't built new binaries nor a new distribution.
Soon; perhaps tomorrow.

Russ

Re: [9fans] 9vx on x86-64

[simplicity]

On Dec 9, 6:45�pm, r...@swtch.com (Russ Cox) wrote:
> 9vx now builds and runs on Ubuntu Linux x86-64,
> and hopefully other Linuxes as well.
> It also runs gs and ape/psh correctly.
> I haven't built new binaries nor a new distribution.
> Soon; perhaps tomorrow.
>
> Russ

please give it to me :)

Re: [9fans] 9vx on x86-64

[Russ Cox]

On Thu, Dec 11, 2008 at 4:04 AM, simplicity <plan9assembler@gmail.com> wrote:
> On Dec 9, 6:45 pm, r...@swtch.com (Russ Cox) wrote:
>> 9vx now builds and runs on Ubuntu Linux x86-64,
>> and hopefully other Linuxes as well.
>> It also runs gs and ape/psh correctly.
>> I haven't built new binaries nor a new distribution.
>> Soon; perhaps tomorrow.
>>
>> Russ
>
> please give it to me :)

you can get it yourself as long as you want to
compile it: http://hg.pdos.csail.mit.edu/hg/vx32

russ

Re: [9fans] 9vx on x86-64

[Devon H. O'Dell]

2008/12/11 Russ Cox <rsc@swtch.com>:
> On Thu, Dec 11, 2008 at 4:04 AM, simplicity <plan9assembler@gmail.com> wrote:
>> On Dec 9, 6:45 pm, r...@swtch.com (Russ Cox) wrote:
>>> 9vx now builds and runs on Ubuntu Linux x86-64,
>>> and hopefully other Linuxes as well.
>>> It also runs gs and ape/psh correctly.
>>> I haven't built new binaries nor a new distribution.
>>> Soon; perhaps tomorrow.
>>>
>>> Russ
>>
>> please give it to me :)
>
> you can get it yourself as long as you want to
> compile it: http://hg.pdos.csail.mit.edu/hg/vx32
>
> russ

I've got a patch at this point that gets it to build on FreeBSD/amd64,
but it dies in the trap handler (surprise, surprise). There are a
couple other things I've added / plan to add shortly. Russ, should I
just keep sending patches your way?

--dho

Re: [9fans] 9vx on x86-64

[prem]

On Dec 11, 7:08�pm, r...@swtch.com (Russ Cox) wrote:
> On Thu, Dec 11, 2008 at 4:04 AM, simplicity <plan9assemb...@gmail.com> wrote:
> > On Dec 9, 6:45 pm, r...@swtch.com (Russ Cox) wrote:
> >> 9vx now builds and runs on Ubuntu Linux x86-64,
> >> and hopefully other Linuxes as well.
> >> It also runs gs and ape/psh correctly.
> >> I haven't built new binaries nor a new distribution.
> >> Soon; perhaps tomorrow.
>
> >> Russ
>
> > please give it to me :)
>
> you can get it yourself as long as you want to
> compile it:http://hg.pdos.csail.mit.edu/hg/vx32
>
> russ

Aborted, here is alog with -P -S -X
------------------------
reate new cpu: kprocq.n=1 nrunproc=0
cpu0: ready 2 *x11*; wakeup kproc cpus
cpu1: runproc 2 *x11* [0 0]
create new cpu: kprocq.n=1 nrunproc=0
cpu0: ready 3 *timer*; wakeup kproc cpus
cpu2: runproc 3 *timer* [0 0]
        namec #/
        namec #e/terminal
        namec #e/cputype
        namec #e/rootdir
        namec #e/service
        namec #e/user
        namec #e/sysname
        namec #Zplan9/
create new cpu: kprocq.n=1 nrunproc=0
cpu0: ready 4 *io*; wakeup kproc cpus
cpu3: runproc 4 *io* [0 0]
create new cpu: kprocq.n=1 nrunproc=0
cpu0: ready 4 *io*; wakeup kproc cpus
cpu3: runproc 4 *io* [0 1]
cpu4: runproc psleep 0 1
        namec /
        namec #p
cpu3: runproc psleep 0 2
        namec /proc
        namec #~/mntloop
        namec #Zplan9/
cpu0: ready 4 *io*; wakeup kproc cpus
cpu3: runproc awake
cpu3: runproc 4 *io* [0 1]
cpu0: idlehands
cpu3: runproc psleep 0 2
cpu0: busy hands
cpu0: idlehands returning
        namec #s/boot
+vx32 712ee0 7ff269bf3010 *init* eip\x1020 espÿfff84
vx32_sighandler signo\x11 eip=0x47674d esp=0x69470c98 vs=0x1f
rax 0000000000000000  rbx 0000000000000000
rcx 00000000004783e2  rdx 000000000000002b
rsi 00007ff269470c58  rdi 0000000050c6c000
rbp 00007ff269470f08  rsp 00007ff269470c98
r8  00007ff269470dc8  r9  0000000000000000
r10 0000000000000000  r11 0000000000000202
r12 0000000000833010  r13 000000000fffff84
r14 0000000000001020  r15 0000000050c6c000
rip 000000000047674d  efl 0000000000010246  cs 0033  ss 0000
err 0000000000000000  trapno 000000000000000d  cr2 0000000000000000
vxemu_sighandler 50c6c000 -0x1
VX trap e err 0 va 00000000 veip 00001020 veflags 00000000
-vx32 712ee0 7ff269bf3010 *init* eip\x1020 espÿfff84 rc=0xe
notify
cpu0: ready 4 *io*; wakeup kproc cpus
cpu3: runproc awake
cpu3: runproc 4 *io* [0 1]
9vx panic: boot process died: sys: trap: page fault pc=0x00001020
cpu3: runproc psleep 0 2
aborting, to dump core.
Aborted
----------------------------------------

Re: [9fans] 9vx on x86-64

[Russ Cox]

> Aborted, here is alog with -P -S -X
> ------------------------
> reate new cpu: kprocq.n1 nrunproc0
> cpu0: ready 2 *x11*; wakeup kproc cpus

It seems a little odd that the log starts with
a partial word.  It is posible that if you did

9vx -PSX >log 2>&1

that somehow the fd offsets for 1 and 2 are
not being maintained properly
(I don't understand it, but I've seen it).

Sometimes it works better to do

9vx -PSX 2>&1 | cat >log

Russ

Re: [9fans] 9vx on x86-64

[prem]

> 9vx -PSX >log 2>&1
I just executed 9vx -P -S -X -r <path of dist 0.12> -u glenda

and pasted what was written on the linux console.

> 9vx -PSX 2>&1 | cat >log
this creates a log of 138 MB :( (19MB gzipped)

However, I think I solved it without actually solving it,
gcc flags changed from -g -03 to -g,
it works like a charm

/Prem

On Dec 12, 5:46�pm, r...@swtch.com (Russ Cox) wrote:
> > Aborted, here is alog with -P -S -X
> > ------------------------
> > reate new cpu: kprocq.n1 nrunproc0
> > cpu0: ready 2 *x11*; wakeup kproc cpus
>
> It seems a little odd that the log starts with
> a partial word. �It is posible that if you did
>
> 9vx -PSX >log 2>&1
>
> that somehow the fd offsets for 1 and 2 are
> not being maintained properly
> (I don't understand it, but I've seen it).
>
> Sometimes it works better to do
>
> 9vx -PSX 2>&1 | cat >log
>
> Russ

Re: [9fans] 9vx on x86-64

[Russ Cox]

>> 9vx -PSX 2>&1 | cat >log
> this creates a log of 138 MB :( (19MB gzipped)

19 MB gzipped doesn't sound so bad.
Can you send it to me (not to 9fans)
as an attachment, or put it up somewhere
that I can fetch it from?

> However, I think I solved it without actually solving it,
> gcc flags changed from -g -03 to -g,
> it works like a charm

That's scary.  Can you send the output of "gcc -v"?

Thanks.
Russ

Re: [9fans] 9vx on x86-64

[prem]

>
> That's scary. �Can you send the output of "gcc -v"?
>
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: /var/tmp/portage/sys-devel/gcc-4.3.2/work/gcc-4.3.2/
configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/
4.3.2 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/include --
datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.3.2 --mandir=/usr/
share/gcc-data/x86_64-pc-linux-gnu/4.3.2/man --infodir=/usr/share/gcc-
data/x86_64-pc-linux-gnu/4.3.2/info --with-gxx-include-dir=/usr/lib/
gcc/x86_64-pc-linux-gnu/4.3.2/include/g++-v4 --host=x86_64-pc-linux-
gnu --build=x86_64-pc-linux-gnu --disable-altivec --disable-fixed-
point --enable-nls --without-included-gettext --with-system-zlib --
disable-checking --disable-werror --enable-secureplt --enable-multilib
--enable-libmudflap --disable-libssp --enable-libgomp --enable-cld --
enable-objc-gc --enable-languages=c,c++,java,objc,obj-c+
+,treelang,fortran --enable-shared --enable-threads=posix --enable-
__cxa_atexit --enable-clocale=gnu --with-bugurl=http://
bugs.gentoo.org/ --with-pkgversion='Gentoo 4.3.2 p1.1'
Thread model: posix
gcc version 4.3.2 (Gentoo 4.3.2 p1.1)

Re: [9fans] 9vx on x86-64

[prem]

Here is the log dump
http://rapidshare.com/files/174406971/log.gz.html

Re: [9fans] 9vx on x86-64

[prem]

On Dec 9, 9:45�am, r...@swtch.com (Russ Cox) wrote:
> 9vx now builds and runs on Ubuntu Linux x86-64,
> and hopefully other Linuxes as well.
> It also runs gs and ape/psh correctly.
> I haven't built new binaries nor a new distribution.
> Soon; perhaps tomorrow.
>
> Russ

Pulled latest sources from mercurial, not working for me. I can see a
window openning and immediately see it crashing
I am using the latest 9vx on old distribution, just replaced the exe.
Compiles fine on a Sabayon 3.5.1 x86_64

9vx panic: boot process died: sys: trap: page fault pc=0x00001020
aborting, to dump core.

Re: [9fans] 9vx on x86-64

[simplicity]

It seems not working on LFS64 (pure-64 linux.from scratch)
vx64?



bash-3.2$ make
gcc -m64 -c -nostdinc -Ilibvxc/include -g -O3 -MD -std=gnu99 -I.  -fno-
stack-protector -m80387 -mfp-ret-in-387 -o libvxc/abort.o libvxc/
abort.c
gcc -m64 -c -nostdinc -Ilibvxc/include -g -O3 -MD -std=gnu99 -I.  -fno-
stack-protector -m80387 -mfp-ret-in-387 -o libvxc/assert.o libvxc/
assert.c
gcc -m64 -c -nostdinc -Ilibvxc/include -g -O3 -MD -std=gnu99 -I.  -fno-
stack-protector -m80387 -mfp-ret-in-387 -o libvxc/atexit.o libvxc/
atexit.c
gcc -m64 -c -nostdinc -Ilibvxc/include -g -O3 -MD -std=gnu99 -I.  -fno-
stack-protector -m80387 -mfp-ret-in-387 -o libvxc/difftime.o libvxc/
difftime.c
gcc -m64 -c -nostdinc -Ilibvxc/include -g -O3 -MD -std=gnu99 -I.  -fno-
stack-protector -m80387 -mfp-ret-in-387 -o libvxc/errno.o libvxc/
errno.c
...
gcc -m64 -c -nostdinc -Ilibvxc/include -g -O3 -MD -std=gnu99 -I.  -fno-
stack-protector -m80387 -mfp-ret-in-387 -o libvxc/bsdstdio/vasprintf.o
libvxc/bsdstdio/vasprintf.c
gcc -m64 -c -nostdinc -Ilibvxc/include -g -O3 -MD -std=gnu99 -I.  -fno-
stack-protector -m80387 -mfp-ret-in-387 -o libvxc/bsdstdio/vfprintf.o
libvxc/bsdstdio/vfprintf.c
libvxc/bsdstdio/vfprintf.c: In function :
libvxc/bsdstdio/vfprintf.c:320: error: incompatible types when
assigning to type  from type
libvxc/bsdstdio/vfprintf.c: In function :
libvxc/bsdstdio/vfprintf.c:1008: error: incompatible types when
assigning to type  from type
make: *** [libvxc/bsdstdio/vfprintf.o] Error 1

Re: [9fans] 9vx on x86-64

[Russ Cox]

> gcc -m64 -c -nostdinc -Ilibvxc/include -g -O3 -MD -std=gnu99 -I.  -fno-
> stack-protector -m80387 -mfp-ret-in-387 -o libvxc/abort.o libvxc/
> abort.c

It looks like you edited the VX32_CC line to say gcc -m64.
That's wrong.  $(VX32_CC) is supposed to be an i386 ELF compiler.
You should be able to compile just fine using gcc -m32.
If your host compiler can't do -m32 then you need to install
the vx32-gcc from the sources on the vx32 home page.

Russ