From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1A82AC001E0 for ; Mon, 31 Jul 2023 23:19:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229454AbjGaXTN (ORCPT ); Mon, 31 Jul 2023 19:19:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41374 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231905AbjGaXS3 (ORCPT ); Mon, 31 Jul 2023 19:18:29 -0400 Received: from mail-yb1-xb4a.google.com (mail-yb1-xb4a.google.com [IPv6:2607:f8b0:4864:20::b4a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4A7DF2106 for ; Mon, 31 Jul 2023 16:18:02 -0700 (PDT) Received: by mail-yb1-xb4a.google.com with SMTP id 3f1490d57ef6-d1ebc896bd7so5964049276.2 for ; Mon, 31 Jul 2023 16:18:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1690845456; x=1691450256; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=A2YbEGxqz9SscBGtet0Gs0ciHUjPL61/tRobVSn5JSc=; b=Aspi3sVz1s4NKlFaJjQOa2DQlODn/JsCKt4eqnvhQolwNg6rVTEqjLQs26sN5J6ZNe 3e/etHAaEqvAoxl+oSQQP1bHfmA59RbK7Nu0azx4K+EVcSxVntDfjH8buFsuy2V7KlEw 5RZ7h2m65ZZHDqRcD6/spD/JjZaCVH323kw1HLp8C4YPZbjDkNb49TqTz+Z2vaOWATUw n/OnsLadTVEbeeCCi9f1Xp8cRMaUuSd29J6gHrEWBjtkXdfJ7q9euJ/ihFEIWOoOKssN /B9i1WTYQfm0A5NhSpMZHAiVkGnI47YF/h8cE5B0h4DZfCGtUwSF1W1GjS47WDQ5r/1d NbPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690845456; x=1691450256; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=A2YbEGxqz9SscBGtet0Gs0ciHUjPL61/tRobVSn5JSc=; b=Q0fhiXEFJMSVUv/j+vvhe/UWO1y9gs5VvXoQPEoZnoPWm7/Zk4naqt2j7diVMfTCYi 4TsAPp/dv0PJRsRWA3/xT4SKQ1LalhvdYPXFrzTqr5qJ+CfPJjgPFiS0iFupq6nQuABq iJdfH/0qTVulaRVo7IJfW5yfg8mBNN9MAeW5X3IEm8q/n7oMT8YZHWel4c6evFmu3aM+ SS5XE+Q6CcOq+b8WOJzaF7UBxrSxc1sJ8QjxXos9KVgOf+irp9sAeTJ0v/56tsL7injn v8g2zlX+hWWM5XEwrRBqnTjVDhaUKEwZejxxe1q0Ixixhp6CJWTv0NqgTdTzBicNqntI lSXw== X-Gm-Message-State: ABy/qLZ3FfkeIyu+VshDubIiOnBxZZCxtyUACz75ck76TkSWvVhPfLmF d82YIDx7p54IRnFBv0NrQfcKr+PdBH8= X-Google-Smtp-Source: APBJJlETEe4EZ6/j95cQ4sv3ryYhK33RfUu+RWsNUCsL/BaRynxJ5PFVR6kJ5MkvzQvyz83entZG77hN4jM= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a25:69c7:0:b0:d07:f1ed:521a with SMTP id e190-20020a2569c7000000b00d07f1ed521amr63258ybc.4.1690845456129; Mon, 31 Jul 2023 16:17:36 -0700 (PDT) Date: Mon, 31 Jul 2023 16:17:34 -0700 In-Reply-To: Mime-Version: 1.0 References: <20230731063317.3720-1-xin3.li@intel.com> Message-ID: Subject: Re: [PATCH v9 00/36] x86: enable FRED for x86-64 From: Sean Christopherson To: Xin3 Li Cc: "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" , Jonathan Corbet , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "x86@kernel.org" , "H . Peter Anvin" , Andy Lutomirski , Oleg Nesterov , Tony Luck , "K . Y . Srinivasan" , Haiyang Zhang , Wei Liu , Dexuan Cui , Paolo Bonzini , Wanpeng Li , Vitaly Kuznetsov , Peter Zijlstra , Jurgen Gross , Stefano Stabellini , Oleksandr Tyshchenko , Josh Poimboeuf , "Paul E . McKenney" , Catalin Marinas , Randy Dunlap , Steven Rostedt , Kim Phillips , Hyeonggon Yoo <42.hyeyoo@gmail.com>, "Liam R . Howlett" , Sebastian Reichel , "Kirill A . Shutemov" , Suren Baghdasaryan , Pawan Gupta , Jiaxi Chen , Babu Moger , Jim Mattson , Sandipan Das , Lai Jiangshan , Hans de Goede , Reinette Chatre , Daniel Sneddon , Breno Leitao , Nikunj A Dadhania , Brian Gerst , Sami Tolvanen , Alexander Potapenko , Andrew Morton , Arnd Bergmann , "Eric W . Biederman" , Kees Cook , Masami Hiramatsu , Masahiro Yamada , Ze Gao , Fei1 Li , Conghui , Ashok Raj , "Jason A . Donenfeld" , Mark Rutland , Jacob Pan , Jiapeng Chong , Jane Malalane , David Woodhouse , Boris Ostrovsky , Arnaldo Carvalho de Melo , Yantengsi , Christophe Leroy , Sathvika Vasireddy Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-edac@vger.kernel.org On Mon, Jul 31, 2023, Xin3 Li wrote: > > > This patch set enables the Intel flexible return and event delivery > > > (FRED) architecture for x86-64. > > > > ... > > > > > -- > > > 2.34.1 > > > > What is this based on? > > The tip tree master branch. > > > FYI, you're using a version of git that will (mostly) > > automatically generate the based, e.g. I do > > > > git format-patch --base=HEAD~$nr ... > > > > in my scripts, where $nr is the number of patches I am sending. My specific > > approaches requires HEAD-$nr to be a publicly visible object/commit, but that > > should be the case the vast majority of the time anyways. > > Are you talking about that you only got a subset of this patch set? No, I'm saying I don't want to waste a bunch of time tracking down exactly which commit a 36 patch series is based on. E.g. I just refreshed tip/master and still get: Applying: x86/idtentry: Incorporate definitions/declarations of the FRED external interrupt handler type error: sha1 information is lacking or useless (arch/x86/include/asm/idtentry.h). error: could not build fake ancestor Patch failed at 0024 x86/idtentry: Incorporate definitions/declarations of the FRED external interrupt handler type hint: Use 'git am --show-current-patch=diff' to see the failed patch > HPA told me he only got patches 0-25/36. > > And I got several undeliverable email notifications, saying > " > The following message to was undeliverable. > The reason for the problem: > 5.x.1 - Maximum number of delivery attempts exceeded. [Default] 450-'4.7.25 Client host rejected: cannot find your hostname, [134.134.136.31]' > " > > I guess there were some problems with the Intel mail system last night, > probably I should resend this patch set later. Yes, lore also appears to be missing patches. I grabbed the mbox off of KVM's patchwork instance.