From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alexander Graf <agraf@suse.de>, Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: "kvm@vger.kernel.org mailing list" <kvm@vger.kernel.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 0/4] PPC: KVM: fix RESUME_GUEST checks
Date: Fri, 07 Feb 2014 00:04:37 +0000 [thread overview]
Message-ID: <52F42315.9010100@ozlabs.ru> (raw)
In-Reply-To: <D00EA30F-A3AC-4869-AED2-7B079FB832DD@suse.de>
On 02/07/2014 04:39 AM, Alexander Graf wrote:
>
> On 06.02.2014, at 17:36, Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
>
>> As discussed in this thread:
>>
>> http://patchwork.ozlabs.org/patch/309166/
>>
>> We need some consistency in the way we check whether the guest
>> should resume or not because:
>> - new RESUME_GUEST_XXX values may show up
>> - more locations in KVM may need to perform a similar check
>>
>> This serie introduces a helper and patches the locations where it
>> should be called. There is yet another location in __kvmppc_vcpu_run,
>> but it is assembly and cannot call a C inlined function.
>
> Thanks, applied all to kvm-ppc-queue. I think the splitting on this one is quite excessive - a single patch would've done :).
Why did it get applied immediately? #3 or #4 (I do not remember for sure)
break HV KVM, this is why I do not repost it and keep trying Paul to reply
to the initial thread.
--
Alexey
WARNING: multiple messages have this Message-ID (diff)
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alexander Graf <agraf@suse.de>, Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: "kvm@vger.kernel.org mailing list" <kvm@vger.kernel.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 0/4] PPC: KVM: fix RESUME_GUEST checks
Date: Fri, 07 Feb 2014 11:04:37 +1100 [thread overview]
Message-ID: <52F42315.9010100@ozlabs.ru> (raw)
In-Reply-To: <D00EA30F-A3AC-4869-AED2-7B079FB832DD@suse.de>
On 02/07/2014 04:39 AM, Alexander Graf wrote:
>
> On 06.02.2014, at 17:36, Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
>
>> As discussed in this thread:
>>
>> http://patchwork.ozlabs.org/patch/309166/
>>
>> We need some consistency in the way we check whether the guest
>> should resume or not because:
>> - new RESUME_GUEST_XXX values may show up
>> - more locations in KVM may need to perform a similar check
>>
>> This serie introduces a helper and patches the locations where it
>> should be called. There is yet another location in __kvmppc_vcpu_run,
>> but it is assembly and cannot call a C inlined function.
>
> Thanks, applied all to kvm-ppc-queue. I think the splitting on this one is quite excessive - a single patch would've done :).
Why did it get applied immediately? #3 or #4 (I do not remember for sure)
break HV KVM, this is why I do not repost it and keep trying Paul to reply
to the initial thread.
--
Alexey
next prev parent reply other threads:[~2014-02-07 0:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 16:36 [PATCH 0/4] PPC: KVM: fix RESUME_GUEST checks Greg Kurz
2014-02-06 16:36 ` Greg Kurz
2014-02-06 16:36 ` [PATCH 1/4] PPC: KVM: introduce helper to check RESUME_GUEST and related Greg Kurz
2014-02-06 16:36 ` Greg Kurz
2014-02-06 16:37 ` [PATCH 2/4] PPC: KVM: fix VCPU run for HV KVM (v2) Greg Kurz
2014-02-06 16:37 ` Greg Kurz
2014-02-06 16:37 ` [PATCH 3/4] PPC: KVM: fix RESUME_GUEST check before ending CEDE in kvmppc_run_core() Greg Kurz
2014-02-06 16:37 ` Greg Kurz
2014-02-06 16:37 ` [PATCH 4/4] PPC: KVM: fix RESUME_GUEST check before returning from kvmppc_run_core() Greg Kurz
2014-02-06 16:37 ` Greg Kurz
2014-02-06 17:39 ` [PATCH 0/4] PPC: KVM: fix RESUME_GUEST checks Alexander Graf
2014-02-06 17:39 ` Alexander Graf
2014-02-07 0:04 ` Alexey Kardashevskiy [this message]
2014-02-07 0:04 ` Alexey Kardashevskiy
2014-02-07 1:29 ` Alexey Kardashevskiy
2014-02-07 1:29 ` Alexey Kardashevskiy
2014-02-07 8:14 ` Greg Kurz
2014-02-07 8:14 ` Greg Kurz
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=52F42315.9010100@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=gkurz@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@samba.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.