From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>, Thomas Huth <thuth@redhat.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Dan Horak <dhorak@redhat.com>
Subject: Re: [Qemu-devel] [PATCH/RFC] configure: enable --s390-pgste linker option
Date: Tue, 22 Aug 2017 17:02:01 +0200 [thread overview]
Message-ID: <c3e49a8a-8dec-51a4-f160-65a89abf9b8e@redhat.com> (raw)
In-Reply-To: <1503413250-18432-1-git-send-email-borntraeger@de.ibm.com>
On 22.08.2017 16:47, Christian Borntraeger wrote:
> KVM guests on s390 need a different page table layout than normal
> processes (2kb page table + 2kb page status extensions vs 2kb page table
> only). As of today this has to be enabled via the vm.allocate_pgste
> sysctl.
>
> Newer kernels (>= 4.12) on s390 check for an S390_PGSTE program header
> and enable the pgste page table extensions in that case. This makes the
> vm.allocate_pgste sysctl unnecessary. We enable this program header for
> the s390 system emulation (qemu-system-s390x) if
> - the linker supports --s390-pgste (binutils >= 2.29)
> - KVM is enabled
>
> This will allow distributions to disable the global vm.allocate_pgste
> sysctl, which will improve the page table allocation for non KVM
> processes as only 2kb chunks are necessary.
>
> Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> Cc: Alexander Graf <agraf@suse.de>
> Cc: Dan Horak <dhorak@redhat.com>
> Cc: David Hildenbrand <david@redhat.com>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Acked-by: Janosch Frank <frankja@linux.vnet.ibm.com>
> ---
> configure | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/configure b/configure
> index dd73cce..4c9084b 100755
> --- a/configure
> +++ b/configure
> @@ -6522,6 +6522,19 @@ if test "$target_linux_user" = "yes" -o "$target_bsd_user" = "yes" ; then
> ldflags="$ldflags $textseg_ldflags"
> fi
>
> +# Newer kernels on s390 check for an S390_PGSTE program header and
> +# enable the pgste page table extensions in that case. This makes
> +# the vm.allocate_pgste sysctl unnecessary. We enable this program
> +# header if
> +# - the linker support --s390-pgste
> +# - we build the system emulation (qemu-system-s390x)
> +# - KVM is enabled
> +if $ld --help 2>/dev/null | grep ".--s390-pgste" >/dev/null 2>/dev/null ; then
>/dev/null 2>&1
(from has(){} definiton)
maybe even introduce
ld_has() {
$ld --help 2>/dev/null | grep ".$1" >/dev/null 2>&1
}
I guess it also makes sense to test for s390x first, before checking for
ld support.
> + if test "$target_softmmu" = "yes" -a "$ARCH" = "s390x" -a "$kvm" = "yes" ; then
> + ldflags="-Wl,--s390-pgste $ldflags"
> + fi
> +fi
> +
> echo "LDFLAGS+=$ldflags" >> $config_target_mak
> echo "QEMU_CFLAGS+=$cflags" >> $config_target_mak
>
>
Happy to see this change :)
--
Thanks,
David
prev parent reply other threads:[~2017-08-22 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 14:47 [Qemu-devel] [PATCH/RFC] configure: enable --s390-pgste linker option Christian Borntraeger
2017-08-22 15:02 ` David Hildenbrand [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=c3e49a8a-8dec-51a4-f160-65a89abf9b8e@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=christian.ehrhardt@canonical.com \
--cc=cohuck@redhat.com \
--cc=dhorak@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).