From: Alexander Graf <agraf@suse.de>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Richard Henderson <rth@twiddle.net>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] pc-bios/s390-ccw: build s390 bios with -fno-zero-initialized-in-bss
Date: Mon, 20 Nov 2017 10:19:31 +0100 [thread overview]
Message-ID: <5a4be37f-29b5-1d0d-91ab-9cb15c93e088@suse.de> (raw)
In-Reply-To: <20171120091520.86128-1-borntraeger@de.ibm.com>
On 11/20/2017 10:15 AM, Christian Borntraeger wrote:
> The QEMU ELF loader does not initialize the bss segment. This has
> triggered several bugs in the past, e.g. see commit 5d739a4787a5
> ("s390-ccw.img: Fix sporadic errors with ccw boot image - initialize
> css").
>
> Instead of fixing these things one-by-one we can build the BIOS
> with -fno-zero-initialized-in-bss. This will move the zero variables
> also into the data segment, which is then part of a LOAD section.
Doesn't this bloat the firmware? Why don't we just manually clear bss in
the firmware itself? It's what all other firmwares do :)
Alex
next prev parent reply other threads:[~2017-11-20 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 9:15 [Qemu-devel] [PATCH] pc-bios/s390-ccw: build s390 bios with -fno-zero-initialized-in-bss Christian Borntraeger
2017-11-20 9:19 ` Alexander Graf [this message]
2017-11-20 9:27 ` Christian Borntraeger
2017-11-20 9:29 ` Alexander Graf
2017-11-20 10:02 ` Christian Borntraeger
2017-11-20 10:16 ` Alexander Graf
2017-11-20 10:19 ` Christian Borntraeger
2017-11-20 10:24 ` Alexander Graf
2017-11-20 10:27 ` Christian Borntraeger
2017-11-20 13:13 ` Richard Henderson
2017-11-20 9:20 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
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=5a4be37f-29b5-1d0d-91ab-9cb15c93e088@suse.de \
--to=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--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).