From owner-svn-src-all@FreeBSD.ORG Wed Feb 11 16:45:51 2015 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1B18B68D; Wed, 11 Feb 2015 16:45:51 +0000 (UTC) Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D6A67A48; Wed, 11 Feb 2015 16:45:50 +0000 (UTC) Received: by ierx19 with SMTP id x19so5342208ier.3; Wed, 11 Feb 2015 08:45:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=CuvBCI/glPLH9iCpKw+3WZ9EFrlbOluecMZKdVMtxjM=; b=Iv+qJXh5y34Fk0FaR+xp6O7Kde//3neDX1gUfY7Kp40qfEPzj+ouTgKvDhjnUq0zpw luYY7rRW2VQ/BFq577jERD/s4yjbzwC4hdDt2IzCSI+CpKDfxgIwUgKsg8UpgeZCBT+C orS6l1Fb6MTZiE7AnK2KR5k1sS0K0iDWyDhK6eCEo2N1CQiZ1HBBSe11OfgVkU/r9IAj KAconJz/kva1XkQJrt0or8Pb1CO6cHzyWSZ0iCxSHG4VmwXSUyl+Z9YdmuV8IkVgzVRA dlRlHQUOjwa9N2m6aWR8esHRqVcwatSGv5lVOkcsIt1ZdW0fuASlwXZx1VC4gmVehwz5 HLlA== X-Received: by 10.43.92.9 with SMTP id bo9mr4076078icc.54.1423673144112; Wed, 11 Feb 2015 08:45:44 -0800 (PST) MIME-Version: 1.0 Sender: mr.kodiak@gmail.com Received: by 10.64.98.228 with HTTP; Wed, 11 Feb 2015 08:45:13 -0800 (PST) In-Reply-To: <6564436.fIAEJlraDt@ralph.baldwin.cx> References: <20150211083200.GO42409@kib.kiev.ua> <6564436.fIAEJlraDt@ralph.baldwin.cx> From: Bryan Venteicher Date: Wed, 11 Feb 2015 10:45:13 -0600 X-Google-Sender-Auth: N0XN6cR8p9rErrOlUw67bChIQUA Message-ID: Subject: Re: svn commit: r278473 - in head/sys: amd64/amd64 amd64/include amd64/vmm contrib/dev/acpica/include i386/i386 i386/include x86/acpica x86/include x86/x86 x86/xen To: John Baldwin Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "src-committers@freebsd.org" , Rui Paulo , "svn-src-all@freebsd.org" , "svn-src-head@freebsd.org" , Konstantin Belousov , =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 16:45:51 -0000 On Wed, Feb 11, 2015 at 9:20 AM, John Baldwin wrote: > On Wednesday, February 11, 2015 10:32:00 AM Konstantin Belousov wrote: > > On Wed, Feb 11, 2015 at 12:43:39AM +0000, Rui Paulo wrote: > > > On Feb 09, 2015, at 01:01 PM, Konstantin Belousov > wrote: > > > > > > Author: kib > > > Date: Mon Feb 9 21:00:56 2015 > > > New Revision: 278473 > > > URL: https://svnweb.freebsd.org/changeset/base/278473 > > > > > > Log: > > > Add x2APIC support. Enable it by default if CPU is capable. The > > > hw.x2apic_enable tunable allows disabling it from the loader prompt. > > > > > > This breaks VMware Fusion when the host CPU has x2APIC support. In > > > my case, mpt(4) was unable to receive interrupts and USB was similarly > > > broken. It's possible that this is a VMware bug, but you might want to > > > avoid turning this on when running under the VMware hypervisor. > > > > Neel pointed this out to me when the patch was reviewed. > > He told me that x2APIC does not work in Fusion 5.x, while it seems > > to be fixed in 7.x. > > https://communities.vmware.com/message/2173695?tstart=0 > > > > Upon further discussion with Neel and Peter, it was suggested that we > > enable enable x2APIC unconditionally, which seems what is done for > > Linux benchmarks. > > > > Is vmware 5.x is used while there is already at least version 7.x ? > > I have no idea about vmware product nomenclature and lifecycle. > > I believe we can ask vmware what version it is when we notice we are > running > under it (which we already detect for TSC purposes). We could quirk for > that > case, or even just disable for VM_GUEST_VMWARE for now. > > I'm not too familiar with this stuff, but is this Linux commit [1] relevant? If so, it might be something nice to wrap into my projects/paravirt branch (I've been extremely busy recently, but I hope to get the review comments addressed and merge it into HEAD soon). [1] - https://lkml.org/lkml/2013/1/17/552 -- > John Baldwin > >