kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: "Christian Borntraeger" <borntraeger@de.ibm.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Fan Zhang <zhangfan@linux.vnet.ibm.com>
Subject: Re: [GIT PULL 5/9] KVM: s390: gs support for kvm guests
Date: Tue, 11 Apr 2017 16:04:12 +0200	[thread overview]
Message-ID: <268251a5-26fa-f1b5-4900-11cc398b43f0@redhat.com> (raw)
In-Reply-To: <e2a724be-790d-ea9f-69a0-72b5782740a2@de.ibm.com>

On 11.04.2017 14:42, Christian Borntraeger wrote:
> On 04/07/2017 02:01 PM, Christian Borntraeger wrote:
>>
>> Indeed this looks like a bug (and the right fix).
>>
>> This was not noticed during test since KVM enables the host management of
>> registers and we do not use the sdnx. So for the KVM under KVM case this
>> does not matter. Still, we should fix it.
>>
>> Radim, Paolo, do you want a respin of the whole series or can I simply send
>> a fixup patch with the next round of patches?
> 
> Radim, Paolo,
> 
> is it ok to schedule the fixup patch for the next round of patches(I plan to
> have some more for 4.12 anyway) and apply this series as is?

This fix really has low priority (hw not available, KVM not using this
feature), so I think this fixup can wait.

-- 

Thanks,

David

  reply	other threads:[~2017-04-11 14:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 10:47 [GIT PULL 0/9] KVM: s390: features for 4.12 (via kvm/next) Christian Borntraeger
2017-04-07 10:47 ` [GIT PULL 1/9] KVM: s390: log runtime instrumentation enablement Christian Borntraeger
2017-04-07 10:47 ` [GIT PULL 2/9] KVM: s390: Handle sthyi also for instruction intercept Christian Borntraeger
2017-04-07 10:47 ` [GIT PULL 3/9] KVM: s390: use defines for execution controls Christian Borntraeger
2017-04-07 10:47 ` [GIT PULL 4/9] KVM: s390: Use defines for intercept code Christian Borntraeger
2017-04-07 10:47 ` [GIT PULL 5/9] KVM: s390: gs support for kvm guests Christian Borntraeger
2017-04-07 11:42   ` David Hildenbrand
2017-04-07 12:01     ` Christian Borntraeger
2017-04-11 12:42       ` Christian Borntraeger
2017-04-11 14:04         ` David Hildenbrand [this message]
2017-04-11 19:23         ` Radim Krčmář
2017-04-07 12:27     ` [PATCH] KVM: s390: Fix sdnxo setting for nested guests Christian Borntraeger
2017-04-11 11:55       ` Cornelia Huck
2017-04-07 10:47 ` [GIT PULL 6/9] KVM: s390: interface for suppressible I/O adapters Christian Borntraeger
2017-04-07 10:48 ` [GIT PULL 7/9] KVM: s390: introduce ais mode modify function Christian Borntraeger
2017-04-07 10:48 ` [GIT PULL 8/9] KVM: s390: introduce adapter interrupt inject function Christian Borntraeger
2017-04-07 10:48 ` [GIT PULL 9/9] KVM: s390: introduce AIS capability Christian Borntraeger

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=268251a5-26fa-f1b5-4900-11cc398b43f0@redhat.com \
    --to=david@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=zhangfan@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).