RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1485398 - Backport selective allocation of PGSTE to avoid global vm.allocate_pgste
Summary: Backport selective allocation of PGSTE to avoid global vm.allocate_pgste
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: binutils
Version: 7.5-Alt
Hardware: s390x
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Nick Clifton
QA Contact: Miloš Prchlík
Vladimír Slávik
Depends On:
Blocks: 1473718 1485399
TreeView+ depends on / blocked
Reported: 2017-08-25 14:53 UTC by David Hildenbrand
Modified: 2018-04-10 10:00 UTC (History)
10 users (show)

Fixed In Version: binutils-2.27-15.base.el7
Doc Type: Enhancement
Doc Text:
Support for selective use of 4 KiB page tables on IBM z Systems This update adds the option `--s390-pgste` to the *ld* linker from the _binutils_ package to mark applications for the IBM z Systems architecture that require 4 KiB memory page tables on the lowest level. As a result, use of this feature can be restricted only to applications that need it, allowing optimal use of space by all applications on the system. Note that the *qemu* backend no longer forces 4 KiB lowest level page tables on all running applications. Make sure to specify the new option if your applications require them.
Clone Of:
Last Closed: 2018-04-10 09:59:05 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1488889 0 unspecified CLOSED s390x: binutils strip tool segfaults 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2018:0686 0 None None None 2018-04-10 10:00:54 UTC

Internal Links: 1488889

Description David Hildenbrand 2017-08-25 14:53:48 UTC
Description of problem:
For now we have to enable allocation of PGSTE globally, using sysctl vm.allocate_pgste=1 (see bz 1454281) in order to be able to run qemu-kvm guests.

This results in the double size of lowest level page tables of all processes. Latest upstream contribution allow to allocate PGSTE selectively, per process. This requires kernel, QEMU and binutil changes.

Additional info:
We have to backport for the binutils part the following commit

commit b4cbbe8f7294070cc93a71ace78f134965ddad82
Author: Andreas Krebbel <krebbel.ibm.com>
Date:   Thu Jun 8 17:24:50 2017 +0200

    S/390: Add support for pgste marker

Comment 20 Miloš Prchlík 2018-02-01 08:20:57 UTC
Verified with binutils-2.27-27.base.el7.s390x.

Comment 23 errata-xmlrpc 2018-04-10 09:59:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.