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

Re: About support for memory event on AMD CPUs


  • To: Jan Beulich <jbeulich@xxxxxxxx>
  • From: Untitled YAN <yanluyi2010@xxxxxxxxxxx>
  • Date: Wed, 24 Nov 2021 09:23:09 +0000
  • Accept-language: en-US, zh-CN
  • 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=uf2tDABW1rdquG0aLJXpTc7bgtZyPWkuOIxWkxUro+o=; b=ORb/9qE5ToeZ7xY7NPPXjZQOqXSav2GnSnNOMtOm3GPlxzkfPYGHg+H1EKIDgNv7ZXA9VYvwk/zRcAEuZn209+JgtbSJBNdO72dpfkl+I50ptpsR8U6ynVUUOiWb2XTB1tvaiV+paMJnIIWsEq8hJWdMLhFy5w/HNT2T+eZDvbss1Wt+foJBDDmbIQVsMRFkU1Kw/mmt6iSYvL6KxMoxnU7nQda7la9JM3cnNGLJriQCYch+J81AAugDIbjKz98jL55W3gz297ugsKI34oCS61JZV3HNwQwmi168SEXDWOf+omNuK5DisGWyUkfWC1S9pta6y1n0mD/A5wMlCLruoA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QxcrPwFddSuJqrIPvEOaZt/E/PVMenhlzjhANFmpDKgZTM34svKU5kLXKfCpVaZFL5/O2NOAHUxfUpNTBdwy2pFlKGGYF/75uQ8cZ8S+nLXhE8BPs+usSJXOSdVOU+5NN1E6RIfEajlRwGmI4LqLj1pmi4mrH9cgw6O0hcCKtR8fciJrPT8O2j1zUFnxZG1MKPLQ3AcwlydhYaj3Iy5stF3YSmBmzTA0XceEUO8BxngGQUtNgxppHaRQIibYbnma+fYV4HtJzGxKSynAEuZBLOIJ3MERmoDaASYwTgpkL5ECRS9npgZ0bmKDl/H4ANZNL3VVtZYnDfwTx5FUxcr+bw==
  • Cc: "tamas@xxxxxxxxxxxxx" <tamas@xxxxxxxxxxxxx>, "aisaila@xxxxxxxxxxxxxxx" <aisaila@xxxxxxxxxxxxxxx>, "ppircalabu@xxxxxxxxxxxxxxx" <ppircalabu@xxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 24 Nov 2021 09:23:23 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Suggested_attachment_session_id: 385db734-82bf-2611-7953-fd7021148395
  • Thread-index: AQHX4Ivyto+Oc0SSQ0aRZryw/8JAG6wST82AgAAO3bA=
  • Thread-topic: About support for memory event on AMD CPUs

Original email:

From: Jan Beulich <jbeulich@xxxxxxxx>
Sent: Wednesday, November 24, 2021 15:54
To: YAN Untitled <yanluyi2010@xxxxxxxxxxx>
Cc: tamas@xxxxxxxxxxxxx <tamas@xxxxxxxxxxxxx>; aisaila@xxxxxxxxxxxxxxx 
<aisaila@xxxxxxxxxxxxxxx>; ppircalabu@xxxxxxxxxxxxxxx 
<ppircalabu@xxxxxxxxxxxxxxx>; xen-devel@xxxxxxxxxxxxxxxxxxxx 
<xen-devel@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: About support for memory event on AMD CPUs 
 
> On 23.11.2021 18:14, YAN Untitled wrote:
> > Dear developers,
> > 
> > Short version: is memory event supported on AMD CPUs or is it going to be
> > supported?
> > 
> > Long version:
> > 
> > Environment: LibVMI 0.15.0 + Xen 4.14.3 on an **AMD CPU** (5950x), 64-bit
> > Debian 11 Dom0.
> > 
> > What I am trying to accomplish: register a **memory event** handler, so that
> > I can capture all memory accesses within a specific range issued by any 
> > thread,
> > or all memory accesses within any range issued by a specific thread.
> > 
> > What I got instead: an error from LibVMI saying
> > "xc_hvm_set_mem_access failed with code: -1".
> > 
> > Some investigation: by inspecting the source code of LibVMI, I find the 
> > direct
> > cause is one of the libxc functions, 1) xc_set_mem_access or
> > 2) 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.
> 
> Aiui underlying what you want is altp2m, which presently depends (in
> the hypervisor) on EPT being available (and in use for the guest in
> question).
> 
> Jan

Dear Jan,

Thanks for your reply. I really appreciate the information. After some
searching with the keyword "EPT" I found [1]. So I checked on dom0 with
"xl dmesg | grep HAP", which says:

> (XEN) HVM: Hardware Assisted Paging (HAP) detected
> (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB

And the guest is an HVM guest running Debian 10 with kernel v4.16 built from
source. Most of the configuration of the guest is generated by virt-manager.
The "xl list -l" shows that there is no explicit configuration for EPT, RVI or
HAP, but it does say the "type" is "hvm". So I am still quite confusing:

1. Is memory event feature for AMD's RVI is even implemented?
2. If memory event should be working on AMD CPUs with RVI enabled, am I missing
   any essential step to make it work?

[1] https://groups.google.com/g/vmitools/c/JRN11E64BNY


Untitled YAN



 


Rackspace

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