Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp2967450ybt; Mon, 29 Jun 2020 11:41:51 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzSSKKaZUx0lRAjt6rIAaX4r3yz508ZqrYM1rtc5iA5LOo7VR0Od8Vq6ZkVFaj2ZC+J2qw6 X-Received: by 2002:aa7:c987:: with SMTP id c7mr18633987edt.268.1593456111793; Mon, 29 Jun 2020 11:41:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593456111; cv=none; d=google.com; s=arc-20160816; b=P2yF4yUqGUF4PxzRy4v9c7QL6sZHsw6CEmEV6mKC/Y9tbSnzDBG89V4z2CPDBaNJ6X utu5s/X5ttbApD0s3H2Txqb7WDLLzfrTMnLOCg6Ti6z1hxkbFDeEloGzCwj4EdvRH4za xHvrBhSZsY2C9wFvExexz/ySD4hn9aIMbeR6y6eQKY3NSvK1LBxrAYaGga1Qcic0arKQ jsNRQ5kE9RzW1qV8wqNHDaWdrL9iBc17Sfp0VRpdTNX3nje7gndKvaiuMXpm7UeP3MRz JphZg4op1fjyqX8IM2Uh0IXVLvlJkD+u/g/64mlJ7ffuxwTQjZ5VKUTp8co1OyfOUqoS Yetw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=Iiom3LNVi9ET0XgfPNiU1I3DflByt3ZNInrS8hmdp2U=; b=RnY52D8J9EpZbBjT48KegOTRtInA5YbVSujvcmCEvkaKGlQb3YEpDWqS5EnD05KqSJ HLJeLcMomNaiRLm6cCPKbddDCoMoBUf2jcB/g14Vk/mIBTi27iOYqymjsgJIeRX7z/5i lbWeKRPtuTrhpNM+dRJeCVc1hqK2/jLQwNYx4hZTx6Bb3DNbxE+AHtrrWXwu00a8f12t 4F91Oifibb6kFIeov+rZNBuBm00ZF0okuaywcDTqw1NBrlHqyZzsjn6mdRs3hFweMDR1 gGlQ5Lkf+A5bNtBFY4ZN8VcLvj8AzBm71LTZ9lvTz8dRtDilXEXYBWSBjK8E/CKKQ+So mV7Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Dm4DRQiQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c12si203485edv.217.2020.06.29.11.41.28; Mon, 29 Jun 2020 11:41:51 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Dm4DRQiQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726153AbgF2SiQ (ORCPT + 99 others); Mon, 29 Jun 2020 14:38:16 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:20021 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727996AbgF2SiN (ORCPT ); Mon, 29 Jun 2020 14:38:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1593455891; 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=Iiom3LNVi9ET0XgfPNiU1I3DflByt3ZNInrS8hmdp2U=; b=Dm4DRQiQ6fUDiw0ODYfzRHM0l5n+/OCax4tsmQVFEte4dJzOhv+iMeaX7PPDTf5oyU2Cvy 0CJwQz6V7YaBivk2kU2ABaaWuXVz4uW6YjOtq4MYIn+3EyNMsgXd1uWHXxibfnQTObK24F 8SkzU6q4SO8an7e201QLwzG41YBOs7A= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-455-zq5FJK0EM5iWibiXsRdCPQ-1; Mon, 29 Jun 2020 02:33:44 -0400 X-MC-Unique: zq5FJK0EM5iWibiXsRdCPQ-1 Received: by mail-wm1-f72.google.com with SMTP id g138so9169162wme.7 for ; Sun, 28 Jun 2020 23:33:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Iiom3LNVi9ET0XgfPNiU1I3DflByt3ZNInrS8hmdp2U=; b=bcJwot1rvvs31r6/bGkj69+UdKhSSU3V29QHO2CN/GXz2IBDw0gXkenJA5N8Fhy7pP yv6SjNdVYVEEVRlWaKnFo2or0J342R83z/tPKQ4Lu+9avZ1h4gk4KJYgOf2tHqquDaxv dKRcHykJPRBatK8yz/XMHye1JGzGO6WzGc6sLB70r9CYKpLVQXCy2bR545Ldhq8kzV0X D5yd0nT6kg01GFPFY99Pd6GrVCh4TVc6u6XvlP94eFK3nSkbkCZoOeL6w1dRROFpCrtp YSGj1o6IHwbwbP+aCQYAekMjaFjAV69JCyzGFY0hANWF6WxxyKy3HdVXawA+ztSCitb3 MamQ== X-Gm-Message-State: AOAM530kykZRCy2aHGfDYcu1cKbcr+mYv9MGX3cJp5TMQP037huGMZHQ 1J5pGyazveM8pQupjHGQXa4NmqbqUiizQhjwevBkf+beDJiPsUI+FM719+Cn3xROx9v64wgxE2c pK53+Jv4h2oM6W7hincD04d3/ X-Received: by 2002:adf:8067:: with SMTP id 94mr14821901wrk.427.1593412423677; Sun, 28 Jun 2020 23:33:43 -0700 (PDT) X-Received: by 2002:adf:8067:: with SMTP id 94mr14821888wrk.427.1593412423531; Sun, 28 Jun 2020 23:33:43 -0700 (PDT) Received: from redhat.com (bzq-79-182-31-92.red.bezeqint.net. [79.182.31.92]) by smtp.gmail.com with ESMTPSA id s8sm41059111wru.38.2020.06.28.23.33.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 28 Jun 2020 23:33:42 -0700 (PDT) Date: Mon, 29 Jun 2020 02:33:39 -0400 From: "Michael S. Tsirkin" To: Peng Fan Cc: Stefano Stabellini , "boris.ostrovsky@oracle.com" , "jgross@suse.com" , "konrad.wilk@oracle.com" , "jasowang@redhat.com" , "x86@kernel.org" , "xen-devel@lists.xenproject.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "iommu@lists.linux-foundation.org" , "virtualization@lists.linux-foundation.org" , dl-linux-imx Subject: Re: [PATCH] xen: introduce xen_vring_use_dma Message-ID: <20200629023225-mutt-send-email-mst@kernel.org> References: <20200624050355-mutt-send-email-mst@kernel.org> <20200624163940-mutt-send-email-mst@kernel.org> <20200624181026-mutt-send-email-mst@kernel.org> <20200626110629-mutt-send-email-mst@kernel.org> <20200629022124-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 29, 2020 at 06:25:41AM +0000, Peng Fan wrote: > > > > > Anyway, re-reading the last messages of the original thread [1], > > > > > it looks like Peng had a clear idea on how to fix the general issue. > > > > > Peng, what happened with that? > > > > > > We shrinked the rpmsg reserved area to workaround the issue. > > > So still use the dma apis in rpmsg. > > > > > > But here I am going to address domu android trusty issue using virtio. > > > > My suggestion is to first of all fix DMA API so it works properly. > > Could you please elaborate more details? > > You mean the DMA API usage of rpmsg? Or xen domu dma_ops? > > Thanks, > Peng. Not 100% sure but I think xen dma ops. -- MST