X-Spam-Check-By: sourceware.org Date: Wed, 16 May 2007 23:38:18 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: DualCores and Current Cygwin problems Message-ID: <20070517033818.GA22068@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4e41f5c20705162032j3af3534am90ba31e1cf2bf71e AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4e41f5c20705162032j3af3534am90ba31e1cf2bf71e@mail.gmail.com> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Wed, May 16, 2007 at 09:32:10PM -0600, Morgan Gangwere wrote: >one of them (for Intel Mac processors with Dual Cores in some stores) >there was a driver that would not allow Cygwin to talk to the device >like UNIX does because it did not have "Hyperviser" mode access - >special access to let the software kernel run on the CPU directly... >(listen to "security now - Blue Pill" for more info) - x86 normal >systems are fine with the system at current because they do not allow >for Hypervisor. Cygwin is a standard Windows DLL which uses Windows APIs to emulate linux. The words "talk to the device like UNIX does" do not make sense in that context. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/