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 AEB26C433EF for ; Fri, 25 Mar 2022 23:02:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234095AbiCYXEQ (ORCPT ); Fri, 25 Mar 2022 19:04:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42106 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234070AbiCYXEO (ORCPT ); Fri, 25 Mar 2022 19:04:14 -0400 Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8371A527EF for ; Fri, 25 Mar 2022 16:02:39 -0700 (PDT) Received: by mail-pl1-x634.google.com with SMTP id g3so9713330plo.6 for ; Fri, 25 Mar 2022 16:02:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=RDTJ2bGKsyg8KfpwWQiMrlouH1KCGMV8rUa8lEFeJps=; b=aYOIVYtu80RxHpdFnwvgx3yyi0P7hN/OMzb9J5wSiiz5f7pX3vdtpLyEAxevtyKn// xeVFmsc4y9tOPUNRtNE5cCfdXy9Cot2H0/mUElJMCy32P4tQ1dts2wgsV8qcJg7h0QZ7 qub9UEznnxnJJzO+tSatq2BvxNKTWUvofLatMBHCBpAtyB+jM6RzVDOLE7vfjLvmzHkb e1B8CInnGUTymswRzzVS+TUbSQH9e8ywFlz/UzPxzvlvcj7x0U7VB4em6qGIeltd/PI5 6ExzVd2aHnbOTjM61USlbbi4c+rlOtN6ImElf9CxdR2m+eINJW5fh7Kkx7RUMM45UQUv NGRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=RDTJ2bGKsyg8KfpwWQiMrlouH1KCGMV8rUa8lEFeJps=; b=CBXE0qgz+w6Yes5C+eAGov139VHJCvTirZCywdEtArVRmJXCM+WqgR1Lf2FGBAQPjD epFoPijaSxtj4TREVm0xFjcu/DNf/PvBoWDZDv0ww2oU1dc1PVFCCbtTTwQQ90hA/qvR VMzXO4sByc8pOINtlYtVV5AdnySlyXNUHb0z8cko8kntMIHQ5boQVUOtYLKQQ6Wg5Ajq 0k2KHqN47K+tpsPUx4EV48/Q5UuUue4ud4PGwwwNRQT+4d0XZsopbIfZPujvP0IB8fvD 1A7EPccpP+ZRizVBmK/o2h+/DJhEJFxy/flTo5aNy4M7tncGQUYo8QyYqTDfuFk2+MwM tRlA== X-Gm-Message-State: AOAM531xOEhvb6cVl+Hogem8RIMNvaUR37TEq3yWF89oIyvLzRkLdAHo VWq2UV5W+3KUUY6lA2Opq4jiZA== X-Google-Smtp-Source: ABdhPJxmNHF3zDTC1ndQwKMHNRa2JwCcCjESyisIvqbKDWHfpEBodDTpGP7VSexHnij3Pa5djLC5yw== X-Received: by 2002:a17:902:ce8b:b0:154:42e2:924e with SMTP id f11-20020a170902ce8b00b0015442e2924emr14096487plg.138.1648249358691; Fri, 25 Mar 2022 16:02:38 -0700 (PDT) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id o24-20020a17090a5b1800b001c6aaafa5fbsm7030187pji.24.2022.03.25.16.02.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 25 Mar 2022 16:02:38 -0700 (PDT) Date: Fri, 25 Mar 2022 23:02:34 +0000 From: Sean Christopherson To: "Maciej S. Szmigiero" Cc: Maxim Levitsky , Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Oliver Upton , Peter Shier Subject: Re: [PATCH 00/21] KVM: x86: Event/exception fixes and cleanups Message-ID: References: <20220311032801.3467418-1-seanjc@google.com> <08548cb00c4b20426e5ee9ae2432744d6fa44fe8.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 25, 2022, Maciej S. Szmigiero wrote: > So, what's the plan here: is your patch set Sean considered to supersede > Maxim's earlier proposed changes or will you post an updated patch set > incorporating at least some of them? Next step is to reach a consensus on how we want to solve the problem (or if we can't reach consensus, until Paolo uses his special powers). I definitely won't post anything new until there's more conversation. > I am asking because I have a series that touches the same general area > of KVM [1] and would preferably have it based on the final form of the > event injection code to avoid unforeseen negative interactions between > these changes. I don't think you need to do anything, at a glance your changes are orthogonal even though they have similar themes. Any conflicts should be minor.