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 lists.gnu.org (lists.gnu.org [209.51.188.17]) (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 624F4C433F5 for ; Fri, 22 Apr 2022 00:14:15 +0000 (UTC) Received: from localhost ([::1]:40410 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nhgwA-0006PO-1O for qemu-devel@archiver.kernel.org; Thu, 21 Apr 2022 20:14:14 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:58558) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nhgvP-0005jH-CE for qemu-devel@nongnu.org; Thu, 21 Apr 2022 20:13:27 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:57170) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nhgvL-0002AS-2R for qemu-devel@nongnu.org; Thu, 21 Apr 2022 20:13:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1650586400; 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: in-reply-to:in-reply-to:references:references; bh=JfUtC+huXvB+ctoh2cLQnrfQDElLCrre8Fy7ZiMq31Y=; b=ghJOsOsASC9nOAnmpZvruwkQmvzJ32lTCUQldh6HS4MivlYK8FS6/lBp+ti43k4ozlWuGJ V6pvttFPekfgSYGcHwrbGdIWfr1sNoTT/SGZbZgDL76JQX7p4e/NHqPIsNmIsUgKBv+bKM jflpQowkz+D6B+uY4upSFrLJ86Z2Pw0= Received: from mail-io1-f72.google.com (mail-io1-f72.google.com [209.85.166.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-477-Gq99chKJNjqR6EnK4BOYkw-1; Thu, 21 Apr 2022 20:13:19 -0400 X-MC-Unique: Gq99chKJNjqR6EnK4BOYkw-1 Received: by mail-io1-f72.google.com with SMTP id x13-20020a0566022c4d00b0065491fa5614so4346754iov.9 for ; Thu, 21 Apr 2022 17:13:19 -0700 (PDT) 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=JfUtC+huXvB+ctoh2cLQnrfQDElLCrre8Fy7ZiMq31Y=; b=RH27kYbcLPIl9kC4XHmFXoGCrSvxCiYuUNdHQDazCwOwcFVu3YTX9Rs9mGMReASSf/ VpoCaR8lUcM81wzjii0TCV8BB8YGcNNOs7bVWkrldDW8rgm5NepS1v4iqGoExfPpiza9 FGJLysjkz9J1luSMErd9DAzSBqUcvBQ/n7tnSYQdhW0OOmiSgTCaiwNp9k3mzwJJEzGC qd192LXK51rrfX03lQXYT6ktfz+U6YeBEQP4wtuJTI5Zt6eSsP/yorqgZSqxm2PbD5MH tgv0ugrmnQy0XZDvgTGpPLSGclJITKkQUhPZ7Dm9MQGz2dlsM4O2wOcF6JZ3kENxlXUb RA7g== X-Gm-Message-State: AOAM530CNNVv92dyi6KO85v+/IbRiJN7rTvim/Gut5kmh/C+zBbDxZC6 KXmDiVr2U5blUG6+GEB9bgXgYwz8sSDcARhjWvfimMf9LEbjxaMeZOcLKu0+fxHa3XP2KGiKZbJ Fk7ESQY4cBtStuJo= X-Received: by 2002:a05:6638:25b:b0:328:858d:9ac1 with SMTP id w27-20020a056638025b00b00328858d9ac1mr990433jaq.198.1650586398218; Thu, 21 Apr 2022 17:13:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz/bcDXNwI5wC4AkX4PLhbjMnYWyAmzrB8K/0DyE90Fh7+m49srzfpK3MnZO18u6xn8y3KLcw== X-Received: by 2002:a05:6638:25b:b0:328:858d:9ac1 with SMTP id w27-20020a056638025b00b00328858d9ac1mr990419jaq.198.1650586397676; Thu, 21 Apr 2022 17:13:17 -0700 (PDT) Received: from xz-m1.local (cpec09435e3e0ee-cmc09435e3e0ec.cpe.net.cable.rogers.com. [99.241.198.116]) by smtp.gmail.com with ESMTPSA id a1-20020a923301000000b002cae7560bfesm295405ilf.62.2022.04.21.17.13.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 21 Apr 2022 17:13:17 -0700 (PDT) Date: Thu, 21 Apr 2022 20:13:15 -0400 From: Peter Xu To: Jason Wang Subject: Re: [PATCH V2 1/4] intel-iommu: don't warn guest errors when getting rid2pasid entry Message-ID: References: <20220321055429.10260-1-jasowang@redhat.com> <20220321055429.10260-2-jasowang@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=170.10.129.124; envelope-from=peterx@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -28 X-Spam_score: -2.9 X-Spam_bar: -- X-Spam_report: (-2.9 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.082, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "Tian, Kevin" , "Liu, Yi L" , "yi.y.sun@linux.intel.com" , "qemu-devel@nongnu.org" , "mst@redhat.com" Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Wed, Mar 30, 2022 at 04:36:36PM +0800, Jason Wang wrote: > > If not, do we want to apply this version scheme only when it > > reaches the production quality or also in the experimental phase? > > Yes. E.g if we think scalable mode is mature, we can enable 3.0. Sorry to come back to the discussion late.. I'd say unless someone (or some organization) strongly ask for a stable interface for scalable mode (better with some developer looking after it along with the organization), until then we start with versioning. Otherwise I hope we can be free to break the interface assuming things are still evolving, just like the spec. Thanks, -- Peter Xu