Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp18845568rwd; Wed, 28 Jun 2023 01:12:43 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4tUhUpSOf3Dgks+br1o/GEDOAD8sjBMYLWYgU4zPLlpxPffJLzQg6sJZ9le598dT/M54ad X-Received: by 2002:a05:6402:649:b0:51d:af4f:c8d1 with SMTP id u9-20020a056402064900b0051daf4fc8d1mr2500819edx.38.1687939963013; Wed, 28 Jun 2023 01:12:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687939962; cv=none; d=google.com; s=arc-20160816; b=yyadNuB4XpxQPA5/NcrB75Ky1YUO5nhH2Op/z/1wpcrG7a4RBkonzvW8JrM5ztZ9n6 ttigP36WjPIX5JmVqcG6GjFY5az+BrT/QQGYn43iDbA+XA01G/F8s7VK85wyK+8xTyzu Py7OSkHh+o1H79f/stOJoO3LJo2mrY2pdOBbM5eCYbvaZaM8pT39mAjLmMLgjp5tBBDY +qGms2NvBWS9q9zPkKvrDDFFQi0GuuayqBeH8tQb9q6LqtM4xGUR3p8uslTC7hYBML15 CG26XvmDyaWE82ONPT1M/iR5TWNMu/6i2fMnn/cDH/l4E42mthDs2yOPj+7Bz/rqkq0M FM8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=zUUe5aIzNm8Qe2LuuasY2t7ArszuQD81zWr0J0PNSeI=; fh=8RlNyjxcUdxxEW5IivFakwWHVNOTqaSUuSDSk9lXu3k=; b=Dq7yIvm6TLe87KGSOW9ttXUL+tTDFlqtbxxAveDBUJJp4ExVAVDv7yclIB1HEEosNF zpNspGTxNYAEXVxpbKevxaQ40XOFy9BpWOXJt8WuWzBz5WD9M9Lhkc7hDrbKs+GtIXFR eN5dL1mBjWTKzepqpQwqUsnHVSz/Fz3vIOii4rxt0N7w068uDLS3culcd6USOt2RaY8d SS/xrRhZT/9J1O9XhpxKTsjFVUubLRcx/znOakIqwOaXqQjDkfSohyrXOBzPsOF19Mv7 YicJcQ33Kyqsya5WunV1+VYp/HvXtxHwDBFU0Fqewmm4t723rA1o/OQnVm26MKO1E8BU U+Ig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=JSEuk7V0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a17-20020aa7d911000000b0051daf1aece3si1419524edr.202.2023.06.28.01.12.01; Wed, 28 Jun 2023 01:12:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=JSEuk7V0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233900AbjF1IKW (ORCPT + 99 others); Wed, 28 Jun 2023 04:10:22 -0400 Received: from mga09.intel.com ([134.134.136.24]:44408 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233122AbjF1IFt (ORCPT ); Wed, 28 Jun 2023 04:05:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1687939549; x=1719475549; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=nPgXph7jE9MY5L1ghfiQHOSu+yYZgBulZjzQgnxPKMQ=; b=JSEuk7V04sLPGc7ejjogysXnTHBVxkMrHx1LWYS5XQ4TZs1mux9gKLU0 TnNqNA5O3xZuUdd2L1M63DrG8jzv4F0BIj0ZhrCUIIq2l5oa8ExYiOL6P gw6MjDGlVTSzMHQFF5M9mNKvenLiy4sdHYBaqZoQ/BaD5Xc3dLof5jFR0 nV31xVOtwQivvhTz5mBRXNQMmLM6o9vFrpvfSgKGQ4IYFaI6gP9bGCZBU 9XJUaOTgitSwWx3aghTxcpFFZmyRXn8QnYtd8TfC7ei0wOEVWzXNHYaX/ M4ersbDC5hJUSTnQcciM69MtLfacMLjL4R+fzWAVGnbrytqztzMMnPUzm g==; X-IronPort-AV: E=McAfee;i="6600,9927,10754"; a="364323158" X-IronPort-AV: E=Sophos;i="6.01,164,1684825200"; d="scan'208";a="364323158" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Jun 2023 00:28:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10754"; a="829976081" X-IronPort-AV: E=Sophos;i="6.01,164,1684825200"; d="scan'208";a="829976081" Received: from zengguan-mobl1.ccr.corp.intel.com (HELO [10.238.2.33]) ([10.238.2.33]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Jun 2023 00:28:34 -0700 Message-ID: <1313445e-1bd2-f559-edd5-e07e0d9ccda9@intel.com> Date: Wed, 28 Jun 2023 15:27:58 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [PATCH v1 1/6] KVM: x86: Consolidate flags for __linearize() To: Sean Christopherson Cc: Paolo Bonzini , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , H Peter Anvin , "kvm@vger.kernel.org" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , Binbin Wu References: <20230601142309.6307-1-guang.zeng@intel.com> <20230601142309.6307-2-guang.zeng@intel.com> Content-Language: en-US From: Zeng Guang In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/28/2023 1:40 AM, Sean Christopherson wrote: > On Thu, Jun 01, 2023, Zeng Guang wrote: >> From: Binbin Wu >> >> Define a 32-bit parameter and consolidate the two bools into it. > Please write changelogs so that they make sense without the context of the shortlog. > In isolation, the above provides zero context. And there's no need to provide a > play-by-play description of the change, e.g. this can be: > > Consolidate __linearize()'s @write and @fetch into a set of flags so that > additional flags can be added without needing more/new boolean parameters, > e.g. to precisely identify the access type for LASS. > >> __linearize() has two bool parameters write and fetch. And new flag >> will be needed to support new feature (e.g. LAM needs a flag to skip > s/LAM/LASS > >> address untag under some conditions). > Looks like this was copy+pasted LAM. AIUI, there is no untagging in LASS. Please, > please take the time to proofread what you're posting. To you it's a minor typo, > to others, incorrect statements like this can create a lot of confusion. LASS and LAM attempts to apply same emulator framework. This patch as prerequisite directly uses the one of LAM patches. But no excuse, we will modify it to non-feature and hardware specific as you suggested. Thanks.