From: Paolo Bonzini <pbonzini@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>,
Sean Christopherson <seanjc@google.com>
Cc: Paul Durrant <paul@xen.org>, Michal Luczaj <mhal@rbox.co>,
kvm@vger.kernel.org
Subject: Re: [PATCH v1 0/2] KVM: x86/xen: Runstate cleanups on top of kvm/queue
Date: Fri, 2 Dec 2022 20:00:25 +0100 [thread overview]
Message-ID: <561885a1-e1de-21f2-1da9-5abfea2a1045@redhat.com> (raw)
In-Reply-To: <24408924dbe6041472f5e401f40c29311e1edd99.camel@infradead.org>
On 11/30/22 20:51, David Woodhouse wrote:
> On Wed, 2022-11-30 at 17:03 +0100, Paolo Bonzini wrote:
>> On 11/27/22 13:22, David Woodhouse wrote:
>>> Clean the update code up a little bit by unifying the fast and slow
>>> paths as discussed, and make the update flag conditional to avoid
>>> confusing older guests that don't ask for it.
>>>
>>> On top of kvm/queue as of today at commit da5f28e10aa7d.
>>>
>>> (This is identical to what I sent a couple of minutes ago, except that
>>> this time I didn't forget to Cc the list)
>>>
>>>
>>
>> Merged, thanks.
>
> Thanks. I've rebased the remaining GPC fixes on top and pushed them out
> (along with Metin's SCHEDOP_poll 32-bit compat support) to
>
> https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/gpc-fixes
Oh, so we do pull requests now too? I'm all for it, but please use
signed tags. :)
> I still haven't reinstated the last of those patches to make gpc->len
> immutable, although I think we concluded it's fine just to make the
> runstate code claim gpc->len=1 and manage its own destiny, right?
Yeah, I'm not super keen on that either, but I guess it can work with
any of len == 1 or len == PAGE_SIZE - offset.
Related to this, for 6.3 I will send a cleanup of the API to put
together lock and check.
Paolo
> In reviewing the merge/squash I spotted a minor cosmetic nit in my
> 'Allow XEN_RUNSTATE_UPDATE flag behaviour to be configured' commit.
> It'd be slightly prettier like this, although the compiler really ought
> to emit identical code.
>
> diff --git a/arch/x86/kvm/xen.c b/arch/x86/kvm/xen.c
> index 5208e05ca9a6..76b7fc6d543a 100644
> --- a/arch/x86/kvm/xen.c
> +++ b/arch/x86/kvm/xen.c
> @@ -382,7 +382,7 @@ static void kvm_xen_update_runstate_guest(struct kvm_vcpu *v, bool atomic)
> entry_time = vx->runstate_entry_time;
> if (update_bit) {
> entry_time |= XEN_RUNSTATE_UPDATE;
> - *update_bit = (vx->runstate_entry_time | XEN_RUNSTATE_UPDATE) >> 56;
> + *update_bit = entry_time >> 56;
> smp_wmb();
> }
>
>
>
next prev parent reply other threads:[~2022-12-02 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 12:22 [PATCH v1 0/2] KVM: x86/xen: Runstate cleanups on top of kvm/queue David Woodhouse
2022-11-27 12:22 ` [PATCH v1 1/2] KVM: x86/xen: Reconcile fast and slow paths for runstate update David Woodhouse
2022-11-30 14:05 ` Paul Durrant
2022-11-27 12:22 ` [PATCH v1 2/2] KVM: x86/xen: Allow XEN_RUNSTATE_UPDATE flag behaviour to be configured David Woodhouse
2022-11-30 14:07 ` Paul Durrant
2022-11-30 16:03 ` [PATCH v1 0/2] KVM: x86/xen: Runstate cleanups on top of kvm/queue Paolo Bonzini
2022-11-30 19:51 ` David Woodhouse
2022-12-02 19:00 ` Paolo Bonzini [this message]
2022-12-02 19:03 ` Sean Christopherson
2022-12-02 20:17 ` David Woodhouse
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=561885a1-e1de-21f2-1da9-5abfea2a1045@redhat.com \
--to=pbonzini@redhat.com \
--cc=dwmw2@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=paul@xen.org \
--cc=seanjc@google.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