From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: x86: Xen changes for 6.7
Date: Fri, 27 Oct 2023 13:49:31 -0700 [thread overview]
Message-ID: <20231027204933.3651381-8-seanjc@google.com> (raw)
In-Reply-To: <20231027204933.3651381-1-seanjc@google.com>
Read the tag, I couldn't figure out how to summarize this one without simply
regurgitating the tag :-)
The following changes since commit 5804c19b80bf625c6a9925317f845e497434d6d3:
Merge tag 'kvm-riscv-fixes-6.6-1' of https://github.com/kvm-riscv/linux into HEAD (2023-09-23 05:35:55 -0400)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-xen-6.7
for you to fetch changes up to 409f2e92a27a210fc768c5569851b4a419e6a232:
KVM: x86/xen: ignore the VCPU_SSHOTTMR_future flag (2023-10-04 15:22:58 -0700)
----------------------------------------------------------------
KVM x86 Xen changes for 6.7:
- Omit "struct kvm_vcpu_xen" entirely when CONFIG_KVM_XEN=n.
- Use the fast path directly from the timer callback when delivering Xen timer
events. Avoid the problematic races with using the fast path by ensuring
the hrtimer isn't running when (re)starting the timer or saving the timer
information (for userspace).
- Follow the lead of upstream Xen and ignore the VCPU_SSHOTTMR_future flag.
----------------------------------------------------------------
David Woodhouse (1):
KVM: x86/xen: Use fast path for Xen timer delivery
Paul Durrant (1):
KVM: x86/xen: ignore the VCPU_SSHOTTMR_future flag
Peng Hao (1):
KVM: X86: Reduce size of kvm_vcpu_arch structure when CONFIG_KVM_XEN=n
arch/x86/include/asm/kvm_host.h | 5 +++-
arch/x86/kvm/cpuid.c | 2 ++
arch/x86/kvm/x86.c | 2 ++
arch/x86/kvm/xen.c | 55 +++++++++++++++++++++++++++++++++++++----
4 files changed, 58 insertions(+), 6 deletions(-)
next prev parent reply other threads:[~2023-10-27 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 20:49 [GIT PULL] KVM: x86 pull requests " Sean Christopherson
2023-10-27 20:49 ` [GIT PULL] KVM: x86: APIC changes " Sean Christopherson
2023-10-31 14:15 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: Documentation updates " Sean Christopherson
2023-10-31 14:14 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2023-10-31 14:21 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2023-10-31 14:20 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: PMU change " Sean Christopherson
2023-10-27 20:49 ` [GIT PULL] KVM: x86: SVM changes " Sean Christopherson
2023-10-31 14:55 ` Paolo Bonzini
2023-10-27 20:49 ` Sean Christopherson [this message]
2023-10-31 14:22 ` [GIT PULL] KVM: x86: Xen " Paolo Bonzini
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=20231027204933.3651381-8-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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
all inboxes | Powered by JetHome®