public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jkratochvil@azul.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: Florian Weimer <fweimer@redhat.com>,
	libc-alpha@sourceware.org, Anton Kozlov <akozlov@azul.com>,
	Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: Re: [PATCH] RFC: Provide a function to reset IFUNC PLTs
Date: Wed, 29 Mar 2023 20:12:01 +0800	[thread overview]
Message-ID: <ZCQrEWdZoUzApcJL@host1.jankratochvil.net> (raw)
In-Reply-To: <a37d306c-1fb2-0214-df42-c7179ebe590f@linaro.org>

On Tue, 21 Mar 2023 00:47:53 +0800, Adhemerval Zanella Netto wrote:
> if I
> understood it correctly when criu restores a dump it will only restore private
> mappings from the process and not shared ones?  If so, how does it handle
> restoring on a system on an older glibc (or on a system with any dependency
> older than the one that the process was dumped)? Does it only restore file
> backed shared mappings based on naming?

Different OS (components) version is not supported, similar to:
	https://cr.openjdk.org/~heidinga/crac/Portability_of_checkpoints.pdf
	2. Same hardware, different distro


> Using a custom built glibc with --disable-multi-arch along with rpath, you
> have a dissociated glibc from the system.  You can even tune to use an
> specific x86_64-vX abi if you see that the workload benefits from some
> specific string/mem/math routine.

Then I need to build also all other used libraries and that is what is called
nowadays a container. Which is a perfectly valid use case. But building
a custom distribution (=glibc) is not a supported way of running any software.
[This is my personal opinion, I do not speak for any company.]


Thanks for your review,
Jan

  reply	other threads:[~2023-03-29 12:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06  8:04 Jan Kratochvil
2023-03-07  8:40 ` Florian Weimer
2023-03-07 13:07   ` Adhemerval Zanella Netto
2023-03-08 10:21     ` Jan Kratochvil
2023-03-08 13:04       ` Adhemerval Zanella Netto
2023-03-09 11:32         ` Jan Kratochvil
2023-03-09 15:47           ` Adhemerval Zanella Netto
2023-03-09 17:43             ` Adhemerval Zanella Netto
2023-03-16 14:38             ` Jan Kratochvil
2023-03-20 16:47               ` Adhemerval Zanella Netto
2023-03-29 12:12                 ` Jan Kratochvil [this message]
2023-03-29 13:14                   ` Adhemerval Zanella Netto
2023-03-13 13:59           ` Florian Weimer
2023-03-14 12:55             ` Jan Kratochvil
2023-03-14 14:49               ` Florian Weimer
2023-03-14 15:06                 ` Jan Kratochvil
2023-03-08 10:23   ` Jan Kratochvil
2023-03-08 10:44     ` Florian Weimer
2023-03-08 11:03       ` Jan Kratochvil

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=ZCQrEWdZoUzApcJL@host1.jankratochvil.net \
    --to=jkratochvil@azul.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=akozlov@azul.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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).