Message ID | 20231003062458.23552-1-xin3.li@intel.com (mailing list archive) |
---|---|
Headers | show
Return-Path: <xen-devel-bounces@lists.xenproject.org> X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 908C2E7542B for <xen-devel@archiver.kernel.org>; Tue, 3 Oct 2023 06:55:05 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.611887.951510 (Exim 4.92) (envelope-from <xen-devel-bounces@lists.xenproject.org>) id 1qnZIp-00041S-Hx; Tue, 03 Oct 2023 06:54:43 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 611887.951510; Tue, 03 Oct 2023 06:54:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from <xen-devel-bounces@lists.xenproject.org>) id 1qnZIp-00041L-F4; Tue, 03 Oct 2023 06:54:43 +0000 Received: by outflank-mailman (input) for mailman id 611887; Tue, 03 Oct 2023 06:54:42 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from <SRS0=XwHy=FR=intel.com=xin3.li@srs-se1.protection.inumbo.net>) id 1qnZIn-00040o-T6 for xen-devel@lists.xenproject.org; Tue, 03 Oct 2023 06:54:42 +0000 Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.126]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id b742ab65-61b9-11ee-98d2-6d05b1d4d9a1; Tue, 03 Oct 2023 08:54:38 +0200 (CEST) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Oct 2023 23:54:35 -0700 Received: from unknown (HELO fred..) ([172.25.112.68]) by fmsmga005.fm.intel.com with ESMTP; 02 Oct 2023 23:54:34 -0700 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion <xen-devel.lists.xenproject.org> List-Unsubscribe: <https://lists.xenproject.org/mailman/options/xen-devel>, <mailto:xen-devel-request@lists.xenproject.org?subject=unsubscribe> List-Post: <mailto:xen-devel@lists.xenproject.org> List-Help: <mailto:xen-devel-request@lists.xenproject.org?subject=help> List-Subscribe: <https://lists.xenproject.org/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xenproject.org?subject=subscribe> Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" <xen-devel-bounces@lists.xenproject.org> X-Inumbo-ID: b742ab65-61b9-11ee-98d2-6d05b1d4d9a1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1696316078; x=1727852078; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=nOMSeUVu9l0D0ehPQn5ZxJkiMveZc24zyXCfbVOqw1g=; b=anWg79sdm5cz8LoKbFnLXddyOGmqtJUMGTRXcBP0qizlPpVPdrH6Wa8g epi1qC/aXPNsCEe2R3+9Fs3C6q80bgGYLUtVpHK4zCwhl6LGvF0f2a643 SYg5gmLudXP2MY/NSHnxmIQAdRyPHEasFT4m/gBVsXqNgB2D8tOfLM+5s LudvldmGOY35NPWcElt3BwhFbCCf2M0hyToLAr8Q1+ZF3xYAvJzJ/y34I 0MLxtvGohNGkCcvzuNSr/vHTMdfwLKdbVGUdjsnepbInztohZj/H8Pkgx HmKZIWmViaMhVMc+aT2C2DdwIIXiOF92qXvHBxmLtr3ZdSkGQEstdlw+0 g==; X-IronPort-AV: E=McAfee;i="6600,9927,10851"; a="367857891" X-IronPort-AV: E=Sophos;i="6.03,196,1694761200"; d="scan'208";a="367857891" X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10851"; a="1081900892" X-IronPort-AV: E=Sophos;i="6.03,196,1694761200"; d="scan'208";a="1081900892" From: Xin Li <xin3.li@intel.com> To: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org, linux-hyperv@vger.kernel.org, kvm@vger.kernel.org, xen-devel@lists.xenproject.org Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, luto@kernel.org, pbonzini@redhat.com, seanjc@google.com, peterz@infradead.org, jgross@suse.com, ravi.v.shankar@intel.com, mhiramat@kernel.org, andrew.cooper3@citrix.com, jiangshanlai@gmail.com, nik.borisov@suse.com Subject: [PATCH v12 00/37] x86: enable FRED for x86-64 Date: Mon, 2 Oct 2023 23:24:21 -0700 Message-Id: <20231003062458.23552-1-xin3.li@intel.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit |
Series |
x86: enable FRED for x86-64
|
expand
|
On 3.10.23 г. 9:24 ч., Xin Li wrote: > This patch set enables the Intel flexible return and event delivery > (FRED) architecture for x86-64. > Which tree is this based on now? I tried running 'b4 diff' but it complains it can't find some context around arch/x86/kernel/cpu/common.c . I have the tip tree updated. >
> > This patch set enables the Intel flexible return and event delivery > > (FRED) architecture for x86-64. > > > > > Which tree is this based on now? > It was based on the tip master on the day I sent the v12 patch set, i.e., Monday night in the US west coast. > I tried running 'b4 diff' but it complains it can't > find some context around arch/x86/kernel/cpu/common.c . > What does it complain? > I have the tip tree updated. I just did a rebase on the latest tip master, and did find a build bug caused by: [PATCH v12 33/37] x86/entry: Add fred_entry_from_kvm() for VMX to handle IRQ/NMI as <asm/export.h> is deprecated by <linux/export.h> yesterday. After I replaced it, it compiles and boots. What should I do now? Thanks! Xin