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: Wed, 30 Nov 2022 17:03:06 +0100 [thread overview]
Message-ID: <cd107b6c-ae02-8fa6-50e0-d6cbca7d88bc@redhat.com> (raw)
In-Reply-To: <20221127122210.248427-1-dwmw2@infradead.org>
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.
Paolo
next prev parent reply other threads:[~2022-11-30 16:04 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 ` Paolo Bonzini [this message]
2022-11-30 19:51 ` [PATCH v1 0/2] KVM: x86/xen: Runstate cleanups on top of kvm/queue David Woodhouse
2022-12-02 19:00 ` Paolo Bonzini
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=cd107b6c-ae02-8fa6-50e0-d6cbca7d88bc@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