Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Nov 2000 17:37:09 +0100
From:      Bernd Walter <ticso@cicely8.cicely.de>
To:        freebsd-alpha@freebsd.org
Subject:   AST and ithread question
Message-ID:  <20001112173709.B5667@cicely8.cicely.de>

next in thread | raw e-mail | index | archive | help
As far as I underderstood an AST is needed for context switching.
An AST can only happen before returning to user-mode.
Which process is running in user-mode during kernel initialisation.
How can the context switched to an scsi-controller ithread during
the first scsi-probe?

I can see that there are getting clock swi scheduled and processed.
after the 15 second period after scsi-reset I see from one or more
controllers an interrupt and the connected ithread is set to the
run-queue.
No ithread including the clock is running after that.
The clock is still geting scheduled.

I tried to remove this AST limitation but this doesn't work as the
kernel hangs during clock initialisation.
I also tried to reduce it to gd_intr_nested_level==0

Possibly the console output from KTR changes the situation as I'm
running on a 9600 seriel.
Does anyone know how I can change this to a higher rate?
If neccesary I will add some sio devices to separate kernel and SRM
output.

-- 
B.Walter              COSMO-Project         http://www.cosmo-project.de
ticso@cicely.de         Usergroup           info@cosmo-project.de



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001112173709.B5667>