public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Marcelo Tossati <mtosatti@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	KVM <kvm@vger.kernel.org>,
	linux-s390@vger.kernel.org
Subject: Re: [PATCH 0/3] s390/kvm fixes
Date: Wed, 30 Jan 2013 12:30:17 +0200	[thread overview]
Message-ID: <20130130103017.GG15004@redhat.com> (raw)
In-Reply-To: <5108DF0C.3090907@de.ibm.com>

On Wed, Jan 30, 2013 at 09:51:24AM +0100, Christian Borntraeger wrote:
> On 29/01/13 22:03, Gleb Natapov wrote:
> 
> >> The question about 1/1. It is CCed to stable, does this mean you want it
> >> to go to 3.8? kvm-next is for 3.9.
> >>
> > On the second thought, if it is not a regression 3.9 is the right place.
> 
> The store status part is broken, but it only has a severe impact in case of 
> a machine check. (The machine check handler revalidates all registers with
> the content of the save area).
> Since machine checks are part of the virtio-ccw code, this can go into 3.9.
> Feel free to remove the CC:stable. 
> 
No reason to drop stable, but 3.8 will have to get the fix through
stable to after it is released.

--
			Gleb.

  reply	other threads:[~2013-01-30 10:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 14:34 [PATCH 0/3] s390/kvm fixes Christian Borntraeger
2013-01-25 14:34 ` [PATCH 1/3] s390/kvm: Fix store status for ACRS/FPRS Christian Borntraeger
2013-01-25 14:34 ` [PATCH 2/3] s390/virtio-ccw: Fix setup_vq error handling Christian Borntraeger
2013-01-25 14:35   ` Christian Borntraeger
2013-01-25 14:34 ` [PATCH 3/3] s390/kvm: Fix instruction decoding Christian Borntraeger
2013-01-29 13:12 ` [PATCH 0/3] s390/kvm fixes Gleb Natapov
2013-01-29 20:41   ` Christian Borntraeger
2013-01-29 20:46     ` Gleb Natapov
2013-01-29 21:03       ` Gleb Natapov
2013-01-30  8:51         ` Christian Borntraeger
2013-01-30 10:30           ` Gleb Natapov [this message]
2013-01-30 10:36 ` Gleb Natapov

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=20130130103017.GG15004@redhat.com \
    --to=gleb@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=schwidefsky@de.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