Re: KSE-MIII ready for commit

On Fri, 28 Jun 2002, David O'Brien wrote: > On Fri, Jun 28, 2002 at 11:39:29PM -0700, Julian Elischer wrote: > > Jake just checked something in that looks like it may be relevant. > > Yes it was. `thediff' on sparc64 is solid. > Still some ast funkiness on Alpha

geom breaks current

current as of an hour or so ago.. ref3> make cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wno-format -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ip

Re: KSE-MIII ready for commit

you are missing kern_thread.c On Fri, 28 Jun 2002, David O'Brien wrote: > Not buildable on sparc64: > > linking kernel.debug > procfs_ctl.o: In function `procfs_control': > procfs_ctl.o(.text+0x56c): undefined reference to `thread_unsuspend' > init_main.o: In function `proc0_init': > init_main

Re: KSE-MIII ready for commit

You must have something wrong in the MD code that jake added.. I don't do anything in that code or with any allignments none of these functions have been altered.. Jake said he had it going... On Fri, 28 Jun 2002, David O'Brien wrote: > On Fri, Jun 28, 2002 at 11:02:51PM -0700, David O'Brien

Re: KSE-MIII ready for commit

Jake just checked something in that looks like it may be relevant. On Fri, 28 Jun 2002, David O'Brien wrote: > On Fri, Jun 28, 2002 at 11:02:51PM -0700, David O'Brien wrote: > > Not buildable on sparc64: > > User error. Now I get: > > Mounting root from ufs:/dev/ad0a > WARNING: / was not pro

KSE times

Some people have suggested to me that adding threads to the system would harm performance on our normal applications.. Here are times for 6 buildworlds. First 3 buildworlds on a NON KSE kernel: --- 3394.762u 1465.676s 1:27:45.19 92.3%

something funny with soft updates?

I did a small test today to try test the speed impact of the KSE test. during this, I noticed that soft updates is not having it's usual performance increaseing effect.. Normal kernel, soft updates: 1387.881u 603.392s 35:48.63 92.6% 2694+2248k 12424+3310io 3587pf+0w KSE kernel, soft update

Re: KSE-MIII ready for commit

be here in case things explode. > : > : > :On Thu, 27 Jun 2002, David O'Brien wrote: > : > :> On Thu, Jun 27, 2002 at 08:18:17PM -0700, Julian Elischer wrote: > :> > > :> > I won't be absent after that, just busier. > :> > :> ENOPARSE &

Re: KSE-MIII ready for commit

ok.. but let me know when you have tested it a bit.. David, ifyou want to test this I really suggest that you grab it with cvsup as a whole rather than doing small patches one at a time... (check my web page for how to do that..) Matt, I just did a sync.. On Thu, 27 Jun 2002, David O'Brien wrot

Re: KSE-MIII ready for commit

wrote: > On Thu, Jun 27, 2002 at 08:18:17PM -0700, Julian Elischer wrote: > > > > I won't be absent after that, just busier. > > ENOPARSE > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

some improbable results..

>From the annals of the journals of the "Society of Improbable Research" I bring you the following statistics.. -current kernel and userland: buildworld: 3951.612u 1556.534s 1:50:43.30 82.9%2627+2535k 47259+23130io 17986pf+0w KSE kernel, -current userland buildworld: 3395.933u 1606.248s

Re: KSE-MIII ready for commit

I won't be absent after that, just busier. On Thu, 27 Jun 2002, David O'Brien wrote: > On Thu, Jun 27, 2002 at 07:50:39PM -0700, Julian Elischer wrote: > > Estimated commit time: (assuming current works at that time) > > will be around 1AM GMT June 29 > &g

KSE-MIII ready for commit

See http://www.freebsd.org/~julian/ for pointers to diffs or other ways of getting the sources.. At this stage it is as good as I can get it right now. It builds world. It runs teh sampel threaded program, it even does both at the same time.. Matt has run it on an SMP machine and there are pat

Re: this ring a bell with anyone?

Ignore this.. pilot error. mismatched acpi module. On Thu, 27 Jun 2002, Julian Elischer wrote: > Using $PIR table, 12 entries at 0xc00f2f70 > npx0: on motherboard To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

this ring a bell with anyone?

Using $PIR table, 12 entries at 0xc00f2f70 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard Fatal trap 12: page fault while in kernel mode fault virtual address = 0x735f6e72 fault code = supervisor read, page not present instruction pointer = 0x8:0xc026be97

Re: interesting: problem with nm?

I think it may be related.. I saw this when I was sufferning from the other problemm make sure you have the pmap fix and then re make buildworld/make installworld when running on a new kernel and see if it goes away. szia! On Thu, 27 Jun 2002, Szilveszter Adam wrote: > On Thu, Jun 27, 2002

Re: What is going on?

no I didn't apply it but Tor just found the problem in the pmap code. On Wed, 26 Jun 2002, walt wrote: > Julian Elischer wrote to FreeBSD-Current: > > > /usr/libexec/ld-elf.so.1: grep: Shared object has no run-time symbol > > table > > This is the same disa

Re: What is going on?

I will add that the file is not really corrupt.. A reboot brings it 'back to life' so it's only corrupt in memory. On Wed, 26 Jun 2002, Julian Elischer wrote: > > After doing a make buildworld, > followed by make installworld and mergemaster. > > The followi

What is going on?

After doing a make buildworld, followed by make installworld and mergemaster. The following 'make buildworld' starts of with: ref4# make buildworld /usr/libexec/ld-elf.so.1: grep: Shared object has no run-time symbol table -- >>> Rebui

UMA/MTX ..last thing stopping KSE M-III

I am seeing the following error messages: ../../../vm/uma_core.c:1331: could sleep with "process lock" locked from ../../../kern/kern_proc.c:258 Though the system is really quite stable now. anyone understand well what this message is trying to say? To Unsubscribe: send mail to [EMAIL PROTE

Re: KSE changes to ps

On Fri, 14 Jun 2002, Juli Mallett wrote: > * Julian Elischer <[EMAIL PROTECTED]> escriurères > > So the question is: what information can PS show > > for a KSE threaded process? > > > > I have been thinking of: > > > > Certainly the f

KSE changes to ps

So the question is: what information can PS show for a KSE threaded process? I have been thinking of: Certainly the first thing to decide it WHAT there is to show.. threads that are in userspace are not visible to ps, or for that matter the kernel, as teh Userland thread scheduler may switch be

KSE MIII kinda-HEADSUP

After some hacking work with others at USENIX, KSE MIII is currently running pretty well on i386. there seems to be a slight issue with alpha and ^Z but it works fine for i386. The test machine has not crashed afer 2+1/2 hours of work at the moment. (not a lot but it's been this stable for sever

Re: Looking for comments on a new utility...

we need to extend this to handle a full thread table per process.. anyone have any ideas on how to do this? Anyone rewriting ps should think about this twist... On 11 Jun 2002, Dag-Erling Smorgrav wrote: > Juli Mallett <[EMAIL PROTECTED]> writes: > > I believe I can get pid, ppid, username (or

Re: Kernel breakage in XE module

the HIDENAME() macro was changed to work with Gcc3.1 (the new compiler) but broke it for the old compiler/assembler. back out the definition in i386/include/asmacros.h to what it was before (it used to use the CONCAT() macro) OR bite the bullet and upgrade to a new -current and get the new comp

uma_core.c:1327: could sleep with "process lock" locked from...

This was in the kernel 3 weeks ago and I see it's still here now.. (sources checked out 1 hour ago) (It's not as common now as it was before though) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Seeking OK to commit KSE MIII

Thanks for looking at it This is not offtopic.. the answer is: No, the code is correct.. here is the logic.. If there are N processors, then there are at most N KSEs (kernel schedulable entities) working to process threads that belong to this KSEGOUP. (kg). If there are N or more threads

Re: Seeking OK to commit KSE MIII-again

On Fri, 31 May 2002, Jake Burkholder wrote: > Apparently, On Fri, May 31, 2002 at 05:49:59PM -0700, > Julian Elischer said words to the effect of; > > > interesting but not exactly brief.. :-) > > > > > > On Fri, 31 May 2002, Jake Burkholder wrote:

Re: Seeking OK to commit KSE MIII-again

interesting but not exactly brief.. :-) On Fri, 31 May 2002, Jake Burkholder wrote: > > The system call stubs in libc are leaf functions; basically just a > trap instruction followed by a return. They do not touch the stack > at all, or change the stack pointer. One of the first few instruct

Re: Seeking OK to commit KSE MIII-again

On Fri, 31 May 2002, Jake Burkholder wrote: [aweful stuff] (always did dislike sparc) jake.. can you show me the sequecne of operations performed on the stack in a syscall before and after the jump to kernel space? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-c

Re: Seeking OK to commit KSE MIII-again

On Fri, 31 May 2002, Bernd Walter wrote: > On Thu, May 30, 2002 at 09:14:33PM +0200, Bernd Walter wrote: > > There are problems with the patchset: fixed This is code that translates the new states to old states for single threaded processes so that 'ps' and friends can continue to report a s

Re: Seeking OK to commit KSE MIII-again

On Thu, 30 May 2002, Peter Wemm wrote: > Julian Elischer wrote: > > On Thu, 30 May 2002, Jake Burkholder wrote: > [..] > > > It is much more difficult to ensure that all the register values > > > end up the same on each return from the system call on sparc64, due

Re: Seeking OK to commit KSE MIII-again

On Thu, 30 May 2002, Jake Burkholder wrote: > apparently, On Thu, May 30, 2002 at 09:20:57AM -0700, > Julian Elischer said words to the effect of; > > > > > > > > Index: bin/ksetest/Makefile > > =

Re: Seeking OK to commit KSE MIII-again

On Thu, 30 May 2002, Bernd Walter wrote: > > Largely these need to be written by someone who is intimately aquainted > > with the register set of the machine in question and knows > > what registers need to be saved to restore a user context correctly. > > I can do the alpha part tomorrow unle

Seeking OK to commit KSE MIII-again

ok, but does anyone other than john (who has commented) have any comments about the logic and work in the change? I'm working on his comments but comments by others would sure be appreciated.. especially if they actually comment on what I'm trying to do.. If I can get the changes for the other

Re: Seeking OK to commit KSE MIII

On Wed, 29 May 2002, Peter Wemm wrote: > > ie: it is ok to change this: > if (foo) { > fumble(); > futz(); > } else > bah; > > into > } else { > bah; > } In this case it's moot because I already did it as a separate commit but it was changing: if (foo) { mum

RE: Seeking OK to commit KSE MIII

On Wed, 29 May 2002, Julian Elischer wrote: > > > On Wed, 29 May 2002, John Baldwin wrote: > > > > > 4) It would be nice if you didn't mix in gratuitous style changes with > >actual content changes such as extra braces in else clause of > >

Re: Seeking OK to commit KSE MIII

Ok I just committed that one on it's own now back to the real points that jhb raised.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Seeking OK to commit KSE MIII

On Wed, 29 May 2002, Matthew Dillon wrote: > > I agree that as a general rule of thumb it makes sense to commit > whitespace/paren/brace changes separately, but that is ALL it is. > A rule of thumb. It should not be followed blindly, on principle, > if it has an adverse effect

Re: Seeking OK to commit KSE MIII

On Wed, 29 May 2002, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Matthew Dillon w > rites: > > >I agree that as a general rule of thumb it makes sense to commit > >whitespace/paren/brace changes separately, but that is ALL it is. > >A rule of thumb. It should not be

RE: Seeking OK to commit KSE MIII

On Wed, 29 May 2002, John Baldwin wrote: > > On 28-May-2002 Julian Elischer wrote: > > Now things are moving again. > > Jonathon Mini and I have cleaned up the patches a bit > > and fixed the more obvious problems.. > > from teh point of view of non KSE proces

Re:why change: from proc to thread?

kthreads are not threads, but, rather, kernel processes.. they have a separate 'proc' structure. (they are badly named..) On Wed, 29 May 2002, kai ouyang wrote: > > Thank you! I know a little more. From the kthread_create() function, I > find Both 4.x and 5.0 are implemented by fork1(). I am p

Seeking OK to commit KSE MIII

KSE Milestone 3 has been running since BSDcon. Since then things got mightily slowed down due to the birth of my daughter, a burst in work and t round-the-world trip (consequence if the birth had to show the grandparents on 2 continents you know..) Now things are moving again. Jonathon Min

Re: why change: from proc to thread?

On Mon, 27 May 2002, kai ouyang wrote: > Hi,everybody > I found many v_operations, such as VOP_UNLOCK, VOP_OPEN., there > all have a parameter(struct proc) in FreeBSD4.x, but, there all be > changed to thread in FreeBSD5.0. why? And what relation of the proc > and thread ? > Thank you!

Re: IPC, npc, nwfs on -current

do you have patches for what you have done? I didn't realise IPX was broken.. On Fri, 24 May 2002, Mikhail Teterin wrote: > Any plans/updates for the subj? I did what was needed to compile the > npc and nwfs modules here (proc -> thread transitions), but IPX is not > even mentioned in NOTES -

Share a Hotel room for USENIX?

Hi peoples.. I'm looking to share a romm at usenix (the bargain rate of $130/night indicates that some people have a very different idea of a bargain to me) Julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: -current and vmware2

Garance A Drosihn wrote: > > At 11:18 AM -0700 5/11/02, Julian Elischer wrote: [...] > > If this is your first attempt to get vmware2 working on > -current, there are a few tricks to getting it to work > right which the port does not know about yet. I've done this before

Re: -current and vmware2

Hiten Pandya wrote: > > --- Julian Elischer <[EMAIL PROTECTED]> wrote: > > seems something broke in the networking side of things using host-only > > networking.. vmnet1 doesn;t show up any more.. > > Does vmware2 crash when it is started? I was recently tryin

-current and vmware2

ore either... -- ++ __ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ [EMAIL PROTECTED] +-->x USA\ a very strange | ( OZ)\___ ___ | country ! +- X_.---._/presently in

RE: linux broken?

On Thu, 25 Apr 2002, John Baldwin wrote: > > On 25-Apr-2002 Julian Elischer wrote: > > kldload sysvipc.ko or compile the SYSV stuff into your kernel. > Perhaps the linux kld needs to have a module dependency on > the sysvipc modules? there is no sysvipc module but th

RE: linux broken?

On Thu, 25 Apr 2002, John Baldwin wrote: > > kldload sysvipc.ko or compile the SYSV stuff into your kernel. > Perhaps the linux kld needs to have a module dependency on > the sysvipc modules? I did.. it make no difference. > > > julian > > -- > > John Baldwin <[EMAIL PROTECTED]> <>< htt

linux broken?

after a complete resup, re-checkout and recompile on trying to load the linux module: link_elf: symbol semop undefined Anyone have a quick fix? julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

What does "FPU bounds check fault" mean?

I got this fault on a production machine.. The given fault PC was 0xc01499f0 which is the first byte of fxpintr() (??) even though coredumps were enabled, for some reason none was made. > > > > > > wss0c left this message in /var/log/messages: > > > Apr 17 08:36:55 wss0c /kernel: Fatal trap 21:

Re: Bluetooth stack for FreeBSD

On Tue, 16 Apr 2002, Maksim Yevmenkin wrote: > > initially all nodes were WRITERs to "release the stack", but then i > changed my strategy and now i'm serializing data at the edge of graph. > for example both "bt3c" and "h4" nodes will NG_HOOK_FORCE_WRITER on > upstream hook. also i probably

Re: Bluetooth stack for FreeBSD

On Mon, 15 Apr 2002, Julian Elischer wrote: > > [out of time for now.. will read more later] > > Julian > ok, read a bit more: you say: 2) Locking/SMP External code now uses ng_send_fn to inject data into Netgraph, so it should be fine as long as Netgr

Re: Bluetooth stack for FreeBSD

Hi... I have been reading the (well actually, "looking at" may be more acurate.. some minor comments.. ng_btsocket.c: unmodified: line 674 sbappendrecord(&pcb->so->so_snd, m); m = m_dup(m, M_TRYWAIT); if (m == NULL) { error = ENOBUFS; goto

Re: Kernel debugging - what's the procedure?

On Sun, 7 Apr 2002, Josef Karthauser wrote: > On Sun, Apr 07, 2002 at 03:29:41AM -0700, Terry Lambert wrote: > > > > You use another machine, and connect the serial ports together. > > See the handbook for details. > > I'd love to ;) but no additional machine is available at the moment. run

Re: usb lpt borked?

As I mentionned before.. usb printing worked fine for me with a December kernel (and I think January) in March it broke so that it printed, but crashed the machine at the final close(). Now it hangs forever on teh initial open(). On Sat, 6 Apr 2002, Scott Long wrote: > On Sat, Apr 06, 2002 at

Re: usb lpt borked?

this with an April 4 kernel. March 4 kernel had problem(2) On Sat, 6 Apr 2002, Alexander Leidinger wrote: > On 5 Apr, Julian Elischer wrote: > > > > ok guys we seem to be going backwards on this one.. > > > > 3 months ago this worked perfectly > > 2 months a

usb lpt borked?

ok guys we seem to be going backwards on this one.. 3 months ago this worked perfectly 2 months ago it crashed after each document (on close()) now it crashes on open().. at least in the old kernel I could get my printouts :-) Apr 5 12:10:23 jules kernel: uhci0: p ort 0x1060-0x107f irq 5 at d

brakage in if_wi

dev/wi/if_wi_pccard.c ../../../dev/wi/if_wi_pccard.c:102: `PCMCIA_STR_3COM_3CRWE777A' undeclared here (not in a function) ../../../dev/wi/if_wi_pccard.c:102: initializer element is not constant ../../../dev/wi/if_wi_pccard.c:102: (near initialization for `wi_pccard_products[1].pp_name') ../../../

Re: comparing executables

On Wed, 3 Apr 2002 [EMAIL PROTECTED] wrote: > > >Compare them without the ELF headers, a section at a time, so > >that the timestamps are irrelevent. > > From what I recall, there _are_ no timestamps in ELF images, > and compiling the same executable multiple times locally here > seems to bea

Re: comparing executables

On Wed, 3 Apr 2002, Poul-Henning Kamp wrote: > > >How can I find out which binaries have changed? > >they are all different according to cksum so I assume > >that there is a timestamp or something in them. > >Is there a way to compare only the text segments? > > You can do wonders with objdum

comparing executables

I have two directories of executables (actually two entire FreeBSD filesystems) they were both produced from the same checked out trees except that between the two compiles, some patches (unknown) were applied to the sources. How can I find out which binaries have changed? they are all differen

Re: vmware

On Mon, 1 Apr 2002, Makoto Matsushita wrote: > > never> Maybe it's better to make two different ports vmware-tools and > never> vmware-tools3, first of which is for vmware2? > > Ancient ports/emulators/vmware-tools (FreeBSD native vmware-tools for > VMware _1.x_) is outdated for VMware 2.x; i

Re: Problem with ssh

On Thu, 28 Mar 2002, Beech Rintoul wrote: > On Thursday 28 March 2002 10:28 am, Michael L. Hostbaek wrote: > > Beech Rintoul (akbeech) writes: > > > > 'ChallengeResponseAuthentication no' > > Thanks, that fixed the problem. just stops my sshd from working at all. (machine is 4.1.1) To Uns

Just a reminder

The following web page is is SO USEFUL for making changes in the kernel (not quite so useful in other places because there's just so much of it, and because the system calls are not cross referenced.) http://snapshots.jp.FreeBSD.org/tour/ I HIGHLY RECOMMEND that everyone put this in their bookm

Re: gcc -O broken in CURRENT

On Sat, 16 Mar 2002, Greg Black wrote: > [Cc's trimmed] > > Kenneth Culver wrote: > > | > (ttypa):{1078}% file /usr/local/lib/netscape/communicator-4.7.us.bin > | > /usr/local/lib/netscape/communicator-4.7.us.bin: FreeBSD/i386 compact > | > demand paged dynamically linked executable > | > >

Re: malloc() and the stock Perl in -CURRENT (and -STABLE)

On Thu, 14 Mar 2002, Matthew Dillon wrote: > > :thing to do in FreeBSD ? :-) > : > :And everybody with VM clue I've asked says it would be trivial to > :flip two page-table entries, so for all I care it can be > : > : mexchangemapping(void *from, void *to, size_t length) > : > :-- > :Pou

Re: eaccess(2) breaks execution of 4.x binaries on 5.x

On Wed, 13 Mar 2002, Maxim Konovalov wrote: > > I believe you have :-) ummm but we =have never guaranteed that N+1 binaries will run on N systems. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: eaccess(2) breaks execution of 4.x binaries on 5.x

any change that has to be added to 4.x tomake it run on 5.x is the wrong answer. 4.x binaries should all run on 5.x (unless something was accidentally committed to 4.x that should be backed out.) any change for allowing 4.x binaries to run on 5.x should be done on the 5.x side of things, (unless

Re: Serial break into debugger broken from 'cu' on -CURRENT?

serial break is different.. it is suppoesed to break into the d debugger if it receives a "BREAK" (i.e framing error) in the serial port. cu ,tip and other such programs have an escape sequence to "send a break" julian On Sun, 10 Mar 2002, Glenn Gombert wrote: > I just rebuilt -current on tw

Re: Keyboard (quasi-)lockup running script

cvs checkout -D "8PM last Monday" :-) (or similar) On Fri, 8 Mar 2002, David Wolfskill wrote: > Is anyone else seeing this? > > Running -CURRENT (been tracking it daily for a while, now), I find that > if I run script(1), things basically run as expected... until I try to > close script's

Re: Anyone using DIAGNOSTIC td_ucred stuff?

I've been running it but I am about to turn it off because I want to cache the value over userland. The code is completely gone in the KSE patch. On Fri, 8 Mar 2002, John Baldwin wrote: > Is anyone using the DIAGNOSTIC cached td_ucred stuff in current? If not, I'd > like to replace it with a

Re: Patch for critical_enter()/critical_exit() & interrupt assem

those reviews object on a purely subjective manner. "I think this is premature" I don't consider that to be a technical review? do you? they do not even comment on the bug-fixing aspect of the patch. On Thu, 7 Mar 2002, Warner Losh wrote: > In message <[EMAIL PROTECTE

Re: Patch for critical_enter()/critical_exit() & interrupt assem

On Thu, 7 Mar 2002, Justin T. Gibbs wrote: > > Then do the right things so it will. Unfortunatly that has been proven to not work. after reverting the change and silently waiting for a week 1/ no person bothered to review it. 2/ people assumed the patch had gone away. To Unsubscribe: send

Re: Patch for critical_enter()/critical_exit() & interrupt assem

On Thu, 7 Mar 2002, Michael Smith wrote: > > Trim your cc's. > > > I'm sorry, but simply not liking the idea of someone else doing a > > particular optimization now verses later is not a good enough reason > > to require that 40+ hours worth of work be thrown away when that > >

Re: Patch for critical_enter()/critical_exit() & interrupt assem

On Thu, 7 Mar 2002, David Greenman wrote: > >No, Core has just said that he doesn't because he can over-rule any change > >in the kernel. And there is no requirement for him to justify it. > >That is definately *NOT* what core has said. Please go re-read our > announcement of the SMPng tec

Re: Patch for critical_enter()/critical_exit() & interrupt assem

On Thu, 7 Mar 2002, Justin T. Gibbs wrote: > > The only way it will get delayed that long is if you spend all of your > time stomping up and down, writing in all caps, and tell the rest of > us that we have to follow the proceedures you think are appropriate. > That's not how colaboration work

Re: Patch for critical_enter()/critical_exit() & interrupt assem

On Wed, 6 Mar 2002, Jeroen C.van Gelderen wrote: > > Search for "paper John Baldwin" and find link 6: A good start though incomplete. Unfortunate that it took such a fight to get it to be written. Hopefully it's existance can prevent soem further bloodshed. Is it possible for other people to

Contemplating THIS change to signals.

Maybe this should be in -arch.. I couldn;t make my mind up, but.. There is some behaviour in signals which seems 1/ un-neccesary 2/ potentially dangerous. in addition it is 3/ Definitly incompatible with KSEs. I am hoping that someone can give me a good reason why it is done, and failing that,

Re: gtags? htags?

It might be an idea if the kernel were kept separate because I find that the cross-reference is good but having kernel and userspace mixed up is a bit confusing.. On Wed, 6 Mar 2002, Makoto Matsushita wrote: > > gnn> They're needed for the tags: target in the kernel makefiles and > gnn> since

Re: Netgraph, device drivers and mutexes

On Mon, 4 Mar 2002, Julian Elischer wrote: > > > On Mon, 4 Mar 2002, Maksim Yevmenkin wrote: > > > Julian, > > > > thank you very much for a such detailed answer :) > > > > [...] > > I just checked in some generic timeout routines int

Re: Damn slow startup

or tell teh config it is a 386 cpu as well as a '686 that will force it to emulate those very slowly done instructins so that they are actually done faster :-) On Tue, 5 Mar 2002, Terry Lambert wrote: > Run -stable. VMWare takes a very long time to emulate > certain locking primitives, for som

Re: Netgraph, device drivers and mutexes

On Mon, 4 Mar 2002, Maksim Yevmenkin wrote: > Julian, [...] > > speaking of ng_tty... it is clear to me how to inject data into Netgraph > in a safe way, but it is not yet clear how Netgraph can inject data into > other subsystems. > > you see, the Bluetooth spec defines several Host (PC) to

Re: Netgraph, device drivers and mutexes

On Mon, 4 Mar 2002, Maksim Yevmenkin wrote: > Julian, > > thank you very much for a such detailed answer :) > > [...] > > > I hope that this helps you! > > yes it did help :) i changed my code and it seems to work just fine. > i wish i had SMP laptop to test it :) Well it aint exactly S

Re: devfs(5) Permissions

s as a default. That would at least get us back the > >features of the old /dev which we're missing now. > > This is much harder than you think... > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [EMAIL PROTECTED] | TCP/IP since RFC 956 > FreeBS

Re: Netgraph, device drivers and mutexes

g1, int arg2) { do_timeout_things(node); } This is GUARANTEED to be run with an exclusive writer lock on that node. Please let me know how this all works out. p.s. Netgraph question shouldalso be sent to -net > > thanks, > max >

Re: more -current testers

On Fri, 1 Mar 2002, Glenn Gombert wrote: >I have spent several months figuring how to do diskless mounts for test > kernels, run debuggers from serial terminals and do remote kernel debugging > with gdb, and spent lots and lots of time doing is as well. Some 'up to > date' "How To's" are re

Re: Patch for critical_enter()/critical_exit() & interrupt assem

On Fri, 1 Mar 2002, Terry Lambert wrote: > I think the right thing to do is to commit the cred changes, > and stabilize them, if there's even a problem, as you expect > from your comments about "dangerous". > John already committed a majority of all the cred changes. I never saw a commit mess

Re: Patch for critical_enter()/critical_exit() & interrupt assem

On Thu, 28 Feb 2002, David Greenman wrote: > >>:John has been consistently chugging along on the job all the way. > >>:At this point in time, until he is officially unseated John is our > >>:designated SMPng architect and his word is pretty final. > >>: > >>:-- > >>:Poul-Henning Kamp | U

Re: Kernel Build(s) broken in -Current

this was fixed.. (many warnings removed) try resup and reconfig On Thu, 28 Feb 2002, Glenn Gombert wrote: > Apparently a recent change in the make file(s) in -Current causes normal > warning messages to be treated as errors (for un-initialized variables) for > example, which stops the build p

RE: Updated ATAPI/CAM patches

We have CVS Why not commit the prototype now and update it as people get the corner cases worked out? The code doesn't interfere with either the CAM system or the ATAPI system that I can see. On Thu, 28 Feb 2002, Jan Stocker wrote: > I think Thomas is doing here a quite good job and it is also

Re: Updated ATAPI/CAM patches

where dod sis post his email..? I never saw it On Thu, 28 Feb 2002, Kenneth Culver wrote: > > Hmm, why do we need to add new layers and loss of functionality > > to the ATAPI devices ? > > Many many many people would like to be able to use cdrecord to burn data > to cd's so that all the fr

Re: Updated ATAPI/CAM patches

Poul-henning. What crack are you on? Have you looked at the patches in question? They are small and non-intrusive. We are relying on the ATA maintainer to tell us whether they are dangerous, but they are so small that we should look at fast-tracking them if possible. Even if it was broken, it'

Re: Updated ATAPI/CAM patches

I think it's better to commit it now and have it fixed in situ. It's new functionality so committing it with bugs will not break anyone. it will however get more work done on it and more testing. On Thu, 28 Feb 2002, Kenneth D. Merry wrote: > On Thu, Feb 28, 2002 at 10:49:18

Re: Updated ATAPI/CAM patches

This is definitly something that is needed.. The question is whether the CAM and ATAPI authors feel it is right. We are guided by them (even though we desperatly need this). Personally even if not perfect.. it's better than nothing and we should probably commit something like it. or based on it

Re: Patch for critical_enter()/critical_exit() & interrupt assem

yes but thete are subcommits that you could go ahead with... the td_ucred stuff could have been checked in directly into -current. On Thu, 28 Feb 2002, John Baldwin wrote: > > On 26-Feb-02 Julian Elischer wrote: > > > > > > On Tue, 26 Feb 2002, John Baldwin wrote:

Re: controversial fix or some errors breaking LINT

sure.. does bus-space have a bzero? On Wed, 27 Feb 2002, Warner Losh wrote: > In message Garance A Drosihn writes: > : How philosophically sickening would it be to create a macro: > : > : #define bcopy_volatile(x,y) bcopy((casts)x,(casts)y) > > How abou

Re: controversial fix or some errors breaking LINT

I presume then that you also feel that allowing bcopy to copy volatile regions is a bad idea? On Wed, 27 Feb 2002, Peter Wemm wrote: > Alfred Perlstein wrote: > > * Matthew Dillon <[EMAIL PROTECTED]> [020227 14:51] wrote: > > > > > > : > > > :ok so I leave it to other people to fix LINT > >

<    5   6   7   8   9   10   11   12   13   14   >