Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp6338399yba; Thu, 11 Apr 2019 17:50:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqzWvdgNCoiiP6l4KKAZCfdbjmHqgoxnbTbxRvuZ38vfiJXjqAhCmkp9HF+WgEAf+pPfGHKO X-Received: by 2002:a63:5a47:: with SMTP id k7mr50238984pgm.174.1555030243315; Thu, 11 Apr 2019 17:50:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555030243; cv=none; d=google.com; s=arc-20160816; b=Lo/nX+Ivt5GDoQkEaCvkL7GXFa9vh9DaFrtsCPgKyb5hJhiSQKkJDeqvP53PdseFTI GZictQy1fdrBC5xexg53Z1hxIDaB3EZkMwvzbgh3SFWd3rFhCqnNpiMe1t7J9+XSCBnw dlvd54pITaIykEEaq1SazzLW/Jtq5ACXVe0BlrIugZe/ynYP5YMXcTvJi3T4/du5/4Hd NTAreh5ikf+KAsMQoAOaW4QvsZmHQjJg8IALMachE96xOeovt1BDC9WoNIyRpJtobPPO +FtXzEmRbnFUFFeL1/U9jOZk8hkLdYJdT5fqs7oa4NT8qslxCIAqqhPFwbLaqvMw7t+H XFZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=ByuGx/CQWT0ckPvSWwZg0fGF5qtU0nQGR52RGTA5DvU=; b=nlgPk29axOMVuDe4jno1y9wneMWemHdTDuYriyEJjJDYclaJJ+OvRXDaAPE3kUcER7 c/i3MDRh6EpFOqM/8Fbx8cwdLPnpC08SXx7Hs/Ddj7Kn+J3G9BCr/V2cqcTbyL+kvmkT TS7rTiGGvPwWZW+pOGy5cpHyfFRnDYocTs2z3rSVQjPxqgjl5oiKqupwIgMhD0iSzCKD FNA5FfLlyvrg0I26z0v22xuyK8hnh7V4fbNW1JDGg+HdZiLzWio2E5zxGLPZMqWsiy3w jVVr5vlqDM7PJJ7ZX8oXWJFtRbrKR6DaPyoFB1poNHZRxIoRVx0qaiv+G8+sZ4TbQTpE ahkA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h20si30964607pgn.69.2019.04.11.17.50.26; Thu, 11 Apr 2019 17:50:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727006AbfDLAid (ORCPT + 99 others); Thu, 11 Apr 2019 20:38:33 -0400 Received: from mga01.intel.com ([192.55.52.88]:43293 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726577AbfDLAid (ORCPT ); Thu, 11 Apr 2019 20:38:33 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Apr 2019 17:38:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,339,1549958400"; d="scan'208";a="135075776" Received: from genxtest-ykzhao.sh.intel.com (HELO [10.239.143.71]) ([10.239.143.71]) by orsmga006.jf.intel.com with ESMTP; 11 Apr 2019 17:38:31 -0700 Subject: Re: [RFC PATCH v3 2/4] x86: Add the support of ACRN guest To: Borislav Petkov Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de, Jason Chen CJ References: <1554711131-21514-1-git-send-email-yakui.zhao@intel.com> <1554711131-21514-3-git-send-email-yakui.zhao@intel.com> <20190408143952.GF15689@zn.tnic> <20190411134900.GG30080@zn.tnic> From: "Zhao, Yakui" Message-ID: <222b3a4a-6706-ed11-a8cf-9e6f516cc7fe@intel.com> Date: Fri, 12 Apr 2019 08:36:34 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20190411134900.GG30080@zn.tnic> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019年04月11日 21:49, Borislav Petkov wrote: > On Wed, Apr 10, 2019 at 05:15:48PM +0800, Zhao, Yakui wrote: >> Currently the x2apic is not enabled in the first step. >> Next step it needs to check the cpu info reported by ACRN hypervisor to >> determine whether the x2apic should be supported. > > What "cpu info"? CPUID or something ACRN-specific? It is based on CPUID. The low-level ACRN hypervisor can return the different output of CPUID when several linux guests executes the CPUID instruction. Then it can control whether x2apic is supported in one linux guest. So we will leverage the X86_FEATURE_X2APIC bit from CPUID to indicate whether the x2apic is supported in linux guest when ACRN hypervisor is detected. Is this fine to you? Thanks >