From nobody Fri Apr 26 03:42:02 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 63.128.21.74 as permitted sender) client-ip=63.128.21.74; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-74.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 63.128.21.74 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1585000622; cv=none; d=zohomail.com; s=zohoarc; b=bLRJ+p7b7npPpBQ+vbVT40GqpfbnaSohwkfiYD9GNREWn7JZQYXPrP/F19hhOcjdk3JiZo49L1e1iVAvZHcqJnjCSTiaZJod3UDCWuI2ESOrqo/2ZPSD3khWc7Gp8FTGtLFGjvxxeRmnL2zXCE6takSp1v4LyQ8+7hWa8DyVCls= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1585000622; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To; bh=ZPNDKEYZPQ2ejQBMZYQOF8iYtabsAoGNnmrt+MY5+5A=; b=Zw03JiND9+mfF8jMmLHSZ0wiWyCUNNoozo5O4QsfZ3mTO78k71NxOkWYHYPoQ68nT/3r33ePPS+qXDEcOgl/2yqXvIHe/2z+Saxecnp8d3u84X4k6yvWKM4ZogFS9MYu0VUiR/Ltx/Sw70yqhK+4bCzCd4dZU9/8/+OEcwMoMtk= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 63.128.21.74 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com Return-Path: Received: from us-smtp-delivery-74.mimecast.com (us-smtp-delivery-74.mimecast.com [63.128.21.74]) by mx.zohomail.com with SMTPS id 158500062251862.49316211446387; Mon, 23 Mar 2020 14:57:02 -0700 (PDT) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-226-L-QGLRpsOz25uGuMl9hjUg-1; Mon, 23 Mar 2020 17:56:58 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 17230DB61; Mon, 23 Mar 2020 21:56:52 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id CF6BC5E1AF; Mon, 23 Mar 2020 21:56:50 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id AE7BB86382; Mon, 23 Mar 2020 21:56:48 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 02NLulIQ017844 for ; Mon, 23 Mar 2020 17:56:47 -0400 Received: by smtp.corp.redhat.com (Postfix) id 3537D10AF413; Mon, 23 Mar 2020 21:56:47 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast06.extmail.prod.ext.rdu2.redhat.com [10.11.55.22]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 30B8B10AF411 for ; Mon, 23 Mar 2020 21:56:45 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D6609185A78F for ; Mon, 23 Mar 2020 21:56:44 +0000 (UTC) Received: from m9a0013g.houston.softwaregrp.com (m9a0013g.houston.softwaregrp.com [15.124.64.91]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-279-P1IfUIWpN7es5ebEjvAJXg-1; Mon, 23 Mar 2020 17:56:42 -0400 Received: FROM m9a0013g.houston.softwaregrp.com (15.121.0.191) BY m9a0013g.houston.softwaregrp.com WITH ESMTP; Mon, 23 Mar 2020 21:55:52 +0000 Received: from M4W0334.microfocus.com (2002:f78:1192::f78:1192) by M9W0068.microfocus.com (2002:f79:bf::f79:bf) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Mon, 23 Mar 2020 21:48:11 +0000 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (15.124.8.14) by M4W0334.microfocus.com (15.120.17.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10 via Frontend Transport; Mon, 23 Mar 2020 21:48:11 +0000 Received: from BY5PR18MB3315.namprd18.prod.outlook.com (2603:10b6:a03:196::12) by BY5PR18MB3156.namprd18.prod.outlook.com (2603:10b6:a03:1ae::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2835.22; Mon, 23 Mar 2020 21:48:10 +0000 Received: from BY5PR18MB3315.namprd18.prod.outlook.com ([fe80::6157:7c41:b13d:23f5]) by BY5PR18MB3315.namprd18.prod.outlook.com ([fe80::6157:7c41:b13d:23f5%3]) with mapi id 15.20.2835.021; Mon, 23 Mar 2020 21:48:10 +0000 Received: from linux-tbji.provo.novell.com (75.169.23.17) by SN6PR16CA0040.namprd16.prod.outlook.com (2603:10b6:805:ca::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2835.15 via Frontend Transport; Mon, 23 Mar 2020 21:48:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1585000621; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=ZPNDKEYZPQ2ejQBMZYQOF8iYtabsAoGNnmrt+MY5+5A=; b=YdgSQY7bJRMxTz1eSwC1P6C95e9ToU2lzZyGvwWaRqe/FBkYmRiMmycP9Ghu5TREwKA9js sj+wHQgUxY2ev+fKLCn+engV1sms0nPe+6QLZbhbN0/nJp2HzdA901Jr9lFo6iMILEBRTA a933coF0qlwUMMqyFQIm8Wh8wvlf+vA= X-MC-Unique: L-QGLRpsOz25uGuMl9hjUg-1 X-MC-Unique: P1IfUIWpN7es5ebEjvAJXg-1 From: Jim Fehlig To: Subject: [PATCH] docs: fix typo in domcaps host-model CPU description Date: Mon, 23 Mar 2020 15:47:49 -0600 Message-ID: <20200323214749.24185-1-jfehlig@suse.com> X-ClientProxiedBy: SN6PR16CA0040.namprd16.prod.outlook.com (2603:10b6:805:ca::17) To BY5PR18MB3315.namprd18.prod.outlook.com (2603:10b6:a03:196::12) MIME-Version: 1.0 X-MS-Exchange-MessageSentRepresentingType: 1 X-Originating-IP: [75.169.23.17] X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 207245c8-2829-485e-00db-08d7cf73e0dc X-MS-TrafficTypeDiagnostic: BY5PR18MB3156: X-MS-Exchange-Transport-Forked: True X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:9508; X-Forefront-PRVS: 0351D213B3 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(39860400002)(376002)(136003)(366004)(396003)(6666004)(956004)(1076003)(66946007)(36756003)(66476007)(66556008)(5660300002)(478600001)(81156014)(8676002)(8936002)(81166006)(86362001)(6506007)(107886003)(4326008)(2616005)(2906002)(450100002)(16526019)(186003)(6512007)(316002)(52116002)(6916009)(6486002)(26005); DIR:OUT; SFP:1102; SCL:1; SRVR:BY5PR18MB3156; H:BY5PR18MB3315.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: HUhhJJu64H5DgNZMin4g5xbJuVD5AmILc5Hq34AJzxEPhtx4A2/wm2u4U/PizHVk52GkFeKV2vapHq1N9JhZ3n4SH+/lyiLdXN8hbi6uJOxMRYepi6cCY4qQMymhXrLrZpMDbix4xU0/QHfB9EBHEnPVwvW7Bs7P/ZyEKVSUh5ES1Fy59NuzmyplD8ySpmptyJpEojYkBJMZ3IT4KxIQyDuvb23dWHX0lPzqqbnV956r5NkVqv9nY5Ft6BnJTN2OI332yoscur6ye/58bV31EisRfwDl4sgz12noAU26ZATAjvHWuRhScW+4Tt9We+4TfTG9sDngVIkMjlFeZzYZwgroMNOXj0nV8fT2j13f3QvahWk/epnsxwEGuKEJlG4nEgw3mzWtOMXVGWRVj77e1VX1RAha8zJdzFXeOu6lakJpe/cJRZoJBjGbBWeMZMDY X-MS-Exchange-AntiSpam-MessageData: b9R7aq0GwFcc3UXb7j3jgolLo3Heza7OoA1REFrhRDfntX391Awh7LToE3HRMvTz55kyAyIjtoM9DCb9kMnTzhTlIUAthqbssgVLFfS55zipufCzFOzrjcvqgagQ7gWPOEZJ7EwBkt7/RaE+HhA1fg== X-MS-Exchange-CrossTenant-Network-Message-Id: 207245c8-2829-485e-00db-08d7cf73e0dc X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Mar 2020 21:48:10.0865 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: 856b813c-16e5-49a5-85ec-6f081e13b527 X-MS-Exchange-CrossTenant-MailboxType: HOSTED X-MS-Exchange-CrossTenant-UserPrincipalName: kxsL/8CJH7vOQoQaH27yap7bkxf1Tf+0c05zoIVJE0g4ss+fRDvlQz72LOax2mfSaAWv81LDMdb8ORLcyjOvAQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR18MB3156 X-OriginatorOrg: suse.com X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3 X-MIME-Autoconverted: from quoted-printable to 8bit by lists01.pubmisc.prod.ext.phx2.redhat.com id 02NLulIQ017844 X-loop: libvir-list@redhat.com Cc: jdenemar@redhat.com X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) Content-Type: text/plain; charset="utf-8" The domain capabilities documentation contains a small but confusing error in the host-model CPU description, referencing the element instead of . Fix this small typo. Signed-off-by: Jim Fehlig --- I only found this small typo (well, I'm pretty sure it's a typo :-)) by tring to understand a more confusing observation. On a machine where capabilities reports CascaseLake-Server, domcapabilities reports Cascadelake-Server Intel ... Cascadelake-Server So using host-model will result in a CascadeLake-Server CPU, but it is not supported when specifying a custom CPU? Interestingly, I see something similar from domcapabilities on machine where capabilities reports Skylake-Server-IBRS Cascadelake-Server Intel ... Skylake-Server-IBRS Skylake-Server Cascadelake-Server This seems contradictory to me but perhaps I'm overlooking something? docs/formatdomaincaps.html.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/formatdomaincaps.html.in b/docs/formatdomaincaps.html.in index 66e758501b..7fd1f91f73 100644 --- a/docs/formatdomaincaps.html.in +++ b/docs/formatdomaincaps.html.in @@ -232,7 +232,7 @@
host-model
If host-model is supported by the hypervisor, the - mode describes the guest CPU which will be used when + model describes the guest CPU which will be used when starting a domain with host-model CPU. The hypervisor specifics (such as unsupported CPU models or features, machine typ= e, etc.) may be accounted for in this guest CPU specification and thus --=20 2.25.0