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.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 854F6C8300A for ; Thu, 30 Apr 2020 10:39:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 57E792137B for ; Thu, 30 Apr 2020 10:39:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1588243166; bh=6+7qBBamWTT9w7zClGZROm5AeCOL7MN9qOqe5yevm90=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=UkfjEkAIeUlrzKblw0KVsRNVYYj62g6Zay6s/8cgqn36BxD2NFZ2B6mrXsqrx6NWQ a/Qo2KEKLrS82Sr2Pe2ZGao4qmw3GhM2ggFdMAQ412EiInUFauV7+IljkodlvvvAe5 MfeTMdt+0Tl6tgxpECE3tLBMIaTRKN/QLRzLm8rw= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726809AbgD3KjZ (ORCPT ); Thu, 30 Apr 2020 06:39:25 -0400 Received: from mail.kernel.org ([198.145.29.99]:55854 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726427AbgD3KjZ (ORCPT ); Thu, 30 Apr 2020 06:39:25 -0400 Received: from willie-the-truck (236.31.169.217.in-addr.arpa [217.169.31.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A3CF920838; Thu, 30 Apr 2020 10:39:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1588243164; bh=6+7qBBamWTT9w7zClGZROm5AeCOL7MN9qOqe5yevm90=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=j4ZaDYWlFfnjJ0Kk6dtybxWMdijfCyiwyxZsPRioDIEIjW2Pq/Kffjmqjr3+J0Ejl JR4YgwOGru7gDKzTHRc+/mOOsVLTS5ejWCp0tS62mKzaXXuC93LMhd13Rxno4+GTvA qmCLkIDor0yLvS+hxfn7Nw42bPZSZSdBu25gx7Rk= Date: Thu, 30 Apr 2020 11:39:19 +0100 From: Will Deacon To: Srivatsa Vaddagiri Cc: konrad.wilk@oracle.com, mst@redhat.com, jasowang@redhat.com, jan.kiszka@siemens.com, stefano.stabellini@xilinx.com, iommu@lists.linux-foundation.org, virtualization@lists.linux-foundation.org, virtio-dev@lists.oasis-open.org, tsoni@codeaurora.org, pratikp@codeaurora.org, christoffer.dall@arm.com, alex.bennee@linaro.org, linux-kernel@vger.kernel.org Subject: Re: [RFC/PATCH 0/1] virtio_mmio: hypervisor specific interfaces for MMIO Message-ID: <20200430103919.GF19932@willie-the-truck> References: <1588240976-10213-1-git-send-email-vatsa@codeaurora.org> <20200430100821.GC19932@willie-the-truck> <20200430102939.GG5097@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200430102939.GG5097@quicinc.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Vatsa, On Thu, Apr 30, 2020 at 03:59:39PM +0530, Srivatsa Vaddagiri wrote: > * Will Deacon [2020-04-30 11:08:22]: > > > > This patch is meant to seek comments. If its considered to be in right > > > direction, will work on making it more complete and send the next version! > > > > What's stopping you from implementing the trapping support in the > > hypervisor? Unlike the other patches you sent out, where the guest memory > > is not accessible to the host, there doesn't seem to be any advantage to > > not having trapping support, or am I missing something here? > > I have had this discussion with hypervisor folks. They seem to be > concerned about complexity of having a VM's fault be handled in another > untrusted VM. They are not keen to add MMIO support. Right, but I'm concerned about forking the implementation from the spec and I'm not keen to add these hooks ;) What does your hook actually do? I'm assuming an HVC? If so, then where the fault is handled seems to be unrelated and whether the guest exit is due to an HVC or a stage-2 fault should be immaterial. In other words, I don't follow why the trapping mechanism necessitates the way in which the fault is handled. Will 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, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,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 1A0A1C8300C for ; Thu, 30 Apr 2020 10:39:27 +0000 (UTC) Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138]) (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 DC0F5214D8 for ; Thu, 30 Apr 2020 10:39:26 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="j4ZaDYWl" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DC0F5214D8 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=iommu-bounces@lists.linux-foundation.org Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id AF3CD87E08; Thu, 30 Apr 2020 10:39:26 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vZDqIQE4Azij; Thu, 30 Apr 2020 10:39:26 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [140.211.9.56]) by whitealder.osuosl.org (Postfix) with ESMTP id 3A3AE8517C; Thu, 30 Apr 2020 10:39:26 +0000 (UTC) Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id 1E903C0864; Thu, 30 Apr 2020 10:39:26 +0000 (UTC) Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id A009CC016F; Thu, 30 Apr 2020 10:39:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by hemlock.osuosl.org (Postfix) with ESMTP id 86C0588304; Thu, 30 Apr 2020 10:39:25 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from hemlock.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T+COBPeX9+Oh; Thu, 30 Apr 2020 10:39:25 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by hemlock.osuosl.org (Postfix) with ESMTPS id 1F9AB880B3; Thu, 30 Apr 2020 10:39:25 +0000 (UTC) Received: from willie-the-truck (236.31.169.217.in-addr.arpa [217.169.31.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A3CF920838; Thu, 30 Apr 2020 10:39:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1588243164; bh=6+7qBBamWTT9w7zClGZROm5AeCOL7MN9qOqe5yevm90=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=j4ZaDYWlFfnjJ0Kk6dtybxWMdijfCyiwyxZsPRioDIEIjW2Pq/Kffjmqjr3+J0Ejl JR4YgwOGru7gDKzTHRc+/mOOsVLTS5ejWCp0tS62mKzaXXuC93LMhd13Rxno4+GTvA qmCLkIDor0yLvS+hxfn7Nw42bPZSZSdBu25gx7Rk= Date: Thu, 30 Apr 2020 11:39:19 +0100 From: Will Deacon To: Srivatsa Vaddagiri Subject: Re: [RFC/PATCH 0/1] virtio_mmio: hypervisor specific interfaces for MMIO Message-ID: <20200430103919.GF19932@willie-the-truck> References: <1588240976-10213-1-git-send-email-vatsa@codeaurora.org> <20200430100821.GC19932@willie-the-truck> <20200430102939.GG5097@quicinc.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20200430102939.GG5097@quicinc.com> User-Agent: Mutt/1.10.1 (2018-07-13) Cc: tsoni@codeaurora.org, virtio-dev@lists.oasis-open.org, mst@redhat.com, jan.kiszka@siemens.com, jasowang@redhat.com, konrad.wilk@oracle.com, christoffer.dall@arm.com, virtualization@lists.linux-foundation.org, alex.bennee@linaro.org, iommu@lists.linux-foundation.org, stefano.stabellini@xilinx.com, pratikp@codeaurora.org, linux-kernel@vger.kernel.org X-BeenThere: iommu@lists.linux-foundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Development issues for Linux IOMMU support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: iommu-bounces@lists.linux-foundation.org Sender: "iommu" Hi Vatsa, On Thu, Apr 30, 2020 at 03:59:39PM +0530, Srivatsa Vaddagiri wrote: > * Will Deacon [2020-04-30 11:08:22]: > > > > This patch is meant to seek comments. If its considered to be in right > > > direction, will work on making it more complete and send the next version! > > > > What's stopping you from implementing the trapping support in the > > hypervisor? Unlike the other patches you sent out, where the guest memory > > is not accessible to the host, there doesn't seem to be any advantage to > > not having trapping support, or am I missing something here? > > I have had this discussion with hypervisor folks. They seem to be > concerned about complexity of having a VM's fault be handled in another > untrusted VM. They are not keen to add MMIO support. Right, but I'm concerned about forking the implementation from the spec and I'm not keen to add these hooks ;) What does your hook actually do? I'm assuming an HVC? If so, then where the fault is handled seems to be unrelated and whether the guest exit is due to an HVC or a stage-2 fault should be immaterial. In other words, I don't follow why the trapping mechanism necessitates the way in which the fault is handled. Will _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu