[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 5/5] xenperf: name "newer" hypercalls
- To: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: Jan Beulich <jbeulich@xxxxxxxx>
- Date: Fri, 3 Dec 2021 13:07:22 +0100
- 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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ms0YHIDv5FBReZC9ySpmTf7afFn9dSpJLL3t23RnwNE=; b=DqxKR/X9lIIscjP9rs+vxRIKTipCqogWbuns3njs/koiS5wyqoUSzQm0L6v7M1VGwQPNOg96yJ6N2KT0wFOT8BFE4tG9/FvZUsHo+1QW/hb30fulx0pMuBIIWM8JQu06sGAHRLW07+RoHg9GL+ll3PFuQ2F2eHH4RYpX35iJ/Ma/mV1LLi3kJuACCDFZYau5qlJrsgkb4R5hmaSemEOFzer1ghb20erdYPOyIz4wU8I0/S0bXLlfNqdPTE4NfgLF5RJfvIHowIDe/iX7iw3R2/rBHhu2qBqxf023cYj30wCUte86SCDSzlUYbQZwqS1uk6WdxMjSXhESKVm1//zXfQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cR2ezW4bj9BBvDk1dLj+Iwniy+DMTauA4SLL+43kZXbVAB5OJo1vudK3a70zRykmztKTGr4AmmUosby1Fb3sw9Pdr2pyBi+T3n8BEtxRm9I+LJJrcZ+jJEdHG5BCJ6lipZAlQiYemaVVa7V7r4VXY/6tfRCEJj/+1vKPn0/j8q1hozVLTsTcaZsezi4/tSqZwkMSrwbZMQozdLiZJzIZbvgreUCr5aHAPUlKn6P5i8oa2AO0XQ/svq34YvFrjPeAMJzKKMh0LpiDjrgPQ0W/g/kIdRQRUy3cT5tLTRq6W6yHdeiTZEd57m9zeQzVMk5rqZfC/taksC5DLLBU6fHyHg==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
- Cc: George Dunlap <george.dunlap@xxxxxxxxxx>, Ian Jackson <iwj@xxxxxxxxxxxxxx>, Wei Liu <wl@xxxxxxx>
- Delivery-date: Fri, 03 Dec 2021 12:07:29 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
This table must not have got updated in quite a while; tmem_op for
example has managed to not only appear since then, but also disappear
again (adding a name for it nevertheless, to make more obvious that
something strange is going on if the slot would ever have a non-zero
value).
Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
---
I wasn't really sure about x86's real names for arch_0 and arch_1. The
tool runs on the same host as the hypervisor, so __i386__ / __x86_64__
conditionals wouldn't be inappropriate to use ...
--- a/tools/misc/xenperf.c
+++ b/tools/misc/xenperf.c
@@ -18,7 +18,7 @@
#include <string.h>
#define X(name) [__HYPERVISOR_##name] = #name
-const char *hypercall_name_table[64] =
+static const char *const hypercall_name_table[64] =
{
X(set_trap_table),
X(mmu_update),
@@ -57,6 +57,11 @@ const char *hypercall_name_table[64] =
X(sysctl),
X(domctl),
X(kexec_op),
+ X(tmem_op),
+ X(argo_op),
+ X(xenpmu_op),
+ X(dm_op),
+ X(hypfs_op),
X(arch_0),
X(arch_1),
X(arch_2),
|
