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 dynamic-link/27201] Consider disabling x86-64-v2 support check Date: Mon, 18 Jan 2021 20:47:43 +0000 [thread overview] Message-ID: <bug-27201-131-jtag9thwWf@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27201-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27201 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> --- I tested KVM on Fedora 33/Westmere. /proc/cpuinfo looks OK: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Westmere E56xx/L56xx/X56xx (IBRS update) stepping : 1 microcode : 0x1 cpu MHz : 3333.292 cache size : 16384 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx pdpe1gb rdtscp lm constant_tsc re p_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq vmx ssse3 cx16 pcid sse 4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes hypervisor lahf_lm cpuid_fault p ti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid tsc_adjust arat um ip arch_capabilities tst-isa-level-1.c works fine: Breakpoint 1, do_test () at ../sysdeps/x86/tst-isa-level-1.c:63 63 const struct cpu_features *cpu_features (gdb) next 65 unsigned int isa_level = get_isa_level (cpu_features); (gdb) 81 do_test_1 ("tst-isa-level-mod-1-baseline.so", false); (gdb) 87 do_test_1 ("tst-isa-level-mod-1-v4.so", true); (gdb) 93 do_test_1 ("tst-isa-level-mod-1-v3.so", true); (gdb) 96 if (has_isa_v2) (gdb) 78 return EXIT_SUCCESS; (gdb) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-18 20:47 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-18 14:23 [Bug dynamic-link/27201] New: " fweimer at redhat dot com 2021-01-18 15:35 ` [Bug dynamic-link/27201] " hjl.tools at gmail dot com 2021-01-18 20:47 ` hjl.tools at gmail dot com [this message] 2021-01-18 20:51 ` fweimer at redhat dot com 2021-01-18 20:58 ` hjl.tools at gmail dot com 2021-01-18 21:06 ` hjl.tools at gmail dot com 2021-01-18 21:10 ` hjl.tools at gmail dot com 2021-01-18 21:20 ` fweimer at redhat dot com 2021-01-18 21:33 ` hjl.tools at gmail dot com 2021-01-18 23:51 ` hjl.tools at gmail dot com 2021-01-19 11:09 ` fweimer at redhat dot com 2021-01-19 12:34 ` hjl.tools at gmail dot com 2021-01-19 16:56 ` hjl.tools at gmail dot com 2021-01-21 12:45 ` berrange at redhat dot com 2021-01-21 13:00 ` hjl.tools at gmail dot com 2021-01-21 13:58 ` berrange at redhat dot com 2021-01-21 15:12 ` hjl.tools at gmail dot com 2021-01-21 15:17 ` fweimer at redhat dot com 2021-01-21 15:27 ` hjl.tools at gmail dot com 2021-01-21 15:28 ` hjl.tools at gmail dot com 2021-01-21 15:41 ` fweimer at redhat dot com 2021-01-21 15:56 ` hjl.tools at gmail dot com 2021-01-21 23:34 ` hjl.tools at gmail dot com 2021-01-22 9:44 ` berrange at redhat dot com 2021-01-22 9:59 ` fweimer at redhat dot com 2021-01-22 10:13 ` berrange at redhat dot com 2021-01-22 10:19 ` fweimer at redhat dot com 2021-01-28 17:46 ` fweimer at redhat dot com
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-27201-131-jtag9thwWf@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).