[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v7] AMD/IOMMU: further work split from XSA-378
- To: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: Jan Beulich <jbeulich@xxxxxxxx>
- Date: Thu, 26 Aug 2021 09:21:36 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GoVpa6yo1+kqij+kyNC8NWRYKew0xeVGaGvImNjjnKY=; b=l/kWjkCrHY15W6IrAYBF86uxYdsEq0X7yWTEH9fn3GcBF4WdxsrIq8Kb61wTosj+jUBQR5cEBcaQIZfY/7XnDzwgomAExfgWa/ooBgUaKL/rb4YEBhBGrw9sWusmwp8lBijrzBXIp/nVgw6buO5k8VYAerrYi5zNrQbpnVtA8DIlUbg68m/T2PH75rrwsTC3eBcyg3JTQnA46qI1qwqUj2utHs4kzFvZy34vWqEFtSheR+RtIFx55JMhEH5nG/ESH3FAPVtJ/e3L53+MYn13LhO9PtxgZH4VDlpAn1pw4IH234TaSsoOb6j0JMSemZyOWFX2zTcvDE126wEhyWFF7A==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ENzH9yS6PesDTLC3Lx+4FUNqNKR/p5rmFgDoTXvqRrm1d64rhoZ7aJ9u+C3lCri8qb1VnrFSKTa2iEqPhJ6pVqJslRdroDVD7iE7VJ3ATAxkX7G1nEFJi/tbAvylVuirAHY6JnsB4BgfSTjKEwyMIPVhOM2jbQM6opEOjONzwqYkLffredxTOFEd+qguOOA2g9IvCr0T8QBwFMbtreggHzyVz+34a7fl0Af6DGKTULz1Mp9ydiyLnHO4kWjZ5ucx0gPZMa5w8KZ/c9ZMzLov1j7eXDFGBs/UtUFlYe4xgveqyrNGzjBHL6tTFJrtf/ZXNhd2cCgTxJ6h8sbz9eiiKA==
- Authentication-results: xen.org; dkim=none (message not signed) header.d=none;xen.org; dmarc=none action=none header.from=suse.com;
- Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Paul Durrant <paul@xxxxxxx>
- Delivery-date: Thu, 26 Aug 2021 07:21:51 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
Along the pieces that were determined to have security relevance
there are quite a few more fixes / improvements (or so I hope)
which were decided to not become part of the XSA itself. Hence
also why this is v7 and why several of them already have a
Reviewed-by tag. Here we go.
1: check / convert IVMD ranges for being / to be reserved
2: obtain IVHD type to use earlier
3: improve (extended) feature detection
4: check IVMD ranges against host implementation limits
5: also insert IVMD ranges into Dom0's page tables
6: provide function backing XENMEM_reserved_device_memory_map
7: add "ivmd=" command line option
8: respect AtsDisabled device flag
Jan
|
