From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5A096C25B47 for ; Fri, 27 Oct 2023 20:50:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346609AbjJ0UuO (ORCPT ); Fri, 27 Oct 2023 16:50:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60260 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235228AbjJ0UuC (ORCPT ); Fri, 27 Oct 2023 16:50:02 -0400 Received: from mail-pl1-x64a.google.com (mail-pl1-x64a.google.com [IPv6:2607:f8b0:4864:20::64a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 77EC110F5 for ; Fri, 27 Oct 2023 13:49:53 -0700 (PDT) Received: by mail-pl1-x64a.google.com with SMTP id d9443c01a7336-1cc1397321fso16511605ad.3 for ; Fri, 27 Oct 2023 13:49:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1698439790; x=1699044590; darn=vger.kernel.org; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:reply-to:from:to:cc:subject:date:message-id:reply-to; bh=EEVVIsdWWT2F4uMf1c4FvIiobmGg9JUhgceROHEWR+A=; b=KM//VnsNn9eRKvDQY5CbQMCsyot6SVvJBRSEFbCBEe3Ubg1X9gqXnF6n1n2SgLIzEj Q5l5ReWlTt3NvpdovcR9ZZ5UIXThZfSsA8EXafz31XVlD3zdAjcF7pJ9BQpJlvlikmrT 3f5GuCPfxC70ejEcl4eZF85NsjzZkqn6GttHQpxVXFE13Ic9TNSZCxV7MsXJZ8ODxoiN yG22nYcIwafWSuy9KDvEQNjvqUNHmnH5NMbQty1FyP99BZ6ND4dCSWmIzqMWLXqejKPU Rx927EwVFuNGm3FpdOnshsPFyD5hEz00lwXuYqq8ECE2jq8eP8Yr6dTIEc/YdSNacEQa HE9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698439790; x=1699044590; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:reply-to:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=EEVVIsdWWT2F4uMf1c4FvIiobmGg9JUhgceROHEWR+A=; b=fvTBCZFOJgUcH7YKQbTtE+psQUypMy6HYWCnkEpmz046KYK1i/nOVeTAnvLdbE1P+e OwtD5LzWIjDCrU7VBv3ToDfEiI6mWgOAt2l1mODJDAkWqEwOmZ+6x0vW4N2k3Y+DDG3N EjiaGDc4XDLuaRNVgxPT4mBFA2+zCNH89oyhO8evfHTwIw68rOAiZoY7CS3DiE57+L9a W7FpsPCvnf6JrVqfleyggVJ9HJ0evy1FspLr672qvDIDXbYH+0sZOtUDErgG0nJt6eOB EfseBTxqUP03WZKtXOAaKHJIUgaqUbm2KcqLbjGaRO7ufngMcVX/UDWExiSIDt/wicoC fMKQ== X-Gm-Message-State: AOJu0YwzIeEX2GDssmvK+0pCLRJ0t+vCsC9bRUNli0xqxRhzQgi8pJRp MC3nuuEw7B9AVJ2ISQbonaZQh5b66cQ= X-Google-Smtp-Source: AGHT+IG04UfCML503rxDdENeI/UsmLklRO2aHvHgYtsD0qYmJgbWaUdx3sIsou8BPaqxlbnXBD9t5lxONX0= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:902:a411:b0:1c9:c879:ee82 with SMTP id p17-20020a170902a41100b001c9c879ee82mr61492plq.11.1698439790722; Fri, 27 Oct 2023 13:49:50 -0700 (PDT) Reply-To: Sean Christopherson Date: Fri, 27 Oct 2023 13:49:31 -0700 In-Reply-To: <20231027204933.3651381-1-seanjc@google.com> Mime-Version: 1.0 References: <20231027204933.3651381-1-seanjc@google.com> X-Mailer: git-send-email 2.42.0.820.g83a721a137-goog Message-ID: <20231027204933.3651381-8-seanjc@google.com> Subject: [GIT PULL] KVM: x86: Xen changes for 6.7 From: Sean Christopherson To: Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Sean Christopherson Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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(-)