public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
	Avi Kivity <avi@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Carsten Otte <cotte@de.ibm.com>, Alexander Graf <agraf@suse.de>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	KVM <kvm@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [PATCH 0/6] kvm/s390: sigp related changes for 3.6
Date: Mon, 2 Jul 2012 12:00:20 +0200	[thread overview]
Message-ID: <20120702120020.1525923d@de.ibm.com> (raw)
In-Reply-To: <20120629231946.GB14304@amt.cnet>

On Fri, 29 Jun 2012 20:19:46 -0300
Marcelo Tosatti <mtosatti@redhat.com> wrote:

> On Tue, Jun 26, 2012 at 04:06:35PM +0200, Cornelia Huck wrote:
> > Avi, Marcelo,
> > 
> > here are some more s390 patches for the next release.
> > 
> > Patches 1 and 2 are included for dependency reasons; they will also
> > be sent through Martin's s390 tree.
> 
> I don't see why patch 1 is a dependency for merging in the kvm 
> tree, and why patch 2 should go through both trees?
> 
> That is, patch 1 can go through S390 tree, patches 2-6 through 
> KVM tree. No?

Patch 3 has a dependency on patch 2 and patch 2 has a dependency
on patch 1. The hunk in pcpu_running would cause a reject:

@@ -155,8 +131,8 @@ static inline int pcpu_stopped(struct pcpu *pcpu)
 
 static inline int pcpu_running(struct pcpu *pcpu)
 {
-       if (__pcpu_sigp(pcpu->address, sigp_sense_running,
-                       0, &pcpu->status) != sigp_status_stored)
+       if (__pcpu_sigp(pcpu->address, SIGP_SENSE_RUNNING,
+                       0, &pcpu->status) != SIGP_CC_STATUS_STORED)
                return 1;
        /* Status stored condition code is equivalent to cpu not running. */
        return 0;


-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.


  reply	other threads:[~2012-07-02 10:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 14:06 [PATCH 0/6] kvm/s390: sigp related changes for 3.6 Cornelia Huck
2012-06-26 14:06 ` [PATCH 1/6] s390/smp: remove redundant check Cornelia Huck
2012-06-26 14:06 ` [PATCH 2/6] s390/smp/kvm: unifiy sigp definitions Cornelia Huck
2012-06-26 14:06 ` [PATCH 3/6] KVM: s390: fix sigp sense running condition code handling Cornelia Huck
2012-06-26 14:52   ` Alexander Graf
2012-06-26 15:33     ` Cornelia Huck
2012-06-26 15:36       ` Alexander Graf
2012-06-26 15:57         ` Cornelia Huck
2012-06-26 16:03           ` Alexander Graf
2012-06-26 14:06 ` [PATCH 4/6] KVM: s390: fix sigp set prefix status stored cases Cornelia Huck
2012-06-26 14:56   ` Alexander Graf
2012-06-26 15:39     ` Cornelia Huck
2012-06-26 15:42       ` Alexander Graf
2012-06-26 14:06 ` [PATCH 5/6] KVM: s390: use sigp condition code defines Cornelia Huck
2012-06-26 14:06 ` [PATCH 6/6] KVM: s390: Fix sigp sense handling Cornelia Huck
2012-06-29 23:19 ` [PATCH 0/6] kvm/s390: sigp related changes for 3.6 Marcelo Tosatti
2012-07-02 10:00   ` Martin Schwidefsky [this message]
2012-07-02 23:16 ` Marcelo Tosatti

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=20120702120020.1525923d@de.ibm.com \
    --to=schwidefsky@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mtosatti@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