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

Does memory event support AMD CPUs now?


  • To: "xen-users@xxxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxxx>
  • From: YAN Untitled <yanluyi2010@xxxxxxxxxxx>
  • Date: Tue, 23 Nov 2021 16:42:25 +0000
  • Accept-language: zh-CN, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; 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=eSPbEhQK+9Xj33u77w07TpQGlJPye3R/DgNg6SrashA=; b=Z7a7bq++NgspYPn3vS6itj8eGFRAi8qRzDuQzN9/dHv47KqAzHqpq8i3D5n7R+sItA6MbPhG+sjbM3Ov1HoW7daBiLclh5afqvRS2er7liI31R0O/FRDX1kG5uwhcYEf19smAnmmzDj7w1yOkef327HxcM3xW520Yri7ssfhU8PWWKkGfdxQbpugcSBK6ja87++Ybs6Juxbyj4RlJkM8/U1ihNVJbAaUy9toR/BNRWCqaTdz+ineZYtgzi82W+P9AG8ZS2PNx7OJOH5T9mZEpQLoIfAztnXdVEfnw1woLX218aaaCLBpuI9QtF3ePTEb62fY8NJbEEhnSdwNA3R+fQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Xv8hepK9HiIJpXHUmM8PyLuGueE8WMl3UJMyXCfDrZIlIsxh9DG7R2ibNic2q5rWsxZs7Cp1KPMlbBKndus+CRqY/Gkzujw1MSqGlLjPXTz1vP83B3o8Qlu7T+sJ8+yf558ipZWNDmWs+4cq7lqmLLcpOOsqcDWH0Dz3YIWZrxRYSEStDwRCyknQL+WhJdbX3MSVH3L9YHMvjZqH+3tEmyQic1ArisjZE0XNYm7GDrSYkmkqlHFBar6a9koPn2RW4sUNl7Fd6zrd2yTkBMGxCMJcotai4u41w9wOK49qe0wFG6lHtWzF+jHTCZWoRFPp/8nrHUAOwto0OIPXdoOFqQ==
  • Delivery-date: Tue, 23 Nov 2021 19:53:35 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>
  • Suggested_attachment_session_id: 085c4425-8082-2e60-92e6-3712c4914660
  • Thread-index: AQHX4IjxEFtFn9EMQUy1pwyZOZ9+Dg==
  • Thread-topic: Does memory event support AMD CPUs now?

Hi,

I am running LibVMI 0.15.0 + Xen 4.14.3 on an **AMD CPU**. When I was trying to
register a **memory event** handler, I got the error from LibVMI
"xc_hvm_set_mem_access failed with code: -1". By inspecting the source code of
LibVMI, I find the direct cause is one of the libxc functions,
xc_set_mem_access or xc_altp2m_set_mem_access, returned error code -1.

After some searching, I found someone else having a similar problem [1]. I also
noted LibVMI says:

> Currently only the Xen Hypervisor provides these features,
> and some of these are specifically only available on Intel CPUs

However, I can't find the exact confirmation for the availability of memory
event on AMD CPUs from https://wiki.xenproject.org.

Could someone please confirm this? And if it is not available on AMD CPU, it is
to be implemented in the future?

[1] https://github.com/libvmi/libvmi/pull/709#discussion_r353729777


Untitled YAN

 


Rackspace

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