From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>,
qemu-s390x <qemu-s390x@nongnu.org>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] s390x/kvm: implement new hardware/firmware features
Date: Thu, 18 Jan 2018 14:31:50 +0100 [thread overview]
Message-ID: <CAATJJ0+4djFATj5qYn5UR=OtK4w0qT2PcPySeMXXNT7PSaQhPg@mail.gmail.com> (raw)
In-Reply-To: <20180118141530.17faabd1.cohuck@redhat.com>
On Thu, Jan 18, 2018 at 2:15 PM, Cornelia Huck <cohuck@redhat.com> wrote:
> On Thu, 18 Jan 2018 13:47:54 +0100
> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
>
>> Have the x86 features been marked as stable? If the answer is yes,
>> shall we mark these patches for stable as well?
>
> Doesn't look like it.
>
> TBH, I'm not quite sure whether this should go into stable as I'm a bit
> unclear what our use case for stable is. It seems to be mostly "don't
> let people run into known crashes" or something like that.
I read the public statement [1] as "... non-x86 processors ...
backported to recent stable releases." or did the changes in
discussion here end up structurally so different that this doesn't
apply anymore?
[1]: https://www.qemu.org/2018/01/04/spectre/
next prev parent reply other threads:[~2018-01-18 13:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 8:56 [Qemu-devel] [PATCH v3 0/3] s390x/kvm: implement new hardware/firmware features Christian Borntraeger
2018-01-18 8:56 ` [Qemu-devel] [PATCH v3 1/3] header sync Christian Borntraeger
2018-01-18 11:42 ` David Hildenbrand
2018-01-22 8:31 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-01-22 8:47 ` Cornelia Huck
2018-01-18 8:56 ` [Qemu-devel] [PATCH v3 2/3] s390x/kvm: Handle bpb feature Christian Borntraeger
2018-01-18 11:42 ` Thomas Huth
2018-01-18 11:43 ` David Hildenbrand
2018-01-18 12:01 ` Halil Pasic
2018-01-18 12:09 ` Christian Borntraeger
2018-01-18 8:56 ` [Qemu-devel] [PATCH v3 3/3] s390x/kvm: provide stfle.81 Christian Borntraeger
2018-01-18 11:05 ` Halil Pasic
2018-01-18 11:43 ` David Hildenbrand
2018-01-18 11:43 ` Thomas Huth
2018-01-18 11:53 ` [Qemu-devel] [PATCH v3 0/3] s390x/kvm: implement new hardware/firmware features Cornelia Huck
2018-01-18 12:47 ` Christian Borntraeger
2018-01-18 13:15 ` Cornelia Huck
2018-01-18 13:31 ` Christian Ehrhardt [this message]
2018-01-18 14:48 ` Cornelia Huck
2018-01-22 10:20 ` Cornelia Huck
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='CAATJJ0+4djFATj5qYn5UR=OtK4w0qT2PcPySeMXXNT7PSaQhPg@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.