Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 19 Dec 2002 17:09:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 19 Dec 2002 17:09:29 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:36360 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Thu, 19 Dec 2002 17:09:04 -0500 Message-ID: <3E024567.3080806@transmeta.com> Date: Thu, 19 Dec 2002 14:17:11 -0800 From: "H. Peter Anvin" Organization: Transmeta Corporation User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021119 X-Accept-Language: en, sv MIME-Version: 1.0 To: Pavel Machek CC: Alan Cox , Andre Hedrick , Linus Torvalds , Dave Jones , Ingo Molnar , Linux Kernel Mailing List Subject: Re: Intel P6 vs P7 system call performance References: <1040137976.20018.3.camel@irongate.swansea.linux.org.uk> <20021218235546.GD705@elf.ucw.cz> In-Reply-To: <20021218235546.GD705@elf.ucw.cz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 748 Lines: 20 Pavel Machek wrote: >> >>Different thing - int 0x80 syscall not i/o port 80. I've done I/O port >>80 (its very easy), but requires we set up some udelay constants with an >>initial safety value right at boot (which we should do - we udelay >>before it is initialised) > > Actually that would be nice -- I have leds on 0x80 too ;-). > Pavel We have tried before, and failed. Phoenix uses something like 0xe2, but apparently some machines with non-Phoenix BIOSes actually use that port. -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/