public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail 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: Fri, 25 Aug 2023 16:20:51 +0000 [thread overview] Message-ID: <bug-30643-131-mtzlBa13hD@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30643-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30643 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |hjl.tools at gmail dot com --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> --- Created attachment 15087 --> https://sourceware.org/bugzilla/attachment.cgi?id=15087&action=edit A patch Florian, can you try this? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-25 16:20 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 [this message] 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 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-mtzlBa13hD@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).