From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 95EC723A98A for ; Wed, 2 Apr 2025 14:58:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743605893; cv=none; b=e6AF0WVRDasTDlKag+kSnPArv6JjLxWb983s1QEo4MRpC9ThCfUcbcQHGtPuwxH4pUO7nsefm++J9e/Mk3JaRVEsM8H1sULyZaNjhlhFydYdVMgQMeavE2i6JeKb+bXEl2SqFs+QTBXvjl0lljKqtYnHVsHej44sQSP4rLaT7q0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743605893; c=relaxed/simple; bh=7qjDoKy6T4RUbyZPwTCSPFSHXYhJvifIH6d2qlp7tLo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=adbOutYSJAkuoH0vPZLv83omKd4iGmK+5+zDQ78xnXKM3QaS6f3eaVCCPt+OBhzsnGpdn3QPhJVuwW+skX+42mHkPry28qooLxIEfGPFNr9r0chxX5ocWXuIVAcNOpncbKe4Dp9IDjRf0JEU0zAKxjtHXx7oLWEtTwMZwHFmCm8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=B1RMrW9L; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="B1RMrW9L" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1743605889; 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=L8Rz3VpKn+8r1+AXWNItama+JHeQ2kHW+quVQG2dGm0=; b=B1RMrW9Led9/DPF2mA3QJwlvgJT3mBGHwPW73yVX6X+ankT4/SdyuXbEerz05347mbAgP8 d5Ytiu4dQqtlL8LTb/bMlo0SHvGjVg1SApmnrGyq8B2Ix6VMXfGf6LSFN34HYzue2GSOfY ukjtHCM/XmdKwJuHERF9xV7FT5ClBN8= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-454-FeU2dh3sOjGSv9VIlCn7Iw-1; Wed, 02 Apr 2025 10:58:08 -0400 X-MC-Unique: FeU2dh3sOjGSv9VIlCn7Iw-1 X-Mimecast-MFC-AGG-ID: FeU2dh3sOjGSv9VIlCn7Iw_1743605887 Received: by mail-wm1-f69.google.com with SMTP id 5b1f17b1804b1-43d6c65dc52so47192235e9.1 for ; Wed, 02 Apr 2025 07:58:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1743605887; x=1744210687; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=L8Rz3VpKn+8r1+AXWNItama+JHeQ2kHW+quVQG2dGm0=; b=STuueMNaVZUa1GKkfpnhxpRw76n7h3cFbW8OmnuVYZpURW9QH2w24dl7S29oQNJYO5 9HiKAZSzTVUfoeC4UsuKZhBEwBzbRn4M5GRFtzTfU6loIksoUOoO4qP4+T0r/H/zj91i Li3cokwZufZUGheVt5ZH/8XK+Cte3C8RthmWjUxDO1CFAoS8x/nmVtKKyhFDqjNNuyeY QPJiTmesQaTmiexTvAepiSvCcpvyzOSjAEGwrY01K1mTDOKq3MvHOtZfDKC9uuZP8A9v k1h1j8zhqwQ/l2D88L7UEvkWckFa6WX3VrmJWXNq4bQZkvLSmqIbuksWTLrNn39kZ9q5 vjmA== X-Forwarded-Encrypted: i=1; AJvYcCX68N6P565C0vRjATlOohk7toV9MOt47Z6lDQ4HGEwRah50Pk7iZayR9+gBWj1RGDexmduPf6RRVUJI@vger.kernel.org X-Gm-Message-State: AOJu0YwYJgUhcgrzIdgawDXprt8jLJYAiG+zv/Vqu0h+tRauverMGV7p m/XrZXCA++c4VQ00U3GJ/5545KjCQPh86kfr+nRNhabct4S/lkvDo7USt0nucqFbUNoqoTccA25 1Z590e5iiNGtWf5/NwLgEfx/eMQYd239H0yQ0DOwkXdtYks3ZvRTM6aheg9g= X-Gm-Gg: ASbGncvBZBJ/TRAjpyu82hWfdvDsQEY4Ka7KisIwEyLJOrfAjpZakUk/9Cos8gqz34P 7bHaJNKzGA13Ye0sEH9tJ29y56rxNRvaOfSAWr11F9EzLvVmuy/sdL5iuMa/t2afCMYrT4WhsTo lyZM1+vcmrkT1Z4UTU8BiCowDCPzbzXkkVMyBplE3/xDd7PzNwPlvWyW+w1tiQcAjhI3A+9ZB91 j8+WtUIxIn/iSv9Zd5xqEEteggYP7C4TfLyECcx+IYHXa4ri6hiyWuf1dkD99unAXNxIRr7J8oi Pc/CE+XggA== X-Received: by 2002:a05:600c:4f85:b0:43c:e7a7:aea0 with SMTP id 5b1f17b1804b1-43eb5c95ab8mr26516265e9.26.1743605887052; Wed, 02 Apr 2025 07:58:07 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGnt5KDjZ7Xbo5Pys2aWUT0a97kfUfsVi0s1wsDCX5Rl3ZcuRhKVDRKDpLSMyp1j0flnDsOkw== X-Received: by 2002:a05:600c:4f85:b0:43c:e7a7:aea0 with SMTP id 5b1f17b1804b1-43eb5c95ab8mr26515985e9.26.1743605886682; Wed, 02 Apr 2025 07:58:06 -0700 (PDT) Received: from redhat.com ([2a0d:6fc0:1517:1000:ea83:8e5f:3302:3575]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-39c0dcc66a4sm16163450f8f.42.2025.04.02.07.58.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 02 Apr 2025 07:58:06 -0700 (PDT) Date: Wed, 2 Apr 2025 10:58:03 -0400 From: "Michael S. Tsirkin" To: David Woodhouse Cc: virtio-comment@lists.linux.dev, hch@infradead.org, Claire Chang , linux-devicetree , Rob Herring , =?iso-8859-1?Q?J=F6rg?= Roedel , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, graf@amazon.de Subject: Re: [RFC PATCH 3/3] transport-pci: Add SWIOTLB bounce buffer capability Message-ID: <20250402105436-mutt-send-email-mst@kernel.org> References: <20250402112410.2086892-1-dwmw2@infradead.org> <20250402112410.2086892-4-dwmw2@infradead.org> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250402112410.2086892-4-dwmw2@infradead.org> On Wed, Apr 02, 2025 at 12:04:47PM +0100, David Woodhouse wrote: > From: David Woodhouse > > Add a VIRTIO_PCI_CAP_SWIOTLB capability which advertises a SWIOTLB bounce > buffer similar to the existing `restricted-dma-pool` device-tree feature. > > The difference is that this is per-device; each device needs to have its > own. Perhaps we should add a UUID to the capability, and have a way for > a device to not *provide* its own buffer, but just to reference the UUID > of a buffer elsewhere? Such uuid appoach will be really messy with physical devices. Also messy with confidential since config space is not encrypted. Really, if you want something complex like this, just use virtio-iommu. It does not require parsing page tables or anything complex like that. The attraction of the same BAR proposal is that it is, at least, simple. > Signed-off-by: David Woodhouse > --- > transport-pci.tex | 33 +++++++++++++++++++++++++++++++++ > 1 file changed, 33 insertions(+) > > diff --git a/transport-pci.tex b/transport-pci.tex > index a5c6719..23e0d57 100644 > --- a/transport-pci.tex > +++ b/transport-pci.tex > @@ -129,6 +129,7 @@ \subsection{Virtio Structure PCI Capabilities}\label{sec:Virtio Transport Option > \item ISR Status > \item Device-specific configuration (optional) > \item PCI configuration access > +\item SWIOTLB bounce buffer > \end{itemize} > > Each structure can be mapped by a Base Address register (BAR) belonging to > @@ -188,6 +189,8 @@ \subsection{Virtio Structure PCI Capabilities}\label{sec:Virtio Transport Option > #define VIRTIO_PCI_CAP_SHARED_MEMORY_CFG 8 > /* Vendor-specific data */ > #define VIRTIO_PCI_CAP_VENDOR_CFG 9 > +/* Software IOTLB bounce buffer */ > +#define VIRTIO_PCI_CAP_SWIOTLB 10 > \end{lstlisting} > > Any other value is reserved for future use. > @@ -744,6 +747,36 @@ \subsubsection{Vendor data capability}\label{sec:Virtio > The driver MUST qualify the \field{vendor_id} before > interpreting or writing into the Vendor data capability. > > +\subsubsection{Software IOTLB bounce buffer capability}\label{sec:Virtio > +Transport Options / Virtio Over PCI Bus / PCI Device Layout / > +Software IOTLB bounce buffer capability} > + > +The optional Software IOTLB bounce buffer capability allows the > +device to provide a memory region which can be used by the driver > +driver for bounce buffering. This allows a device on the PCI > +transport to operate without DMA access to system memory addresses. > + > +The Software IOTLB region is referenced by the > +VIRTIO_PCI_CAP_SWIOTLB capability. Bus addresses within the referenced > +range are not subject to the requirements of the VIRTIO_F_ORDER_PLATFORM > +capability, if negotiated. > + > +\devicenormative{\paragraph}{Software IOTLB bounce buffer capability}{Virtio > +Transport Options / Virtio Over PCI Bus / PCI Device Layout / > +Software IOTLB bounce buffer capability} > + > +Devices which present the Software IOTLB bounce buffer capability > +SHOULD also offer the VIRTIO_F_SWIOTLB feature. > + > +\drivernormative{\paragraph}{Software IOTLB bounce buffer capability}{Virtio > +Transport Options / Virtio Over PCI Bus / PCI Device Layout / > +Software IOTLB bounce buffer capability} > + > +The driver SHOULD use the offered buffer in preference to passing system > +memory addresses to the device. If the driver accepts the VIRTIO_F_SWIOTLB > +feature, then the driver MUST use the offered buffer and never pass system > +memory addresses to the device. > + > \subsubsection{PCI configuration access capability}\label{sec:Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / PCI configuration access capability} > > The VIRTIO_PCI_CAP_PCI_CFG capability > -- > 2.49.0 >