From owner-freebsd-current@FreeBSD.ORG Sat Jan 14 15:32:03 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD80216A41F for ; Sat, 14 Jan 2006 15:32:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3431743D46 for ; Sat, 14 Jan 2006 15:32:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k0EFW1wj047782; Sat, 14 Jan 2006 08:32:02 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43C91972.7020901@samsco.org> Date: Sat, 14 Jan 2006 08:32:02 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Divacky Roman References: <20060114095318.GA39508@stud.fit.vutbr.cz> In-Reply-To: <20060114095318.GA39508@stud.fit.vutbr.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: current@freebsd.org Subject: Re: sysenter patch question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2006 15:32:03 -0000 Divacky Roman wrote: > hi > > there's a patch which makes fbsd use sysenter. why wasnt it commited? is there > any plan to make it into kernel? or was it just forgotten? > > thnx for the info > > roman > I was the last to work on the patch, and that was about a year or so ago. It worked fine under fairly simple processes, but trying to run things like KDE and Mozilla made it blow up fairly quickly. I suspect that it has something to do with thread upcalls, but I never got around to figuring it out. If someone wants to pick it up, that would be great. Note that this only matters for i386; amd64 has always had its own version of sysenter that it uses. Scott