[9fans] lguest on 2.6.25

[9fans] lguest on 2.6.25

[Alex Lee]

Hi all,

I'd like to set up a cpu/auth/file server for my home network. I
already have a laptop server running Ubuntu 8.04, so the idea is to
also get Plan 9 running on it, via lguest. It's mostly working, but
I'm encountering a few problems.

Here's what I've done so far (maybe it's excessive list every single
step, but just in case...):

1. Grab relevant files.

- Download 9lguestcpu.2.6.25.elf and RUNLGUEST from Ron's contrib directory
- Get thx9.img out http://9grid.net/rminnich/src/lguest/thnx9.bz2
- Download the 2.6.25 kernel: linux-2.6.25.tar.bz2 (dated 2008-04-17;
I tried the latest version, 2.6.25.16, but encountered the same
problems that were reported in http://9fans.net/archive/2008/07/690)

2. Compile and install kernel

- I start with the stock 2.6.25 kernel. I then copy in my current
config (Ubuntu 2.6.24-19-generic), run 'make oldconfig', then answer
the config prompts with mostly the defaults.
- Then I configure the LGUEST, LGUEST_LGUEST, VIRTIO, etc. config
entries as per the lguest.txt documentation.
- Then I compile (here the debian way, with 'make-kpkg kernel_image
kernel_headers').
- I also run 'make' in Documentation/lguest to get my 'lguest' binary.

3. Prepare host machine

- Install the new kernel on the host machine and reboot.
- modprobe lg syscall_vector=64
- iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
- echo 1 > /proc/sys/net/ipv4/ip_forward

4. Run Plan 9 in lguest

- I modified RUNLGUEST so that the command is:
  ./lguest 256 9lguestcpu.2.6.25.elf --block=thx9.img
--tunnet=192.168.19.1
'venti=#S/sd00/arenas;bootdisk=local!#S/sd00/fossil;bootargs=local!#S/sd00/fossil'
- sudo ./RUNLGUEST

Eventually it prompts for the filesystem, and I pick the default. Here
is the output from that point onwards:

root is from (tcp, il, local)[local!#S/sd00/fossil]:
disk is #S/sd00/fossil
AUTHENTICATE ...
time...
GET VENTI ENV! #S/sd00/arenas
IN THERE AND nf is 1
F 0 is #S/sd00/arenas
venti...configloopbackk!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
DID CONFIG LOOPBACK
setenv venti to tcp!127.1!17034
fossil(#S/sd00/fossil)...version...time...
init[0] = init
init[1] = -c
LGATTACH edev c0440b90 ctlr c0440dd0
LGINIT
SETMAC: NO
ETHERIN: devno 3 ring 0 irq 34
ETHEROUT: devno 3 ring 0 irq 35
lguestnetwork is
ndb/dns: can't read my ip address
rc (cpurc): null list in concatenation

init: starting /bin/rc
%

Networking wasn't working at first. So I modified /lib/ndb/local so
that the dns entry pointed to my router (192.168.1.1), and then I ran
the following:

% ip/ipconfig -g 192.168.19.1 ether /net/ether0 192.168.19.2 255.255.255.0
% ndb/dns -r

And then I can resolve names and ping out. So far, so good, but there
are three problems that I'm still trying to figure out:

1. How can I avoid having to manually configure networking each time I boot?
2. I can ping from the host machine to the lguest interface
(192.168.19.2), but when I try to connect with drawterm the connection
is refused.
3. lguest always runs at full CPU. How can I figure out why this is
happening? (I don't feel comfortable running lguest for more than a
few minutes at a time -- the laptop gets pretty hot.)

Any advice or pointers on these issues would be greatly appreciated. Thanks!

Alex


--
Alex Lee <alexlee@uchicago.edu>

Re: [9fans] lguest on 2.6.25

[ron minnich]

OK, I see this note and am sorry this is not working well for you. I
will try again this week to get this going.

It's harder now as I'm now on a 64-bit machine and 64-bit lguest is not there.

But I'll try to get you an answer.

Sorry

ron

Re: [9fans] lguest on 2.6.25

[ron minnich]

On Sun, Aug 24, 2008 at 4:23 PM, Alex Lee <alexlee@uchicago.edu> wrote:

> Here's what I've done so far (maybe it's excessive list every single
> step, but just in case...):

not at all!

>
> 1. Grab relevant files.
>
> - Download 9lguestcpu.2.6.25.elf and RUNLGUEST from Ron's contrib directory
> - Get thx9.img out http://9grid.net/rminnich/src/lguest/thnx9.bz2
> - Download the 2.6.25 kernel: linux-2.6.25.tar.bz2 (dated 2008-04-17;
> I tried the latest version, 2.6.25.16, but encountered the same
> problems that were reported in http://9fans.net/archive/2008/07/690)

The linux kernel is very fluid nowadays, and 2.6.xx.yy is not always
working as 2.6.22.yy++. It's frustrating. So:
>
> 2. Compile and install kernel
>
> - I start with the stock 2.6.25 kernel. I then copy in my current
> config (Ubuntu 2.6.24-19-generic), run 'make oldconfig', then answer
> the config prompts with mostly the defaults.
> - Then I configure the LGUEST, LGUEST_LGUEST, VIRTIO, etc. config
> entries as per the lguest.txt documentation.
> - Then I compile (here the debian way, with 'make-kpkg kernel_image
> kernel_headers').
> - I also run 'make' in Documentation/lguest to get my 'lguest' binary.
>

good.

> 3. Prepare host machine
>
> - Install the new kernel on the host machine and reboot.
> - modprobe lg syscall_vector=64
> - iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
> - echo 1 > /proc/sys/net/ipv4/ip_forward

good.

>
> 4. Run Plan 9 in lguest
>
> - I modified RUNLGUEST so that the command is:
>  ./lguest 256 9lguestcpu.2.6.25.elf --block=thx9.img
> --tunnet=192.168.19.1
> 'venti=#S/sd00/arenas;bootdisk=local!#S/sd00/fossil;bootargs=local!#S/sd00/fossil'
> - sudo ./RUNLGUEST
>
> Eventually it prompts for the filesystem,

that's encouraging.

>and I pick the default. Here
> is the output from that point onwards:
>
> root is from (tcp, il, local)[local!#S/sd00/fossil]:
> disk is #S/sd00/fossil
> AUTHENTICATE ...
> time...
> GET VENTI ENV! #S/sd00/arenas
> IN THERE AND nf is 1
> F 0 is #S/sd00/arenas
> venti...configloopbackk!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> DID CONFIG LOOPBACK
> setenv venti to tcp!127.1!17034
> fossil(#S/sd00/fossil)...version...time...
> init[0] = init
> init[1] = -c
> LGATTACH edev c0440b90 ctlr c0440dd0
> LGINIT
> SETMAC: NO
> ETHERIN: devno 3 ring 0 irq 34
> ETHEROUT: devno 3 ring 0 irq 35
> lguestnetwork is

see this line? It's a variable read in /rc/bin/cpurc. You can check
that script and see how it can be set so that networking is a little
better. More I do not recall and the machine is not nearby ...

> ndb/dns: can't read my ip address
> rc (cpurc): null list in concatenation
>
> init: starting /bin/rc
> %
>
> Networking wasn't working at first. So I modified /lib/ndb/local so
> that the dns entry pointed to my router (192.168.1.1), and then I ran
> the following:
>
> % ip/ipconfig -g 192.168.19.1 ether /net/ether0 192.168.19.2 255.255.255.0
> % ndb/dns -r
>
> And then I can resolve names and ping out. So far, so good, but there
> are three problems that I'm still trying to figure out:

ok
>
> 1. How can I avoid having to manually configure networking each time I boot?

Something has to answer a DHCP request from your guest. Can you run
dhcpd on the host?

> 2. I can ping from the host machine to the lguest interface
> (192.168.19.2), but when I try to connect with drawterm the connection
> is refused.

Try restarting the listen? that's an odd one. If you telnet to the
port from the host to the guest what do you see?

> 3. lguest always runs at full CPU. How can I figure out why this is
> happening? (I don't feel comfortable running lguest for more than a
> few minutes at a time -- the laptop gets pretty hot.)

hmm. I have not seen this one. Again, not sure why this is happening.
But the halt
may not be working. Possibly the API has changed -- not sure.

ron

Re: [9fans] lguest on 2.6.25

[Alex Lee]

On Sun, Aug 24, 2008 at 11:32 PM, ron minnich <rminnich@gmail.com> wrote:
[snip]
>> lguestnetwork is
>
> see this line? It's a variable read in /rc/bin/cpurc. You can check
> that script and see how it can be set so that networking is a little
> better. More I do not recall and the machine is not nearby ...
>
[snip]
>> 2. I can ping from the host machine to the lguest interface
>> (192.168.19.2), but when I try to connect with drawterm the connection
>> is refused.
>
> Try restarting the listen? that's an odd one. If you telnet to the
> port from the host to the guest what do you see?

Ah, I see now. I added "lguestnetwork=NAT" to parameters in RUNLGUEST,
and now both networking and drawterm are working great!

>> 3. lguest always runs at full CPU. How can I figure out why this is
>> happening? (I don't feel comfortable running lguest for more than a
>> few minutes at a time -- the laptop gets pretty hot.)
>
> hmm. I have not seen this one. Again, not sure why this is happening.
> But the halt
> may not be working. Possibly the API has changed -- not sure.
>
> ron

Let me know if there's any information that I can provide to help with
this. Many thanks for all the hard work that you've put into doing
this port.

Best,
Alex


--
Alex Lee <alexlee@uchicago.edu>

Re: [9fans] lguest on 2.6.25

[John Soros]

On Sun, 24 Aug 2008 23:58:21 -0500
"Alex Lee" <alexlee@uchicago.edu> wrote:

> On Sun, Aug 24, 2008 at 11:32 PM, ron minnich <rminnich@gmail.com> wrote:
> [snip]
> >> lguestnetwork is
> >
> > see this line? It's a variable read in /rc/bin/cpurc. You can check
> > that script and see how it can be set so that networking is a little
Hello,
I have gotten the lguest port working on the 2.6.25.0 kernel, it works mighty fine here.
The load issue for me is only on plan9, on the host I can see with 'top' that the lguest guest isn't consuming all the cpu, so this might ust be a plan9 problem. I have also seen quite a few messages in /sys/log/cron i get a lot of lines saying:
$sysname Aug 25 08:31:14 time went backward

I found routed networking to be the simplest, nat gives me the creeps.
So here is my way to start the lguest guest, I hope it will be helpful:

====snip
#!/bin/bash
set -x
/root/bin/lguest --tunnet=$1 --block=/dev/mirror/plan9cpu \
	512 /home/johnny/9lguestcpu.2.6.25.elf 'bootargs=local!#S/sd00/fossil;sysname=9soul;bootdisk=local!#S/sd00/fossil'
sleep 10
ip route add $3 via $1 dev $2
ip route del 192.168.0.0/24 dev $2
echo 1 > /proc/sys/net/ipv4/conf/$2/proxy_arp
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
====snip

$1 is the host ip, $2 is the tap interface the guest will use, and $3 is the ip the guest will have. This method only works for static networking, also you will need to install the iproute2 utilities. These command also assume the your net is 192.168.0.0 netmask 255.255.255.0, change that to whatever suits you.

Cheers,
John


> > better. More I do not recall and the machine is not nearby ...
> >
> [snip]
> >> 2. I can ping from the host machine to the lguest interface
> >> (192.168.19.2), but when I try to connect with drawterm the connection
> >> is refused.
> >
> > Try restarting the listen? that's an odd one. If you telnet to the
> > port from the host to the guest what do you see?
>
> Ah, I see now. I added "lguestnetwork=NAT" to parameters in RUNLGUEST,
> and now both networking and drawterm are working great!
>
> >> 3. lguest always runs at full CPU. How can I figure out why this is
> >> happening? (I don't feel comfortable running lguest for more than a
> >> few minutes at a time -- the laptop gets pretty hot.)
> >
> > hmm. I have not seen this one. Again, not sure why this is happening.
> > But the halt
> > may not be working. Possibly the API has changed -- not sure.
> >
> > ron
>
> Let me know if there's any information that I can provide to help with
> this. Many thanks for all the hard work that you've put into doing
> this port.
>
> Best,
> Alex
>
>

Re: [9fans] lguest on 2.6.25

[erik quanstrom]

> Hello,
> I have gotten the lguest port working on the 2.6.25.0 kernel, it works mighty fine here.
> The load issue for me is only on plan9, on the host I can see with 'top' that the lguest guest isn't consuming all the cpu, so this might ust be a plan9 problem. I have also seen quite a few messages in /sys/log/cron i get a lot of lines saying:
> $sysname Aug 25 08:31:14 time went backward

both the excessive load and these messages sound like a timesync problem.

- erik

Re: [9fans] lguest on 2.6.25

[ron minnich]

On Mon, Aug 25, 2008 at 3:56 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> Hello,
>> I have gotten the lguest port working on the 2.6.25.0 kernel, it works mighty fine here.
>> The load issue for me is only on plan9, on the host I can see with 'top' that the lguest guest isn't consuming all the cpu, so this might ust be a plan9 problem. I have also seen quite a few messages in /sys/log/cron i get a lot of lines saying:
>> $sysname Aug 25 08:31:14 time went backward
>
> both the excessive load and these messages sound like a timesync problem.
>

yeah, that's really weird. One option is to set up the kernels without
any fancy timers -- just use the old PC timers.

ron

Re: [9fans] lguest on 2.6.25

[ron minnich]

On Mon, Aug 25, 2008 at 7:52 AM, ron minnich <rminnich@gmail.com> wrote:
> On Mon, Aug 25, 2008 at 3:56 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>>> Hello,
>>> I have gotten the lguest port working on the 2.6.25.0 kernel, it works mighty fine here.
>>> The load issue for me is only on plan9, on the host I can see with 'top' that the lguest guest isn't consuming all the cpu, so this might ust be a plan9 problem. I have also seen quite a few messages in /sys/log/cron i get a lot of lines saying:
>>> $sysname Aug 25 08:31:14 time went backward
>>
>> both the excessive load and these messages sound like a timesync problem.
>>
>
> yeah, that's really weird. One option is to set up the kernels without

by 'kernel' here I mean linux kernel, sorry.

ron

Re: [9fans] lguest on 2.6.25

[erik quanstrom]

>> both the excessive load and these messages sound like a timesync problem.
>>
>
> yeah, that's really weird. One option is to set up the kernels without
> any fancy timers -- just use the old PC timers.

do you think that's the problem?

time jumping backwards doesn't seem like something that could
be traced to some oddity of the lguest environment.  (at least i
lack the imagination to know how this could happen.) it sounds
more like the traditional problem of having started two timsyncs.

it any event, fixing timesync properly is likely to fix the excessive
load problem.

- erik

Re: [9fans] lguest on 2.6.25

[ron minnich]

On Mon, Aug 25, 2008 at 7:59 AM, erik quanstrom <quanstro@coraid.com> wrote:

> it any event, fixing timesync properly is likely to fix the excessive
> load problem.

good to know. I probably jumped to the wrong conclusion.

ron

Re: [9fans] lguest on 2.6.25

[John Soros]

Hello again,
Well, i don't think I am starting two timesync, ps a shows only one:
cpu% ps a |grep timesync
bootes           77    0:00   0:00       92K Pread    timesync
I also can not write to /dev/rtc, so the timesync part of cpurc fails, this part in particular
=========snip
if(! ps|grep -s timesync) {
	aux/timesync -n pool.ntp.org
	if (test -e '#r/rtc') @ {
		sleep 10			# let timesync correct the time
		awk '{print $1}' /dev/time >'#r/rtc'	# fix hw clock
	} &
}
=============
awk: i/o error occurred while closing /dev/stdout
 input record /dev/time:1
 source line 1

I have also tried to compile the kernel by doing:
cpu% fcp /n/sources/contrib/rminnich/lguest/lg25.tgz $home/src; cd $home/src; tar xzf lg25.tgz;
cpu% mkdir src/boot
cpu% mkdir src/ip
cpu% mkdir src/pc
cpu% mkdir src/port
cpu% rc bin/rc/lguest
cpu% mk 'conf=lguestcpu'
.....
8c -FTVw lgkbd.c
../port/portdat.h:536 dat.h:130 lgkbd.c:4 syntax error, last name: Tval
mk: 8c -FTVw lgkbd.c  : exit status=rc 887: 8c 889: error

Any help would be appreciated, this timesync problem is causing me quite some headaches :-)

Thanks
John


On Mon, 25 Aug 2008 10:59:37 -0400
erik quanstrom <quanstro@coraid.com> wrote:

> >> both the excessive load and these messages sound like a timesync problem.
> >>
> >
> > yeah, that's really weird. One option is to set up the kernels without
> > any fancy timers -- just use the old PC timers.
>
> do you think that's the problem?
>
> time jumping backwards doesn't seem like something that could
> be traced to some oddity of the lguest environment.  (at least i
> lack the imagination to know how this could happen.) it sounds
> more like the traditional problem of having started two timsyncs.
>
> it any event, fixing timesync properly is likely to fix the excessive
> load problem.
>
> - erik
>
>

Re: [9fans] lguest on 2.6.25

[lucio]

> Well, i don't think I am starting two timesync, ps a shows only one:

If Xen is anything to go by, time keeping is a problem in
virtualisation.  And Erik is misguiding you :-)

Thing is, if timesync is wresting with the clock as it seems to do if
two instances are running, it does consume a lot of cpu time,
according to experiences reported on this list.  But it's possible
that timesync is wrestling with the virtual executive rather than with
another instance of itself.

Would it hurt you to run without timesync?

++L

Re: [9fans] lguest on 2.6.25

[John Soros]

hello,

On Mon, 25 Aug 2008 20:54:53 +0200
lucio@proxima.alt.za wrote:

> > Well, i don't think I am starting two timesync, ps a shows only one:
>
> If Xen is anything to go by, time keeping is a problem in
> virtualisation.  And Erik is misguiding you :-)
>
> Thing is, if timesync is wresting with the clock as it seems to do if
> two instances are running, it does consume a lot of cpu time,
> according to experiences reported on this list.  But it's possible
> that timesync is wrestling with the virtual executive rather than with
> another instance of itself.
>
> Would it hurt you to run without timesync?

will try, thanks :-)

>
> ++L
>
>
John

Re: [9fans] lguest on 2.6.25

[John Soros]

Hello.
For one timesync couldn't write to the rtc, so I commented out the lines in cpurc.
Well, here timesync is not the problem, time is reported incorrectly, and I do not really know how to set it. I tried echoing unix time into '#r' and /dev/rtc, with no luck:
$sysname# ls -l /dev/rtc
--rw-rw-r-- r 0 bootes bootes 0 Apr 23 20:43 /dev/rtc
$sysname# echo -n '1219699386' > /dev/rtc
echo: write error: permission denied
(on the hostowners console)
Also cron still spews messages flooding it's log with lines like this:
Aug 26 02:29:41 time went backward
Which might be related to time issues..

rgds


On Mon, 25 Aug 2008 20:54:53 +0200
lucio@proxima.alt.za wrote:

> > Well, i don't think I am starting two timesync, ps a shows only one:
>
> If Xen is anything to go by, time keeping is a problem in
> virtualisation.  And Erik is misguiding you :-)
>
> Thing is, if timesync is wresting with the clock as it seems to do if
> two instances are running, it does consume a lot of cpu time,
> according to experiences reported on this list.  But it's possible
> that timesync is wrestling with the virtual executive rather than with
> another instance of itself.
>
> Would it hurt you to run without timesync?
>
> ++L
>
>

Re: [9fans] lguest on 2.6.25

[ron minnich]

I just realized that even one timesync is too much. You should not
run any at all. The hardware clock is set from Linux and I don't even
allow it to be set. It makes no sense to do that.

So don't let timesync run.

thanks

ron

[9fans] Anyone handy with Alpha assembler?

[Benjamin Huntsman]

[-- Attachment #1: Type: text/plain, Size: 606 bytes --]

Anyone around here still familiar with Alpha assembler (and the Alpha kernel in general) willing to point me in the right direction?

Supposing one wanted to implement instruction emulation for the BWX extensions, etc, like Tru64 and OpenVMS do, so that you can run the same binaries on EV4 and EV5, where would be the best place to hook in?  illegal0 in /sys/src/9/alphapc/l.s or illegal in /sys/src/9/alphapc/trap.c?  

Furthermore, how would one obtain the faulting instruction?  Best I can tell, it's the Ureg *ur passed to illegal in trap.c or 8(R30) from illegal0.

Thanks in advance!

-Ben

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2747 bytes --]

Re: [9fans] lguest on 2.6.25

[John Soros]

Ok, still, it would be great to know how to set the time, as my time is way off (by more than 4 hours).
Best++
John

On Mon, 25 Aug 2008 15:44:39 -0700
"ron minnich" <rminnich@gmail.com> wrote:http://www.unixtimestamp.com/

> I just realized that even one timesync is too much. You should not
> run any at all. The hardware clock is set from Linux and I don't even
> allow it to be set. It makes no sense to do that.
>
> So don't let timesync run.
>
> thanks
>
> ron
>

Re: [9fans] Anyone handy with Alpha assembler?

[Paweł Lasek]

On Tue, Aug 26, 2008 at 01:53, Benjamin Huntsman
<BHuntsman@mail2.cu-portland.edu> wrote:
> Anyone around here still familiar with Alpha assembler (and the Alpha kernel in general) willing to point me in the right direction?
>
> Supposing one wanted to implement instruction emulation for the BWX extensions, etc, like Tru64 and OpenVMS do, so that you can run the same binaries on EV4 and EV5, where would be the best place to hook in?  illegal0 in /sys/src/9/alphapc/l.s or illegal in /sys/src/9/alphapc/trap.c?
>
> Furthermore, how would one obtain the faulting instruction?  Best I can tell, it's the Ureg *ur passed to illegal in trap.c or 8(R30) from illegal0.
>
> Thanks in advance!
>
> -Ben
>

I think trap.c would be easier to work with or extend to other
instructions, l.s might give better performance. PALcode would be
probably the best option if it was properly patched during boot, but I
don't know where one might get apropriate SDK nowadays.

Anyway, If you want to check your code on an old Avanti-based EV45
Alpha, I am of service (unless I'll have to get rid of it when I move
to Scotland...)

Good luck with Alpha hacking, and remember about memory barriers...
("Program Counter is not reliable source of information about which
instruction caused the exception" - It's like a mantra in Alpha
manuals...)

-- 
Paweł Lasek

Re: [9fans] Anyone handy with Alpha assembler?

[Benjamin Huntsman]

[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]

>I think trap.c would be easier to work with or extend to other
>instructions, l.s might give better performance. 

That was my concern as well.  The Alpha compiler doesn't optimize much.  Not that optimization is going to matter much on an EV4.
The problem I'm running into now is that by the time we get to the illegal routine in trap.c, obtaining the faulting instruction isn't so easy.  From the Alpha Architecture Reference, 19.4.2:

"...The saved PC at(SP+00) is the address of the instruction after the instruction that 
caused the bpt, bugchk, gentrap, and opDec synchronous traps."

So it looks like trap() in trap.c doesn't actually get passed the faulty instruction, but just the contents o a0...a2, etc.  I'm thinking the best way to do this without making sweeping (and slow) changes will be to test for and potentially jump to the emulations from illegal0 in l.s, and let the existing code handle the exceptions.

>PALcode would be probably the best option if it was properly patched during boot, but I
>don't know where one might get apropriate SDK nowadays.

I've got the EBSDK, which was the PALCode developer's kit from the AlphaPC boards.  I don't think there's any pressing need to patch up the PALCode though.  The OSF/1 PALCode that Plan 9 runs with is already designed for UNIX-like systems.  Besides, since they're all implementation-specific, it'd be a bad idea to try to run the EBSDK PALCode on a GS-series machine, should anyone want to run Plan 9 on one in the future. :)

>Good luck with Alpha hacking, and remember about memory barriers...
>("Program Counter is not reliable source of information about which
>instruction caused the exception" - It's like a mantra in Alpha
>manuals...)

Thanks for the tip!  I'll keep it in mind.

-Ben

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3743 bytes --]

Re: [9fans] Anyone handy with Alpha assembler?

[Paweł Lasek]

On Tue, Aug 26, 2008 at 19:56, Benjamin Huntsman
<BHuntsman@mail2.cu-portland.edu> wrote:
>>I think trap.c would be easier to work with or extend to other
>>instructions, l.s might give better performance.
>
> That was my concern as well.  The Alpha compiler doesn't optimize much.  Not that optimization is going to matter much on an EV4.

Well, even on EV4 it could matter. At least I don't remember Alpha
having any real cache-coherency (or memory coheency at all), also EV4
and EV5 which don't have BWX can get much higher speed from using
8-byte aligned data, as well as sticking to 64-bit data where
possible. All those masking operations are probably slowing the code
much.

> I've got the EBSDK, which was the PALCode developer's kit from the AlphaPC boards.  I don't think there's any pressing need to patch up the PALCode though.  The OSF/1 PALCode that Plan 9 runs with is already designed for UNIX-like systems.  Besides, since they're all implementation-specific, it'd be a bad idea to try to run the EBSDK PALCode on a GS-series machine, should anyone want to run Plan 9 on one in the future. :)

Well, the code for updating PALcode probably should be in bootloader
anyway, and HWPRB *does* report processor type, doesn't it? Patching
only "illegal instruction trap" should be enough. As for GS-series, at
my current job we still have some GS1280 (those were EV7z?) Pity I
wouldn't be able to play with those machines....

And could you share EBSDK? If the license permits, of course.

> -Ben
>



-- 
Paweł Lasek

Re: [9fans] Anyone handy with Alpha assembler?

[Benjamin Huntsman]

[-- Attachment #1: Type: text/plain, Size: 227 bytes --]

>And could you share EBSDK? If the license permits, of course.

If others here are interested, I can review the license and share what bits I can.  Most of it is under the BSD license, though there are parts that are not.  

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2739 bytes --]

Re: [9fans] lguest on 2.6.25

[Alex Lee]

On Tue, Aug 26, 2008 at 1:44 AM, John Soros <sorosj@gmail.com> wrote:
> Ok, still, it would be great to know how to set the time, as my time is way off (by more than 4 hours).
> Best++
> John

Hi again,

A couple of updates: I'm getting the same cron messages and time
problems that John is seeing. I've made sure that timesync isn't
running. My lguest time is about 3.5 hours ahead of host time.

As for the load issue: The full cpu usage that I was seeing earlier
actually stops after a several minutes.

After booting, ^T^Tp shows genrandom as Running. Several minutes later
the cpu usage drops to near idle, and genrandom goes to Wakeme. Then
every now and then (I'm not sure if anything in particular triggers
it, or if just randomly happens) I see the cpu usage jump again, and I
can see that genrandom is once again Running. Then after several
minutes it stops again.

When genrandom is running, stats shows a load of around 3000.
Otherwise, load is always around 2000.

The problem looks similar to this:
http://9fans.net/archive/2006/03/588 -- except that the lguest
instance works fine while genrandom is running. Is this genrandom
behavior anything out of the ordinary?

Alex


--
Alex Lee <alexlee@uchicago.edu>

Re: [9fans] lguest on 2.6.25

[ron minnich]

On Wed, Aug 27, 2008 at 7:28 PM, Alex Lee <alexlee@uchicago.edu> wrote:

> The problem looks similar to this:
> http://9fans.net/archive/2006/03/588 -- except that the lguest
> instance works fine while genrandom is running. Is this genrandom
> behavior anything out of the ordinary?
>

I don't think so. Genrandom make me want to look at using the hardware
RNGs a few years ago, but then Intel killed firmware hub and the whole
idea kind of went away.

ron

Re: [9fans] lguest on 2.6.25

[ron minnich]

On Mon, Aug 25, 2008 at 11:44 PM, John Soros <sorosj@gmail.com> wrote:
> Ok, still, it would be great to know how to set the time, as my time is way off (by more than 4 hours).

What's the time on your host (Linux) look like? Are you sure it's not
a time zone setup issue?

Is it always four hours? It should not be drifting.

ron

Re: [9fans] lguest on 2.6.25

[John Soros]

Hi again, 9fans

On Wed, 27 Aug 2008 21:28:42 -0500
"Alex Lee" <alexlee@uchicago.edu> wrote:

> On Tue, Aug 26, 2008 at 1:44 AM, John Soros <sorosj@gmail.com> wrote:
> > Ok, still, it would be great to know how to set the time, as my time is way off (by more than 4
> > hours). Best++
> > John
>
> Hi again,
>
> A couple of updates: I'm getting the same cron messages and time
> problems that John is seeing. I've made sure that timesync isn't
> running. My lguest time is about 3.5 hours ahead of host time.
>
> As for the load issue: The full cpu usage that I was seeing earlier
> actually stops after a several minutes.
This is what i've been experiencing. This is fine, from the linux host, the guest takes a lot of load in the begginning, but then it calms down, and the load only goes up once in a while. From inside the guest, though, the load looks like it's maxed out all the tim. This might be because of time issues, though.
As for the timezone issues, well, i have my timezon set up properly on the host, and in plan9 I did cp /adm/timezon/CET /adm/timezone/local.
>
> After booting, ^T^Tp shows genrandom as Running. Several minutes later
> the cpu usage drops to near idle, and genrandom goes to Wakeme. Then
> every now and then (I'm not sure if anything in particular triggers
> it, or if just randomly happens) I see the cpu usage jump again, and I
> can see that genrandom is once again Running. Then after several
> minutes it stops again.
>
> When genrandom is running, stats shows a load of around 3000.
> Otherwise, load is always around 2000.
>
> The problem looks similar to this:
> http://9fans.net/archive/2006/03/588 -- except that the lguest
> instance works fine while genrandom is running. Is this genrandom
> behavior anything out of the ordinary?
>
> Alex
>
>
John

Re: [9fans] lguest on 2.6.25

[Richard Miller]

> As for the load issue: The full cpu usage that I was seeing earlier
> actually stops after a several minutes.
> ...
> Is this genrandom
> behavior anything out of the ordinary?

/dev/random normally runs at 100% cpu after booting, and whenever
its queue of random bytes is getting empty.  Since it uses the
clock to produce entropy, this might take longer than usual if
your clock is behaving strangely.

Re: [9fans] lguest on 2.6.25

[erik quanstrom]

>
> When genrandom is running, stats shows a load of around 3000.
> Otherwise, load is always around 2000.
>

what are the other two processes that are constantly
running?

- erik

Re: [9fans] lguest on 2.6.25

[erik quanstrom]

>
> I don't think so. Genrandom make me want to look at using the hardware
> RNGs a few years ago, but then Intel killed firmware hub and the whole
> idea kind of went away.
>

via has release the padlock documentation.

unfortunately one needs to enable floating point
and sse to use the padlock rng.

on reading that, i decided that software rng
wasn't as slow or as important as i'd remembered.

there's also the problem of ensuring that the
hardware rng is at least as good as plan 9's.

- erik

Re: [9fans] lguest on 2.6.25

[ron minnich]

this is weird. So, to recap, your timezone is set correctly, and yet
you are four hours off.

A useful thing to do is cat /dev/time and see how it changes.

The time from lguest is simple: you read a 64-bit # which is time.
It's just like Xen that way.

Also, try this to test another issue:

date && sleep 60 && date

Two things: should take 60 seconds by the watch and the two dates
should report 60 seconds apart.

Do they?

ron

Re: [9fans] lguest on 2.6.25

[John Soros]

i think it is weird too,
as far as i could mesure it, it took 60 seconds, here it is:
cpu% date && sleep 60 && date
Thu Aug 28 22:19:21 CET 2008
Thu Aug 28 22:20:22 CET 2008
cpu%
My timezones are all set up to be CET (host and plan9 guest), the hardware clock is set to UTC. I am running vanilla 2.6.25 kernel, on a gentoo system.
Thank you for helping debug this problem, is there any more info I can give to help this process?

John

On Thu, 28 Aug 2008 08:38:56 -0700
"ron minnich" <rminnich@gmail.com> wrote:

> this is weird. So, to recap, your timezone is set correctly, and yet
> you are four hours off.
>
> A useful thing to do is cat /dev/time and see how it changes.
>
> The time from lguest is simple: you read a 64-bit # which is time.
> It's just like Xen that way.
>
> Also, try this to test another issue:
>
> date && sleep 60 && date
>
> Two things: should take 60 seconds by the watch and the two dates
> should report 60 seconds apart.
>
> Do they?
>
> ron
>

Re: [9fans] lguest on 2.6.25

[erik quanstrom]

any chance that the rtc is being kept in local
time and not utc?

- erik

Re: [9fans] lguest on 2.6.25

[Alex Lee]

On Thu, Aug 28, 2008 at 10:38 AM, ron minnich <rminnich@gmail.com> wrote:
> this is weird. So, to recap, your timezone is set correctly, and yet
> you are four hours off.
>
> A useful thing to do is cat /dev/time and see how it changes.
>
> The time from lguest is simple: you read a 64-bit # which is time.
> It's just like Xen that way.
>
> Also, try this to test another issue:
>
> date && sleep 60 && date
>
> Two things: should take 60 seconds by the watch and the two dates
> should report 60 seconds apart.
>
> Do they?
>
> ron

I've doublechecked the timezone setting, and it appears to be correct.
The 'date' test seems to work fine:

# date && sleep 60 && date
Thu Aug 28 15:52:19 CDT 2008
Thu Aug 28 15:53:19 CDT 2008

Within a second of one another, I ran:

lguest: cat /dev/time
 1219956674   1219956674748050432   1219956674748050432            4294967296
host: date +%s
1219943774

So lguest is 12900 seconds ahead (= 215 minutes, = 3 hrs 35 minutes).
John, are you getting the same?

Best,
Alex


--
Alex Lee <alexlee@uchicago.edu>

Re: [9fans] lguest on 2.6.25

[Alex Lee]

[-- Attachment #1: Type: text/plain, Size: 783 bytes --]

On Thu, Aug 28, 2008 at 6:55 AM, erik quanstrom <quanstro@coraid.com> wrote:
>> When genrandom is running, stats shows a load of around 3000.
>> Otherwise, load is always around 2000.
>
> what are the other two processes that are constantly
> running?
>
> - erik

Seems like it might be fossil, but I'm not really sure. Here are two
process listings, one while genrandom is running, one when it isn't.
(File is attached. Sorry if I'm missing something obvious in the
listings!)

Oh, and probably unrelated: The console spits out the following lines
pretty regularly:

LGATTACH edev c0440b90 ctlr c0440dd0
ETHERIN: devno 3 ring 0 irq 34
ETHEROUT: devno 3 ring 0 irq 35

Thanks again for the help and suggestions,

Alex


--
Alex Lee <alexlee@uchicago.edu>

[-- Attachment #2: lguest_processes.txt --]
[-- Type: text/plain, Size: 22298 bytes --]

GENRANDOM RUNNING
(load is around 3)

  1:      init pc     89ec dbgpc     89ec     Await (Wakeme) ut 1 st 0 bss 17000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
  2: genrandom pc c015412e dbgpc        0   Running (Running) ut 323 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c01543d7 pri 1
  3:     alarm pc        0 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 35:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 4 st 12 bss d38000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 13: rxmitproc pc     31a6 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 14:  factotum pc    192d3 dbgpc    192d3     Pread (Wakeme) ut 0 st 0 bss 42000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 16:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 17:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 18:    fossil pc    2942f dbgpc    2942f     Pread (Wakeme) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 19:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 20:    fossil pc    2942f dbgpc    2942f     Pread (Wakeme) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 21:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 22:    fossil pc    2942f dbgpc    2942f     Pread (Wakeme) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 23:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 2 bss d38000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 24:    fossil pc    29401 dbgpc    29401     Sleep (Wakeme) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 25:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 26:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 27:    fossil pc    29401 dbgpc    29401     Sleep (Wakeme) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 28:    fossil pc    29401 dbgpc    29401     Sleep (Wakeme) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 29: #I0tcpack pc        0 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 30:    fossil pc    2943f dbgpc    2943f      Open (Wakeme) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 31:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 1 st 11 bss d38000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 32:    fossil pc    2942f dbgpc    2942f     Pread (Wakeme) ut 1 st 7 bss d38000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 33:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 34:    fossil pc    2942f dbgpc    2942f     Pread (Wakeme) ut 0 st 0 bss d38000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 36:     pager pc        0 dbgpc        0      Idle (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 88:        rc pc    1478b dbgpc    1478b     Pread (Wakeme) ut 0 st 1 bss 3e000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 89:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 62:    listen pc     b562 dbgpc     b562     Await (Wakeme) ut 0 st 1 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 42:    mntgen pc     8264 dbgpc     8264     Pread (Wakeme) ut 1 st 0 bss 1f000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 45:etherread4 pc        0 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 46:recvarpproc pc        0 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 47:etherread6 pc        0 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 49:        cs pc    10617 dbgpc    10617     Pread (Wakeme) ut 0 st 3 bss 2c000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 56: secstored pc     9421 dbgpc     9421      Open (Wakeme) ut 0 st 0 bss 25000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 58:     keyfs pc     e7c5 dbgpc     e7c5     Pread (Wakeme) ut 0 st 0 bss 1a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 90:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 61:      cron pc     5812 dbgpc     5812     Sleep (Wakeme) ut 0 st 0 bss 2c000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 63:    listen pc     b562 dbgpc     b562     Await (Wakeme) ut 0 st 0 bss 26000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 66:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 26000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 68:       dns pc    1ff39 dbgpc    1ff39     Await (Wakeme) ut 1 st 2 bss 62000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 69:       dns pc    1ff11 dbgpc    1ff11     Pread (Wakeme) ut 0 st 0 bss 62000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 71:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 1 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 73:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 85:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 91:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 87:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 77:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 84:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 92:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 80:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 81:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 82:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 83:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 93:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 94:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 97:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 1 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 96:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 98:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 1 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 99:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
100:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10

bootes            1    0:00   0:00       88K Await    init
bootes            2    0:03   0:00        0K Ready    genrandom
bootes            3    0:00   0:00        0K Wakeme   alarm
bootes           13    0:00   0:00        0K Wakeme   rxmitproc
bootes           14    0:00   0:00      260K Pread    factotum
bootes           16    0:00   0:00    13532K Rendez   fossil
bootes           17    0:00   0:00    13532K Rendez   fossil
bootes           18    0:00   0:00    13532K Pread    fossil
bootes           19    0:00   0:00    13532K Rendez   fossil
bootes           20    0:00   0:00    13532K Pread    fossil
bootes           21    0:00   0:00    13532K Rendez   fossil
bootes           22    0:00   0:00    13532K Pread    fossil
bootes           23    0:00   0:00    13532K Rendez   fossil
bootes           24    0:00   0:00    13532K Sleep    fossil
bootes           25    0:00   0:00    13532K Rendez   fossil
bootes           26    0:00   0:00    13532K Rendez   fossil
bootes           27    0:00   0:00    13532K Sleep    fossil
bootes           28    0:00   0:00    13532K Sleep    fossil
bootes           29    0:00   0:00        0K Wakeme   #I0tcpack
bootes           30    0:00   0:00    13532K Open     fossil
bootes           31    0:00   0:00    13532K Rendez   fossil
bootes           32    0:00   0:00    13532K Pread    fossil
bootes           33    0:00   0:00    13532K Rendez   fossil
bootes           34    0:00   0:00    13532K Pread    fossil
bootes           35    0:00   0:00    13532K Rendez   fossil
bootes           36    0:00   0:00        0K Idle     pager
bootes           42    0:00   0:00      120K Pread    mntgen
bootes           45    0:00   0:00        0K Wakeme   etherread4
bootes           46    0:00   0:00        0K Wakeme   recvarpproc
bootes           47    0:00   0:00        0K Wakeme   etherread6
bootes           49    0:00   0:00      172K Pread    cs
bootes           56    0:00   0:00      144K Open     secstored
bootes           58    0:00   0:00      100K Pread    keyfs
bootes           61    0:00   0:00      172K Sleep    cron
none             62    0:00   0:00      160K Await    listen
bootes           63    0:00   0:00      148K Await    listen
bootes           66    0:00   0:00      148K Open     listen
bootes           68    0:00   0:00      388K Await    dns
bootes           69    0:00   0:00      388K Pread    dns
none             71    0:00   0:00      160K Open     listen
none             73    0:00   0:00      160K Open     listen
none             77    0:00   0:00      160K Open     listen
none             80    0:00   0:00      160K Open     listen
none             81    0:00   0:00      160K Open     listen
none             82    0:00   0:00      160K Open     listen
none             83    0:00   0:00      160K Open     listen
none             84    0:00   0:00      160K Open     listen
none             85    0:00   0:00      160K Open     listen
none             87    0:00   0:00      160K Open     listen
bootes           88    0:00   0:00      244K Await    rc
none             89    0:00   0:00      160K Open     listen
none             90    0:00   0:00      160K Open     listen
none             91    0:00   0:00      160K Open     listen
none             92    0:00   0:00      160K Open     listen
none             93    0:00   0:00      160K Open     listen
none             94    0:00   0:00      160K Open     listen
none             96    0:00   0:00      160K Open     listen
none             97    0:00   0:00      160K Open     listen
none             98    0:00   0:00      160K Open     listen
none             99    0:00   0:00      160K Open     listen
none            100    0:00   0:00      160K Open     listen
bootes          104    0:00   0:00      188K Pread    ps

GENRANDOM NOT RUNNING
(load is around 2)

  1:      init pc     89ec dbgpc     89ec     Await (Wakeme) ut 1 st 0 bss 17000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
  2: genrandom pc c0105802 dbgpc        0    Wakeme (Wakeme) ut 4137 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 0
  3:     alarm pc        0 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 35:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 4 st 17 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 3
 13: rxmitproc pc     31a6 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 14:  factotum pc    192d3 dbgpc    192d3     Pread (Wakeme) ut 0 st 0 bss 42000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 16:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 17:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 18:    fossil pc    2942f dbgpc    2942f     Pread (Wakeme) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 19:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 20:    fossil pc    2942f dbgpc    2942f     Pread (Wakeme) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 21:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 22:    fossil pc    2942f dbgpc    2942f     Pread (Wakeme) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 23:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 4 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 24:    fossil pc    29401 dbgpc    29401     Sleep (Wakeme) ut 0 st 2 bss d3a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 25:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 26:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 2 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 27:    fossil pc    29401 dbgpc    29401     Sleep (Wakeme) ut 3 st 7 bss d3a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 1
 28:    fossil pc    29401 dbgpc    29401     Sleep (Wakeme) ut 0 st 2 bss d3a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 29: #I0tcpack pc        0 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 30:    fossil pc    2943f dbgpc    2943f      Open (Wakeme) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 31:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 5 st 16 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 32:    fossil pc    2942f dbgpc    2942f     Pread (Wakeme) ut 7 st 13 bss d3a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 33:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 13
 34:    fossil pc    2942f dbgpc    2942f     Pread (Wakeme) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 36:     pager pc        0 dbgpc        0      Idle (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 88:        rc pc    1478b dbgpc    1478b     Pread (Wakeme) ut 0 st 1 bss 3e000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 89:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 62:    listen pc     b562 dbgpc     b562     Await (Wakeme) ut 0 st 1 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 42:    mntgen pc     8264 dbgpc     8264     Pread (Wakeme) ut 1 st 0 bss 1f000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 45:etherread4 pc        0 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 46:recvarpproc pc        0 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 47:etherread6 pc        0 dbgpc        0    Wakeme (Wakeme) ut 0 st 0 bss 0 qpc 0 nl 0 nd 0 lpc c0154df8 pri 13
 49:        cs pc    10617 dbgpc    10617     Pread (Wakeme) ut 2 st 7 bss 2c000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 56: secstored pc     9421 dbgpc     9421      Open (Wakeme) ut 0 st 0 bss 25000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 58:     keyfs pc     e7c5 dbgpc     e7c5     Pread (Wakeme) ut 0 st 0 bss 1a000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 90:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 61:      cron pc     5812 dbgpc     5812     Sleep (Wakeme) ut 0 st 0 bss 2c000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 63:    listen pc     b562 dbgpc     b562     Await (Wakeme) ut 0 st 0 bss 26000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 66:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 26000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 68:       dns pc    1ff39 dbgpc    1ff39     Await (Wakeme) ut 1 st 2 bss 62000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 69:       dns pc    1ff11 dbgpc    1ff11     Pread (Wakeme) ut 2 st 0 bss 62000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 71:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 1 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 73:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 85:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 91:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 87:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 77:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 84:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 92:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc c0158197 nl 0 nd 0 lpc c0154df8 pri 10
 80:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 81:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 82:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 83:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 93:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 94:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 97:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 1 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 96:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 98:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 1 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
 99:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
100:    listen pc     4a16 dbgpc     4a16      Open (Wakeme) ut 0 st 0 bss 29000 qpc 0 nl 0 nd 0 lpc c0154df8 pri 10
121:    fossil pc    379d8 dbgpc    379d8    Rendez (Rendez) ut 0 st 0 bss d3a000 qpc 0 nl 0 nd 0 lpc c016061f pri 13

bootes            1    0:00   0:00       88K Await    init
bootes            2    0:41   0:00        0K Wakeme   genrandom
bootes            3    0:00   0:00        0K Wakeme   alarm
bootes           13    0:00   0:00        0K Wakeme   rxmitproc
bootes           14    0:00   0:00      260K Pread    factotum
bootes           16    0:00   0:00    13540K Rendez   fossil
bootes           17    0:00   0:00    13540K Rendez   fossil
bootes           18    0:00   0:00    13540K Pread    fossil
bootes           19    0:00   0:00    13540K Rendez   fossil
bootes           20    0:00   0:00    13540K Pread    fossil
bootes           21    0:00   0:00    13540K Rendez   fossil
bootes           22    0:00   0:00    13540K Pread    fossil
bootes           23    0:00   0:00    13540K Rendez   fossil
bootes           24    0:00   0:00    13540K Sleep    fossil
bootes           25    0:00   0:00    13540K Rendez   fossil
bootes           26    0:00   0:00    13540K Rendez   fossil
bootes           27    0:00   0:00    13540K Sleep    fossil
bootes           28    0:00   0:00    13540K Sleep    fossil
bootes           29    0:00   0:00        0K Wakeme   #I0tcpack
bootes           30    0:00   0:00    13540K Open     fossil
bootes           31    0:00   0:00    13540K Rendez   fossil
bootes           32    0:00   0:00    13540K Pread    fossil
bootes           33    0:00   0:00    13540K Rendez   fossil
bootes           34    0:00   0:00    13540K Pread    fossil
bootes           35    0:00   0:00    13540K Rendez   fossil
bootes           36    0:00   0:00        0K Idle     pager
bootes           42    0:00   0:00      120K Pread    mntgen
bootes           45    0:00   0:00        0K Wakeme   etherread4
bootes           46    0:00   0:00        0K Wakeme   recvarpproc
bootes           47    0:00   0:00        0K Wakeme   etherread6
bootes           49    0:00   0:00      172K Pread    cs
bootes           56    0:00   0:00      144K Open     secstored
bootes           58    0:00   0:00      100K Pread    keyfs
bootes           61    0:00   0:00      172K Sleep    cron
none             62    0:00   0:00      160K Await    listen
bootes           63    0:00   0:00      148K Await    listen
bootes           66    0:00   0:00      148K Open     listen
bootes           68    0:00   0:00      388K Await    dns
bootes           69    0:00   0:00      388K Pread    dns
none             71    0:00   0:00      160K Open     listen
none             73    0:00   0:00      160K Open     listen
none             77    0:00   0:00      160K Open     listen
none             80    0:00   0:00      160K Open     listen
none             81    0:00   0:00      160K Open     listen
none             82    0:00   0:00      160K Open     listen
none             83    0:00   0:00      160K Open     listen
none             84    0:00   0:00      160K Open     listen
none             85    0:00   0:00      160K Open     listen
none             87    0:00   0:00      160K Open     listen
bootes           88    0:00   0:00      244K Await    rc
none             89    0:00   0:00      160K Open     listen
none             90    0:00   0:00      160K Open     listen
none             91    0:00   0:00      160K Open     listen
none             92    0:00   0:00      160K Open     listen
none             93    0:00   0:00      160K Open     listen
none             94    0:00   0:00      160K Open     listen
none             96    0:00   0:00      160K Open     listen
none             97    0:00   0:00      160K Open     listen
none             98    0:00   0:00      160K Open     listen
none             99    0:00   0:00      160K Open     listen
none            100    0:00   0:00      160K Open     listen
bootes          121    0:00   0:00    13540K Rendez   fossil
bootes          145    0:00   0:00      188K Pread    ps

Re: [9fans] lguest on 2.6.25

[John Soros]

yep, i get exactly the same:
plan9:
% date
Thu Aug 28 23:40:17 CET 2008
Linux host:
$ date
Thu Aug 28 20:06:02 CEST 2008
even the time difference seems to be the same. strange!

rgds
John

On Thu, 28 Aug 2008 12:24:32 -0500
"Alex Lee" <alexlee@uchicago.edu> wrote:

> On Thu, Aug 28, 2008 at 10:38 AM, ron minnich <rminnich@gmail.com> wrote:
> > this is weird. So, to recap, your timezone is set correctly, and yet
> > you are four hours off.
> >
> > A useful thing to do is cat /dev/time and see how it changes.
> >
> > The time from lguest is simple: you read a 64-bit # which is time.
> > It's just like Xen that way.
> >
> > Also, try this to test another issue:
> >
> > date && sleep 60 && date
> >
> > Two things: should take 60 seconds by the watch and the two dates
> > should report 60 seconds apart.
> >
> > Do they?
> >
> > ron
>
> I've doublechecked the timezone setting, and it appears to be correct.
> The 'date' test seems to work fine:
>
> # date && sleep 60 && date
> Thu Aug 28 15:52:19 CDT 2008
> Thu Aug 28 15:53:19 CDT 2008
>
> Within a second of one another, I ran:
>
> lguest: cat /dev/time
>  1219956674   1219956674748050432   1219956674748050432            4294967296
> host: date +%s
> 1219943774
>
> So lguest is 12900 seconds ahead (= 215 minutes, = 3 hrs 35 minutes).
> John, are you getting the same?
>
> Best,
> Alex
>
>