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 X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6D8EFC433E0 for ; Tue, 23 Jun 2020 10:26:37 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id DAB4E2072E for ; Tue, 23 Jun 2020 10:26:36 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="UQpR6sez"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="UQpR6sez" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DAB4E2072E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 49rjB2106lzDqS6 for ; Tue, 23 Jun 2020 20:26:34 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=redhat.com (client-ip=207.211.31.81; helo=us-smtp-delivery-1.mimecast.com; envelope-from=pbonzini@redhat.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=UQpR6sez; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=UQpR6sez; dkim-atps=neutral Received: from us-smtp-delivery-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 49rj802mjdzDqGt for ; Tue, 23 Jun 2020 20:24:47 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1592907884; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rM1BfodItBtK7hezukdZSeFePaoeuCpD4E8vQ9IKGDU=; b=UQpR6sezXewhvjEHd2WzS0gocnChl5WNNacxcdC8B9WNKzsCtUypWz+r9hWoh8kCTNfiGO 7IJMEN+Cy4+HzZuK6yLUPQVExZOll17urXYwSEgQF+URC4EV3tx6KxXsB8lamAzWc+XCn1 zD5kzbEzLsOdop/Nbtx9DpEYNbcVqQo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1592907884; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rM1BfodItBtK7hezukdZSeFePaoeuCpD4E8vQ9IKGDU=; b=UQpR6sezXewhvjEHd2WzS0gocnChl5WNNacxcdC8B9WNKzsCtUypWz+r9hWoh8kCTNfiGO 7IJMEN+Cy4+HzZuK6yLUPQVExZOll17urXYwSEgQF+URC4EV3tx6KxXsB8lamAzWc+XCn1 zD5kzbEzLsOdop/Nbtx9DpEYNbcVqQo= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-355-izHYmbAxPCGbeOSfPttdPA-1; Tue, 23 Jun 2020 06:24:42 -0400 X-MC-Unique: izHYmbAxPCGbeOSfPttdPA-1 Received: by mail-wm1-f69.google.com with SMTP id p24so3459556wmc.1 for ; Tue, 23 Jun 2020 03:24:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=K0VMF+zOglKc79uK7nAPfjf+HV37t2ditCPtYi6hRnc=; b=aJLJLBQ4U7gr//kpWKBdoAjjCDpVZmZwLYC1AxF1Up91YZDh4xvdN/u/N2leJnVKJT fKLXrHVToZJQoLr3P1lfORVRHmRKH36paR7pm4uY9cfxz9a01n2BZgiUirIccJd0eYht tVQpVlWZnjPDypd4SuhWvTzuS/m2mtEaD05rT0jOvKs2jLQmWKgiAdbRny9eLYtjZJhO 4kq4XiDcLiGxNVircemzMNB08jJW7yrEEDWbc1obvk9LEV2qoAYrdspbg+S2jAowLlsT d1aWWGBiwrxdT6MP/j0M4WmvPerJuJZUhaGLSKgCF90UrL0ad7OK7QSqnd9eUg44xUg8 Twmg== X-Gm-Message-State: AOAM533HM7SuzKpVrFqBDMXqfBqcLvEgErZONfqgTymzLnNuPjs9VZB5 1KtEBxk96kois13OwaOfmx4OyQNqkx3D5A5/rf+MIr99h0gv5qvi0I9iiZkpo5oja0IRY4jdYAx h07ESwOvrH0wp5WMOwmIkUlQPmw== X-Received: by 2002:a05:6000:ce:: with SMTP id q14mr16454574wrx.294.1592907881340; Tue, 23 Jun 2020 03:24:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw7GKxnJWV0b4Mz/7lWJjdPl3+rZwUgIO80Ac5HDjj13PmRVjDey+yK0l49hJjTmncjlmTnYw== X-Received: by 2002:a05:6000:ce:: with SMTP id q14mr16454534wrx.294.1592907881013; Tue, 23 Jun 2020 03:24:41 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:24f5:23b:4085:b879? ([2001:b07:6468:f312:24f5:23b:4085:b879]) by smtp.gmail.com with ESMTPSA id c66sm3351206wma.20.2020.06.23.03.24.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 23 Jun 2020 03:24:40 -0700 (PDT) Subject: Re: [PATCH v4 0/7] clean up redundant 'kvm_run' parameters To: Tianjia Zhang , tsbogend@alpha.franken.de, paulus@ozlabs.org, mpe@ellerman.id.au, benh@kernel.crashing.org, borntraeger@de.ibm.com, frankja@linux.ibm.com, david@redhat.com, cohuck@redhat.com, heiko.carstens@de.ibm.com, gor@linux.ibm.com, sean.j.christopherson@intel.com, vkuznets@redhat.com, wanpengli@tencent.com, jmattson@google.com, joro@8bytes.org, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com, maz@kernel.org, james.morse@arm.com, julien.thierry.kdev@gmail.com, suzuki.poulose@arm.com, christoffer.dall@arm.com, peterx@redhat.com, thuth@redhat.com, chenhuacai@gmail.com References: <20200427043514.16144-1-tianjia.zhang@linux.alibaba.com> <3a2bee8b-20b4-5d33-7d12-09c374a5afde@linux.alibaba.com> From: Paolo Bonzini Message-ID: Date: Tue, 23 Jun 2020 12:24:38 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <3a2bee8b-20b4-5d33-7d12-09c374a5afde@linux.alibaba.com> Content-Language: en-US X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org, linux-mips@vger.kernel.org, kvm-ppc@vger.kernel.org, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On 23/06/20 12:00, Tianjia Zhang wrote: > > > On 2020/6/23 17:42, Paolo Bonzini wrote: >> On 27/04/20 06:35, Tianjia Zhang wrote: >>> In the current kvm version, 'kvm_run' has been included in the >>> 'kvm_vcpu' >>> structure. For historical reasons, many kvm-related function parameters >>> retain the 'kvm_run' and 'kvm_vcpu' parameters at the same time. This >>> patch does a unified cleanup of these remaining redundant parameters. >>> >>> This series of patches has completely cleaned the architecture of >>> arm64, mips, ppc, and s390 (no such redundant code on x86). Due to >>> the large number of modified codes, a separate patch is made for each >>> platform. On the ppc platform, there is also a redundant structure >>> pointer of 'kvm_run' in 'vcpu_arch', which has also been cleaned >>> separately. >> >> Tianjia, can you please refresh the patches so that each architecture >> maintainer can pick them up?  Thanks very much for this work! >> >> Paolo >> > > No problem, this is what I should do. > After I update, do I submit separately for each architecture or submit > them together in a patchset? You can send them together. Paolo