From owner-freebsd-current@FreeBSD.ORG Wed May 5 14:52:36 2004 Return-Path: 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 EF86B16A4CE for ; Wed, 5 May 2004 14:52:35 -0700 (PDT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with SMTP id C3FD843D49 for ; Wed, 5 May 2004 14:52:34 -0700 (PDT) (envelope-from ltning@anduin.net) Received: (qmail 96592 invoked by uid 6759); 5 May 2004 21:52:33 -0000 Received: from ltning@anduin.net by anduin.net by uid 82 with qmail-scanner-1.20 (clamscan: 0.60. spamassassin: 2.60. Clear:RC:1(217.8.136.185):. Processed in 0.023863 secs); 05 May 2004 21:52:33 -0000 X-Qmail-Scanner-Mail-From: ltning@anduin.net via anduin.net X-Qmail-Scanner: 1.20 (Clear:RC:1(217.8.136.185):. Processed in 0.023863 secs) Received: from gatekeeper.in-space.org (HELO ?192.168.1.10?) (217.8.136.185) by anduin.net with SMTP; 5 May 2004 21:52:33 -0000 Message-ID: <4099621C.2090107@anduin.net> Date: Wed, 05 May 2004 23:52:28 +0200 From: Eirik Oeverby User-Agent: Mozilla Thunderbird 0.6 (X11/20040504) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Gallatin References: <16536.59752.749995.185110@grasshopper.cs.duke.edu> In-Reply-To: <16536.59752.749995.185110@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: enabling second cpu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 05 May 2004 21:52:36 -0000 Hi, Thanks for trying, but this doesn't seem to be enough. The CPU is still flagged as unusable and SMP is not enabled sysctl kern.smp.active=0. kern.smp.cpus=1. I somehow guess this might have been the wrong/not the only place to do such a 'hack'? Been looking around a bit myself, but have given up at this point - I'm no C coder, really, and definitely no kernel hacker.. /Eirik Andrew Gallatin wrote: > Just a guess, but maybe WinXP is ignoring the flags in the mptable > which mark the CPU as not usable. > > Try something like the appended patch and see if it helps. > (make sure you have a backup kernel just in case it blows up). > > Drew > > Index: i386/i386/mptable.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/i386/mptable.c,v > retrieving revision 1.229 > diff -u -r1.229 mptable.c > --- i386/i386/mptable.c 10 Dec 2003 19:29:39 -0000 1.229 > +++ i386/i386/mptable.c 5 May 2004 13:13:41 -0000 > @@ -414,7 +414,7 @@ > switch (*entry) { > case MPCT_ENTRY_PROCESSOR: > proc = (proc_entry_ptr)entry; > - if (proc->cpu_flags & PROCENTRY_FLAG_EN) { > + if (1 /*proc->cpu_flags & PROCENTRY_FLAG_EN*/) { > lapic_create(proc->apic_id, proc->cpu_flags & > PROCENTRY_FLAG_BP); > cpu_mask = (u_int *)arg;