From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: [GIT PULL 00/18] KVM: s390: Fixes and features for kvm/next (4.6)
Date: Fri, 12 Feb 2016 23:25:40 +0100 [thread overview]
Message-ID: <56BE5BE4.9090804@redhat.com> (raw)
In-Reply-To: <56BE332F.6060005@de.ibm.com>
On 12/02/2016 20:31, Christian Borntraeger wrote:
> On 02/12/2016 05:18 PM, Paolo Bonzini wrote:
>>
>>
>> On 12/02/2016 17:08, Christian Borntraeger wrote:
>>>>> I need one patch for 4.4 as well (vs. 3 patches against 4.5-rc3). So bisect is broken
>>>>> on 4.4 as well, I just had it fixed earlier.
>>>>
>>>> If these three patches are in Linus's tree, just send the pull request
>>>> against that. It's okay if a submaintainer pull request brings back a
>>>> few more commits from Linus's tree.
>>>
>>> Not yet in Linus tree (cgroup-fixes mostly)
>>
>> As long as the bugs only surface with libvirt, I guess that's acceptable.
>
> If disabling the cpuset controller in libvirt + disabling thp is considered
> ok for bisecting, then you can go ahead and pull.
Well, certainly not optimal but feasible.
> Otherwise I can wait for
> the cgroup fix tree to be pulled and then rebase.
Ok, then I'll pull it and add a note in the merge commit to Linus.
Paolo
next prev parent reply other threads:[~2016-02-12 22:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 13:22 [GIT PULL 00/18] KVM: s390: Fixes and features for kvm/next (4.6) Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 01/18] KVM: s390: allow sync of fp registers via vregs Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 02/18] KVM: s390: sync of fp registers via kvm_run Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 03/18] KVM: s390: PSW forwarding / rewinding / ilc rework Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 04/18] KVM: s390: migration / injection of prog irq ilc Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 05/18] KVM: s390: gaccess: introduce access modes Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 06/18] KVM: s390: gaccess: implement instruction fetching mode Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 07/18] KVM: s390: read the correct opcode on SIE faults Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 08/18] KVM: s390: clean up prog irq injection on prog irq icpts Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 09/18] KVM: s390: irq delivery should not rely on icptcode Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 10/18] KVM: s390: provide prog irq ilc on SIE faults Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 11/18] KVM: s390: instruction-fetching exceptions " Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 12/18] KVM: s390: remove old fragment of vector registers Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 13/18] KVM: s390: add documentation of KVM_S390_VM_TOD Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 14/18] KVM: s390: add documentation of KVM_S390_VM_CRYPTO Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 15/18] KVM: s390: usage hint for adapter mappings Christian Borntraeger
2016-02-12 13:23 ` [GIT PULL 16/18] KVM: s390: do not take mmap_sem on dirty log query Christian Borntraeger
2016-02-12 13:23 ` [GIT PULL 17/18] KVM: s390: do not block CPU on dirty logging Christian Borntraeger
2016-02-12 13:23 ` [GIT PULL 18/18] KVM: s390: bail out early on fatal signal in " Christian Borntraeger
2016-02-12 15:51 ` [GIT PULL 00/18] KVM: s390: Fixes and features for kvm/next (4.6) Paolo Bonzini
2016-02-12 15:54 ` Christian Borntraeger
2016-02-12 16:00 ` Paolo Bonzini
2016-02-12 16:08 ` Christian Borntraeger
2016-02-12 16:15 ` Christian Borntraeger
2016-02-12 16:18 ` Paolo Bonzini
2016-02-12 19:31 ` Christian Borntraeger
2016-02-12 22:25 ` Paolo Bonzini [this message]
2016-02-16 17:48 ` Paolo Bonzini
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=56BE5BE4.9090804@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/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.