From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id A2E7A1FF15C for ; Fri, 5 Sep 2025 14:00:31 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 028B113B3E; Fri, 5 Sep 2025 14:00:47 +0200 (CEST) Message-ID: <95c34f0a-0256-4f9f-8657-6077293fa923@proxmox.com> Date: Fri, 5 Sep 2025 14:00:13 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Daniel Kral , Proxmox VE development discussion References: <20250902112307.124706-1-d.kral@proxmox.com> <20250902112307.124706-3-d.kral@proxmox.com> <1d1b02b3-6932-4550-ae3d-76f24d04cb94@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1757073595785 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.023 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [gitlab.com] Subject: Re: [pve-devel] [PATCH qemu-server v2 1/4] fix #6608: expose viommu driver aw-bits option X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Am 05.09.25 um 1:45 PM schrieb Daniel Kral: > On Fri Sep 5, 2025 at 12:07 PM CEST, Fiona Ebner wrote: >> Am 02.09.25 um 1:23 PM schrieb Daniel Kral: >>> Therefore, expose the 'aw-bits' option of the intel-iommu and >>> virtio-iommu QEMU drivers to allow users to set the value. >>> >>> [0] https://lore.kernel.org/qemu-devel/20241212083757.605022-17-zhenzhong.duan@intel.com/ >>> [1] https://lore.kernel.org/qemu-devel/20240605083043.317831-18-zhenzhong.duan@intel.com/ >>> >> >> Nit: I'd prefer references to qemu commits rather than mails > > ACK, but not sure in what format we reference external repos, to the > qemu-project gitlab or just the repo + commit hash + summary? > > So > > [0] https://gitlab.com/qemu-project/qemu/-/commit/ddd84fd0c1 > [1] https://gitlab.com/qemu-project/qemu/-/commit/77f6efc0ab > > or > > [0] qemu ddd84fd0c1 ("intel_iommu: Set default aw_bits to 48 starting from QEMU 9.2") > [1] qemu 77f6efc0ab ("intel_iommu: Check compatibility with host IOMMU capabilities") I much prefer this as one can also see the commit title and as web locations of repos are not stable long-term. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel