[9fans] replica problem

[9fans] replica problem

[cej]

>> usage: 'srv -Adp replica'
>> 
>> however , -Adp didn't work either, I had to remove all options, and voila!
>Did you use a very old version of fossil?

maybe of June, or so?

>permission checking and allow arbitrary changes to owner and user
>fields when doing a pull.
>
>The d flag causes fossil to delete a service. That's definitely not
>wanted for the clientmount. ;-) You can use it after the pull was
>successful.

i did pull -s, restored config files, and it seems to work. should try another pull
now, though...

[nice to see the development moving so rapidly forward, indeed!]

++pac

---
Odchozí zpráva neobsahuje viry.
Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz).
Verze: 6.0.786 / Virová báze: 532 - datum vydání: 29. 10. 2004
 

[9fans] assembler scheduling

[Tim Newsham]

Eek!  The assembler messed with my code.  Here's the original going
into ka.  Notice the *** line:

TEXT	syslink(SB), $-4
	MOVW	R2, R10
	MOVW	$setSB(SB), R2
	MOVW	$mach0(SB), R14
	MOVW	(4*2)(R14), R13		/* m->proc */
	MOVW	(4*2)(R13), R9		/* m->proc->kstack */
	MOVW	R1, (KSTACK-UREGSZ+4*1)(R9)	/* SP */
	MOVW	R10, (KSTACK-UREGSZ+4*2)(R9)	/* SB */
	MOVW	R5, (KSTACK-UREGSZ+4*5)(R9)	/* PROC */
	MOVW	R6, (KSTACK-UREGSZ+4*6)(R9)	/* MACH */
	ADD		$(KSTACK-UREGSZ), R9, R1
	MOVW	R13, R5
	MOVW	R14, R6

	MOVW	R2, (4*2)(R1)			/* SB */
	MOVW	R3, (4*3)(R1)			/* global register */
	MOVW	R4, (4*4)(R1)			/* global register */
	MOVW	R7, (4*7)(R1)			/* syscall # */
	MOVW	TBR, R20
	MOVW	R20, (4*(32+1))(R1)		/* TBR */
	AND		$~0x1F, R19
	MOVW	R19, (4*(32+2))(R1)		/* PSR */
	MOVW	R18, (4*(32+3))(R1)		/* nPC */
	MOVW	R17, (4*(32+4))(R1)		/* PC */
***	RESTORE	R0, R0
	/* now our registers R8-R31 are same as before trap */
	MOVW	R15, (4*15)(R1)

	MOVW	$setSB(SB), R2
	MOVW	R1, R7			/* pointer to Ureg */
	SUB		$8, R1
	MOVW	$SYSPSR, R8
	MOVW	R8, PSR
	JMPL	syscall(SB)
	/* R7 contains return value from syscall */

Got turned into:
syslink:                        or      %g0, %g2, %o2
syslink+0x4:                    sethi   %hi(0xe0071400), %sp
syslink+0x8:                    add     %sp, 0x128, %g2
syslink+0xc:                    ld      [%g2+0x46c], %sp
syslink+0x10:                   ld      [%sp+0x8], %o5
syslink+0x14:                   ld      [%o5+0x8], %o1
syslink+0x18:                   st      %g1, [%o1+0xf6c]
syslink+0x1c:                   st      %o2, [%o1+0xf70]
syslink+0x20:                   st      %g5, [%o1+0xf7c]
syslink+0x24:                   st      %g6, [%o1+0xf80]
syslink+0x28:                   add     %o1, 0xf68, %g1
syslink+0x2c:                   or      %g0, %o5, %g5
syslink+0x30:                   or      %g0, %sp, %g6
syslink+0x34:                   st      %g2, [%g1+0x8]
syslink+0x38:                   st      %g3, [%g1+0xc]
syslink+0x3c:                   st      %g4, [%g1+0x10]
syslink+0x40:                   st      %g7, [%g1+0x1c]
syslink+0x44:                   rd      %tbr, %l4
syslink+0x48:                   st      %l4, [%g1+0x84]
syslink+0x4c:                   and     %l3, 0xffffffe0, %l3
syslink+0x50:                   st      %l3, [%g1+0x88]
syslink+0x54:                   st      %l2, [%g1+0x8c]
syslink+0x58:                   st      %l1, [%g1+0x90]
syslink+0x5c:                   st      %o7, [%g1+0x3c]
syslink+0x60:                   sethi   %hi(0xe0071400), %sp
syslink+0x64:                   add     %sp, 0x128, %g2
syslink+0x68:                   or      %g0, %g1, %g7
syslink+0x6c:                   sub     %g1, 0x8, %g1
syslink+0x70:                   sethi   %hi(0x1c00), %sp
syslink+0x74:                   add     %sp, 0x3a0, %o0
syslink+0x78:                   wr      %o0, 0x0, %psr
syslink+0x7c:                   call    p9:syscall
syslink+0x80:       ***         restore %g0, %g0, %g0
syslink+0x84:                   add     %g1, 0x8, %g1
syslink+0x88:                   ld      [%g1+0x88], %o0

Notice it moved the RESTORE instruction into the delay slot of the
call.  In this case this causes bad things to happen, since RESTORE
changes the registers (I guess since ka doesn't use windows it is
unaware of this special meaning of restore).

How can I override this scheduling of the RESTORE instruction?
(I'd prefer to let it continue to schedule other statements and
not completely turn of scheduling).

Tim N.

Re: [9fans] assembler scheduling

[Charles Forsyth]

>>Eek!  The assembler messed with my code.  Here's the original going

actually, it's the loader kl that does scheduling.
use NOSCHED and SCHED pseudo-ops in ka (see /sys/doc/asm.ps, not
that there are many more details)