[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] xen/vpci: zero guest-visible BAR addresses to ensure domU asssigns its own


  • To: Jan Beulich <jbeulich@xxxxxxxx>, Ariadne Conill <ariadne@ariadne.space>
  • From: Stewart Hildebrand <stewart.hildebrand@xxxxxxx>
  • Date: Wed, 25 Feb 2026 21:50:27 -0500
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=suse.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none (0)
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=EOhfFcZ1Kl2mwEYxFjm/DvBdB6OvJHKuNoWGZ+Z69lc=; b=gjqpRP8GGH+ojsnpE6xDeAKgbI80Q6qDsccaT/q3E0RfJ1mXlHqcpVh8z6BzVdvCzuahFwiX0VtrVdAyHDW25xmbx/hTXD5fX0lAj4Q1HVrir5HcpOfU0nhRtUuLHjDay+6PY5AXKHaEHIsbcIVCz3DX5RQXyWU1f3SSRqBhOGThq416Byp8qRt4IrAMsuQIn04xM2nzS9Cj1PkwXPbFYYo6hDMjXb5SZaKL0fpyCLjHvOVsRhBA9c+Q6AvafbXbM2+3QtvWrswXJ43yJwS7zrWquD9B85cCpn9aexAKQtiqSZAJiXXCbW0uH8I9FplXaEsU/f6HvZpF8rSl/tAHuw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=Uf0VQq8lsgUdD8RvNZfGg9rG0xt7uVKZVsX0XBdhLGEcpuaE1qnp7kzJPHadlVruK0RIZ+9tdCPjshW1RJuFwO6V0lwZm+nij/N2o38ItprS/Eb4CPOUPKfwpgMMhsjHi7sjtbGZZucEDKa3yNAHYtZb1dSfP0159QBXcV1UtWtbBGtkOdXH1KtqFEO1LKWBX08PkJN5OPy3H4xueNR71SJjMkdn53eU0ub64/H9/zlz6LSfMgOJQqC9pdRL5YePVWdIhDhuBUBELg9DyCkUQnSLjhmpHUGAt2cQGgslCSDwo9MOphL2xiGQa0RgK/38pd5dSyMKNpLuKZuphxYIcw==
  • Cc: Roger Pau Monné <roger.pau@xxxxxxxxxx>, Steven Noonan <steven@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 26 Feb 2026 02:50:48 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 2/25/26 10:37, Jan Beulich wrote:
> On 25.02.2026 00:12, Ariadne Conill wrote:
>> From: Steven Noonan <steven@xxxxxxxxx>
>>
>> If we just use the host's BAR addresses, the domU might not attempt to
>> reconfigure the BAR ranges and may never try to map them with the IOMMU.
>> Zeroing them ensures the guest kernel knows the BARs are not configured
>> and needs to make its own choices about where to map the BARs.
> 
> Yet for this, don't we first need to expose a full topology to the guest,
> i.e. at least a host bridge, and maybe further bridges?
While we eventually do want to expose (a) virtual bridge(s) to vPCI domUs (this
work is currently in development), I don't think it's pre-requisite for the code
change herein: clearly, leaking host BAR addresses to domUs isn't right, and
there's no need to wait to address that.

With that said, the commit title/description don't align well with the code
change. Assuming we want to move the code change forward, for v2 of the patch I
suggest dropping the 2nd half of the title, and reworking the commit description
to focus on describing the code change at hand and less on what the domU might
do.



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.