kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
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>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Uros Bizjak <ubizjak@gmail.com>,
	Like Xu <like.xu.linux@gmail.com>
Subject: [PATCH v2 0/2] KVM: x86: Purge __ex() and __kvm_spurious_fault()
Date: Mon,  9 Aug 2021 10:39:53 -0700	[thread overview]
Message-ID: <20210809173955.1710866-1-seanjc@google.com> (raw)

Two patches to remove __ex() and __kvm_spurious_fault(), and hide
kvm_spurious_fault() in x86.h.  These were part of a larger series that
received the magic "Queued, thanks", but got lost at some point.

v1: https://lore.kernel.org/kvm/20201231002702.2223707-1-seanjc@google.com/

Sean Christopherson (1):
  KVM: x86: Kill off __ex() and __kvm_handle_fault_on_reboot()

Uros Bizjak (1):
  KVM: x86: Move declaration of kvm_spurious_fault() to x86.h

 arch/x86/include/asm/kvm_host.h | 25 -------------------------
 arch/x86/kvm/svm/sev.c          |  2 --
 arch/x86/kvm/svm/svm.c          |  2 --
 arch/x86/kvm/svm/svm_ops.h      |  2 +-
 arch/x86/kvm/vmx/vmx_ops.h      |  4 +---
 arch/x86/kvm/x86.c              |  9 ++++++++-
 arch/x86/kvm/x86.h              |  2 ++
 7 files changed, 12 insertions(+), 34 deletions(-)

-- 
2.32.0.605.g8dce9f2422-goog


             reply	other threads:[~2021-08-09 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 17:39 Sean Christopherson [this message]
2021-08-09 17:39 ` [PATCH v2 1/2] KVM: x86: Kill off __ex() and __kvm_handle_fault_on_reboot() Sean Christopherson
2021-08-09 17:39 ` [PATCH v2 2/2] KVM: x86: Move declaration of kvm_spurious_fault() to x86.h Sean Christopherson
2021-08-10 17:40 ` [PATCH v2 0/2] KVM: x86: Purge __ex() and __kvm_spurious_fault() 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=20210809173955.1710866-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=like.xu.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=ubizjak@gmail.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).