From owner-freebsd-i386@FreeBSD.ORG  Thu Nov 11 17:58:23 2004
Return-Path: <owner-freebsd-i386@FreeBSD.ORG>
Delivered-To: freebsd-i386@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2E41516A4CE
	for <freebsd-i386@freebsd.org>; Thu, 11 Nov 2004 17:58:23 +0000 (GMT)
Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D6D5243D39
	for <freebsd-i386@freebsd.org>; Thu, 11 Nov 2004 17:58:22 +0000 (GMT)
	(envelope-from anurekh@gmail.com)
Received: by rproxy.gmail.com with SMTP id 34so363668rns
        for <freebsd-i386@freebsd.org>; Thu, 11 Nov 2004 09:58:20 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=Rx9fktjePnkjpaGII0qOPkV3IC6cmAUEZVXgWB7CHnNTBKM4VdpwZZfCXbtelePvhpJONdCbCg/Aaa62/vZ+LpIJ7k8wOMzUq8EQRsBMxFYlrxGL8mKeR97Ci43WTj8cSzZ3IHSo+9TyeKI5xT2JNkNEUYJ/4W453ngXH2Z3eV8=
Received: by 10.38.206.26 with SMTP id d26mr301659rng;
        Thu, 11 Nov 2004 09:58:20 -0800 (PST)
Received: by 10.38.8.23 with HTTP; Thu, 11 Nov 2004 09:58:20 -0800 (PST)
Message-ID: <aa26c8a904111109581723563d@mail.gmail.com>
Date: Thu, 11 Nov 2004 12:58:20 -0500
From: Anurekh Saxena <anurekh@gmail.com>
To: freebsd-i386@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: kernel: return from interrupt
X-BeenThere: freebsd-i386@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Anurekh Saxena <anurekh@gmail.com>
List-Id: I386-specific issues for FreeBSD <freebsd-i386.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-i386>
List-Post: <mailto:freebsd-i386@freebsd.org>
List-Help: <mailto:freebsd-i386-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Nov 2004 17:58:23 -0000

Hi,

I was under the impression that the 5.3 release had an option for full
preemption.
If I am correct, why does the kernel refuse to schedule on a 
return_from_interrupt if its not
going back to userland?
I can understand this being a problem if interrupts were nested, or
return from a page fault in a
critical section. 
Please correct me if I am wrong, but if a *high* priority interrupt
thread is ready to run, it
should be given a chance. Presuming the *interrupted* kernel path is
going to give up the CPU
fast enough is probably not a good idea. 


I hope I have sent this to the right mailing list.

Thanks,
Anurekh