From: DJ Delorie <dj@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: tunables vs osxsave vs checkpointing vs _dl_runtime_resolve
Date: Fri, 19 Mar 2021 00:35:18 -0400 [thread overview]
Message-ID: <xnft0rn4l5.fsf@rhel8.vm> (raw)
In-Reply-To: <CAMe9rOoNBoWHoYnkyQgQVOF0oSHTBE08xT5gT30Fhaq7BF5YSA@mail.gmail.com> (hjl.tools@gmail.com)
"H.J. Lu" <hjl.tools@gmail.com> writes:
> Try this.
close... fixed osxsave, broke xsavec
(gdb) set env GLIBC_TUNABLES=glibc.cpu.hwcaps=-OSXSAVE
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: ... /home/dj/criu-test --direct
Breakpoint 4, _dl_runtime_resolve_fxsave () at ../sysdeps/x86_64/dl-trampoline.h:72
72 pushq %rbx # push subtracts stack by 8.
(gdb) set env GLIBC_TUNABLES=glibc.cpu.hwcaps=-XSAVE
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: ... /home/dj/criu-test --direct
Breakpoint 3, _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:72
72 pushq %rbx # push subtracts stack by 8.
(gdb) set env GLIBC_TUNABLES=glibc.cpu.hwcaps=-XSAVEC
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: ... /home/dj/criu-test --direct
Breakpoint 3, _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:72
72 pushq %rbx # push subtracts stack by 8.
(gdb)
next prev parent reply other threads:[~2021-03-19 4:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 17:18 DJ Delorie
2021-03-18 17:29 ` H.J. Lu
2021-03-18 17:45 ` DJ Delorie
2021-03-18 20:39 ` H.J. Lu
2021-03-19 3:40 ` DJ Delorie
2021-03-19 4:16 ` H.J. Lu
2021-03-19 4:35 ` DJ Delorie [this message]
2021-03-18 17:32 ` Florian Weimer
2021-03-18 17:47 ` DJ Delorie
2021-03-18 17:57 ` Florian Weimer
2021-03-18 18:19 ` DJ Delorie
2021-03-19 16:43 ` Szabolcs Nagy
2021-03-19 21:12 ` DJ Delorie
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=xnft0rn4l5.fsf@rhel8.vm \
--to=dj@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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: link
Be 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).