From: David Woodhouse <dwmw2@infradead.org>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Joao Martins <joao.m.martins@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Metin Kaya <metikaya@amazon.co.uk>,
Paul Durrant <pdurrant@amazon.co.uk>
Subject: Re: [PATCH v2 1/2] KVM: x86/xen: PV oneshot timer fixes
Date: Sun, 13 Mar 2022 14:57:08 +0000 [thread overview]
Message-ID: <6fe5ae4ca4db60350f95fdafb8346f20abdfbd53.camel@infradead.org> (raw)
In-Reply-To: <1d35eef3-df9d-ab48-8b36-4d7874b405cc@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
On Sun, 2022-03-13 at 15:30 +0100, Paolo Bonzini wrote:
> Squashed, thanks. But---sure you want to get rid of timer migration?
Yeah, it's just pointless complexity. These are only one-shot timers;
they'll get set up again on the new CPU soon enough.
Xen guests generally just turn off the periodic Xen timer, so we
haven't optimised that in the kernel; if we ever do then we can add the
migration back again.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
next prev parent reply other threads:[~2022-03-13 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 14:38 [PATCH 0/2] KVM: Xen PV timer fixups David Woodhouse
2022-03-09 14:38 ` [PATCH 1/2] KVM: x86/xen: PV oneshot timer fixes David Woodhouse
2022-03-09 15:39 ` Paolo Bonzini
2022-03-09 16:11 ` David Woodhouse
2022-03-09 16:28 ` Paolo Bonzini
2022-03-09 16:37 ` David Woodhouse
2022-03-09 16:39 ` Paolo Bonzini
2022-03-09 16:41 ` [PATCH v2 " David Woodhouse
2022-03-13 14:30 ` Paolo Bonzini
2022-03-13 14:57 ` David Woodhouse [this message]
2022-03-09 14:38 ` [PATCH 2/2] KVM: x86/xen: Update self test for Xen PV timers David Woodhouse
2022-03-09 14:47 ` [PATCH 0/2] KVM: Xen PV timer fixups 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=6fe5ae4ca4db60350f95fdafb8346f20abdfbd53.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=boris.ostrovsky@oracle.com \
--cc=jmattson@google.com \
--cc=joao.m.martins@oracle.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=metikaya@amazon.co.uk \
--cc=pbonzini@redhat.com \
--cc=pdurrant@amazon.co.uk \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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).