Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5593367imu; Tue, 29 Jan 2019 23:44:54 -0800 (PST) X-Google-Smtp-Source: ALg8bN7Ad0XV/DB5tIgLaA9t9wN15kiBkoEXUf/ydbCm4+BaM2COyzAi9OT/XiNoB9dMd+m+84vr X-Received: by 2002:a62:55c4:: with SMTP id j187mr29337558pfb.129.1548834294810; Tue, 29 Jan 2019 23:44:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548834294; cv=none; d=google.com; s=arc-20160816; b=JyOjTNgdb68nAvhxQwXri5ZUNANF7pz6reMOFivRMnjuhrdhAU5LpTuRkuXnWTahog PsuY1vW9w5lv5uokghJyhXv18F36X3i2fKL0alumTxOq8m5O/tjCSTs5Yj0MJrZ8rSuG Yt4AZKZiMbcJBY4nLggAIesjz7Q4iLUzE/3Yl3FQyx4JKSX6jE5wQ+esb3oHAsSDklvp 1201FFU/CKBxH9/G2N5qAhOhVRNnGxG+a+740FFNsNSC6hMGl9uY7NehGWUQok5AklPK /u9u+rCw/nkQ3WrkoCNPlbD6lb2MO83wryi9TzK903gKMyHARPaUlizV4xnXIMQcE3IS /PsA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=XmvZkVzyhLpoF+Ie4K1VY01aqHx2WItp2XA8GRSGdPI=; b=HfYYjfAk+863DSZU1jBKdgfg6xsAwzFA5vQthSKsngty8QZmzv3HMHvoaGNpbU7AL8 lQDr17iDTbs9H3rsh7BXR7gzn7IGBTKcOxDlkGygQMEORDqn5dA3PkoRvUbBJcEDJOwf Fxhs2iw2iL9g1QLFxFekBVjl+E4wu10ITix24gv5QBTWXsSsmLNwvd1zCU/+ai9Kejpq IaznxOB7nk8/SAm7PNvHvlCiNE3i7UjB+InYI93mjvH7DVr7cmURU3HRbwFbuvelGBFg HKpo6Yf6XEB5/+f03ZYKZ2dIESAgPEi+miOoWV82V+AxihIrhMacg5Fx0PzYHcfu3Ja5 ZpiA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f5si720378plo.422.2019.01.29.23.44.39; Tue, 29 Jan 2019 23:44:54 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730107AbfA3Ho3 (ORCPT + 99 others); Wed, 30 Jan 2019 02:44:29 -0500 Received: from verein.lst.de ([213.95.11.211]:50668 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725819AbfA3Ho3 (ORCPT ); Wed, 30 Jan 2019 02:44:29 -0500 Received: by newverein.lst.de (Postfix, from userid 2407) id 9623068CEC; Wed, 30 Jan 2019 08:44:27 +0100 (CET) Date: Wed, 30 Jan 2019 08:44:27 +0100 From: Christoph Hellwig To: "Michael S. Tsirkin" Cc: Jason Wang , Thiago Jung Bauermann , virtualization@lists.linux-foundation.org, linuxppc-dev@lists.ozlabs.org, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Christoph Hellwig , David Gibson , Alexey Kardashevskiy , Paul Mackerras , Benjamin Herrenschmidt , Ram Pai , Jean-Philippe Brucker Subject: Re: [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted Message-ID: <20190130074427.GA29516@lst.de> References: <87zhrj8kcp.fsf@morokweng.localdomain> <87womn8inf.fsf@morokweng.localdomain> <20190129134750-mutt-send-email-mst@kernel.org> <6c68f7f7-1b28-6eba-9b8b-2c32efac9701@redhat.com> <20190129213137-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190129213137-mutt-send-email-mst@kernel.org> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 29, 2019 at 09:36:08PM -0500, Michael S. Tsirkin wrote: > This has been discussed ad nauseum. virtio is all about compatibility. > Losing a couple of lines of code isn't worth breaking working setups. > People that want "just use DMA API no tricks" now have the option. > Setting a flag in a feature bit map is literally a single line > of code in the hypervisor. So stop pushing for breaking working > legacy setups and just fix it in the right place. I agree with the legacy aspect. What I am missing is an extremely strong wording that says you SHOULD always set this flag for new hosts, including an explanation why.