From: Richard Henderson <richard.henderson@linaro.org>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
pbonzini@redhat.com, philmd@linaro.org, laurent@vivier.eu,
deller@gmx.de, qemu-devel@nongnu.org
Subject: Re: [PATCH for-8.1] linux-user: Define real MAP_FIXED_NOREPLACE value
Date: Tue, 8 Aug 2023 09:19:38 -0700 [thread overview]
Message-ID: <af38a30d-e91c-2354-812b-c1938487424f@linaro.org> (raw)
In-Reply-To: <5e416a73-365e-407d-98fa-3b48be20045d@daynix.com>
On 8/8/23 08:16, Akihiko Odaki wrote:
>> Which supported hosts do not define this value? Can we simply remove the fallback?
>
> glibc didn't have this defined until 2.28. The older releases still maintained are 2.26,
> and 2.27, according to:
> https://sourceware.org/glibc/wiki/Release
Thanks for digging into glibc versions.
> The page says ALT Linux p9 and Ubuntu 18.04 LTS (Bionic Beaver) has glibc 2.27.
QEMU says
# Support for the previous major version will be dropped 2 years
# after the new major version is released or when the vendor itself
# drops support, whichever comes first.
Ubuntu 22.04 is the current major version, so 20.04 is still supported until 2024, but
18.04 is unsupported.
Similarly, ALT 10.0 was released in 2021, so ALT 9 is now unsupported.
I have just run a patch to remove the fallback through gitlab CI and it has passed:
https://gitlab.com/rth7680/qemu/-/pipelines/959680899/
r~
prev parent reply other threads:[~2023-08-08 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 11:52 [PATCH for-8.1] linux-user: Define real MAP_FIXED_NOREPLACE value Akihiko Odaki
2023-08-08 14:42 ` Richard Henderson
2023-08-08 15:16 ` Akihiko Odaki
2023-08-08 16:19 ` Richard Henderson [this message]
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=af38a30d-e91c-2354-812b-c1938487424f@linaro.org \
--to=richard.henderson@linaro.org \
--cc=akihiko.odaki@daynix.com \
--cc=alex.bennee@linaro.org \
--cc=deller@gmx.de \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).