From owner-freebsd-current Thu Jan 23 16:14:39 2003 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 74CCB37B401 for ; Thu, 23 Jan 2003 16:14:38 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id C7DEE43F43 for ; Thu, 23 Jan 2003 16:14:32 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 73283 invoked by uid 1000); 24 Jan 2003 00:14:27 -0000 Date: Thu, 23 Jan 2003 16:14:27 -0800 (PST) From: Nate Lawson To: Garance A Drosihn Cc: current@FreeBSD.ORG Subject: Re: 5.0-RELEASE & VMWare 3.2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 23 Jan 2003, Garance A Drosihn wrote: > Someone recently added an 'SMP' file to sys/i386/conf, which just > includes GENERIC, changes the 'ident' and then turns on the SMP > and APIC_IO options. Perhaps we should add a VMWARE one, with an > eye towards building a "vmware-appropriate" kernel that would be > available on the install CD's? Or to fix this longer term, provide a way at run-time for a kernel to provide different code for the same purpose. Linux did this for the syscall (int 0x80 vs. syscall) instructions. I could see it being done for locking low-level operations as well. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message