From: Thomas Huth <thuth@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
David Hildenbrand <david@redhat.com>,
Farhan Ali <alifm@linux.vnet.ibm.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
"Collin L. Walling" <walling@linux.vnet.ibm.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] S390 bios breaks in qemu 2.10.rc3
Date: Tue, 29 Aug 2017 11:35:22 +0200 [thread overview]
Message-ID: <c79ab349-116d-10d5-9310-f3ff8a6b4b81@redhat.com> (raw)
In-Reply-To: <2fdd5a70-6339-c4ec-c13c-d6f96d7abfc9@de.ibm.com>
On 28.08.2017 09:18, Christian Borntraeger wrote:
>
>
> On 08/25/2017 10:29 AM, Cornelia Huck wrote:
>> On Fri, 25 Aug 2017 10:21:58 +0200
>> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
>>
>>> On 08/25/2017 09:20 AM, Cornelia Huck wrote:
>>
>>>> OK, to recap:
>>>>
>>>> - the current pre-built bios seems fine
>>>> - rebuilding the bios may yield a version that fails on some systems
>>>> (different compiler?)
>>>> - adding aligned(8) looks like the right thing to do
>>>> - it seems to fix the problem, but on at least one system something
>>>> still seems off (under investigation)
>>>
>>> Yes. I am out of office today, so for any aligned(8) patch
>>> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
>>> even for 2.10.
>>
>> I fear the 2.10 train has already left the station, but any aligned(8)
>> patch should be cc:stable.
>
> I think this could be a topic for QEMU summit. Our process of not allowing
> fixes in rcx without requiring an rc(x+1) seems a bit odd. The Linux kernel
> style (there are fixes between the last rc and release) seems more balanced
> as long as we establish some safety nets.
This sounds like a good idea to me, yes. And maybe we could also ease
the situation a little bit by providing the first stable .1 release
already two or three weeks after the .0 release [*] ? Then these "we are
not 100% sure whether this is a severe blocker or not" patches could
simply be provided to the public with that .1 release instead of
blocking the QEMU master branch in freeze state...
Thomas
[*] I know that means more additional work for Michael - sorry for that
... but at least we should talk about this, I think. Maybe someone else
could also help with the releases if it's too much work for one person?
next prev parent reply other threads:[~2017-08-29 9:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 15:05 [Qemu-devel] S390 bios breaks in qemu 2.10.rc3 Farhan Ali
2017-08-24 15:13 ` Cornelia Huck
2017-08-24 15:35 ` Thomas Huth
2017-08-24 15:47 ` Halil Pasic
2017-08-24 15:50 ` Thomas Huth
2017-08-24 15:53 ` Farhan Ali
2017-08-24 16:02 ` Halil Pasic
2017-08-24 18:15 ` Christian Borntraeger
2017-08-24 16:07 ` Peter Maydell
2017-08-24 17:38 ` Farhan Ali
2017-08-24 18:14 ` Christian Borntraeger
2017-08-25 7:20 ` Cornelia Huck
2017-08-25 8:21 ` Christian Borntraeger
2017-08-25 8:29 ` Cornelia Huck
2017-08-28 7:18 ` Christian Borntraeger
2017-08-29 9:35 ` Thomas Huth [this message]
2017-08-29 10:28 ` Christian Borntraeger
2017-08-31 17:44 ` Michael Roth
2017-09-01 7:06 ` Christian Ehrhardt
2017-09-01 14:03 ` Michael Roth
2017-08-25 14:38 ` Philippe Mathieu-Daudé
2017-08-24 15:37 ` Halil Pasic
2017-08-24 18:33 ` Christian Borntraeger
2017-08-24 19:56 ` Farhan Ali
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=c79ab349-116d-10d5-9310-f3ff8a6b4b81@redhat.com \
--to=thuth@redhat.com \
--cc=alifm@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=walling@linux.vnet.ibm.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).