public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "decui at microsoft dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/30643] Missing cache information on x86-64 under Intel TDX Date: Mon, 28 Aug 2023 18:24:57 +0000 [thread overview] Message-ID: <bug-30643-131-E2xhHL4qPR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30643-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30643 --- Comment #6 from Dexuan Cui <decui at microsoft dot com> --- My TDX blade is running a Hyper-V dev build (July 26), which should be similar to the version on Azure. My Ubuntu 20.04 VM has glibc 2.31-0ubuntu9.9. I'm running this kernel [1] in the VM: the kernel here means v6.5-rc4 + the patches in the Hyper-V tree's next branch [2] + a few other patches. The patches should not affect the values returned from CPUID) Hyper-V provides two modes for running Intel TDX VMs [3]: Mode A) TD Partitioning mode with a paravisor. Mode B) In "fully enlightened" mode with normal TDX shared bit control over page encryption, and no paravisor. This is the output for Mode A: # ./getconf-static -a | grep CACHE LEVEL1_ICACHE_SIZE 32768 LEVEL1_ICACHE_ASSOC LEVEL1_ICACHE_LINESIZE 64 LEVEL1_DCACHE_SIZE 49152 LEVEL1_DCACHE_ASSOC 12 LEVEL1_DCACHE_LINESIZE 64 LEVEL2_CACHE_SIZE 2097152 LEVEL2_CACHE_ASSOC 16 LEVEL2_CACHE_LINESIZE 64 LEVEL3_CACHE_SIZE 110100480 LEVEL3_CACHE_ASSOC 15 LEVEL3_CACHE_LINESIZE 64 LEVEL4_CACHE_SIZE LEVEL4_CACHE_ASSOC LEVEL4_CACHE_LINESIZE This is the output for Mode B: # ./getconf-static -a | grep CACHE LEVEL1_ICACHE_SIZE 32768 LEVEL1_ICACHE_ASSOC LEVEL1_ICACHE_LINESIZE 64 LEVEL1_DCACHE_SIZE 49152 LEVEL1_DCACHE_ASSOC 12 LEVEL1_DCACHE_LINESIZE 64 LEVEL2_CACHE_SIZE 2097152 LEVEL2_CACHE_ASSOC 16 LEVEL2_CACHE_LINESIZE 64 LEVEL3_CACHE_SIZE LEVEL3_CACHE_ASSOC LEVEL3_CACHE_LINESIZE LEVEL4_CACHE_SIZE LEVEL4_CACHE_ASSOC LEVEL4_CACHE_LINESIZE [1] https://github.com/dcui/linux/commits/decui/upstream-hyperv/hyperv-next/TDX/0824-with-and-without-HCL [2] https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/log/?h=hyperv-next [3]https://lwn.net/ml/linux-kernel/20230824080712.30327-1-decui@microsoft.com/ -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-28 18:24 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-17 7:29 [Bug libc/30643] New: " fweimer at redhat dot com 2023-07-17 8:46 ` [Bug libc/30643] " fweimer at redhat dot com 2023-07-17 13:49 ` decui at microsoft dot com 2023-07-18 8:41 ` fweimer at redhat dot com 2023-07-18 8:42 ` fweimer at redhat dot com 2023-07-20 22:33 ` hjl.tools at gmail dot com 2023-08-25 16:20 ` hjl.tools at gmail dot com 2023-08-28 5:20 ` fweimer at redhat dot com 2023-08-28 17:05 ` decui at microsoft dot com 2023-08-28 17:46 ` hjl.tools at gmail dot com 2023-08-28 18:24 ` decui at microsoft dot com [this message] 2023-08-28 18:29 ` decui at microsoft dot com 2023-08-28 18:33 ` fweimer at redhat dot com 2023-08-28 18:48 ` decui at microsoft dot com 2023-08-28 19:00 ` fweimer at redhat dot com 2023-08-28 19:04 ` hjl.tools at gmail dot com 2023-08-29 19:58 ` cvs-commit at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30643-131-E2xhHL4qPR@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).