From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: 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,
Derek Yerger <derek@djy.llc>,
kernel@najdan.com, Thomas Lambertz <mail@thomaslambertz.de>,
Rik van Riel <riel@surriel.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Borislav Petkov <bp@suse.de>, Dave Hansen <dave.hansen@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2 4/4] KVM: x86: Remove unused ctxt param from emulator's FPU accessors
Date: Sat, 18 Jan 2020 22:35:16 +0100 [thread overview]
Message-ID: <b8491683-3717-4dbe-637f-c3daeef08d81@redhat.com> (raw)
In-Reply-To: <20200117193052.1339-5-sean.j.christopherson@intel.com>
On 17/01/20 20:30, Sean Christopherson wrote:
> Remove an unused struct x86_emulate_ctxt * param from low level helpers
> used to access guest FPU state. The unused param was left behind by
> commit 6ab0b9feb82a ("x86,kvm: remove KVM emulator get_fpu / put_fpu").
>
> No functional change intended.
Makes sense since the new implementation of emulator_get/put_fpu can be
considered generic, and therefore it's okay not to tie it to ctxt->ops.
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-01-18 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 19:30 [PATCH v2 0/4] KVM: x86: TIF_NEED_FPU_LOAD bug fixes Sean Christopherson
2020-01-17 19:30 ` [PATCH v2 1/4] KVM: x86: Handle TIF_NEED_FPU_LOAD in kvm_{load,put}_guest_fpu() Sean Christopherson
2020-01-17 19:30 ` [PATCH v2 2/4] KVM: x86: Ensure guest's FPU state is loaded when accessing for emulation Sean Christopherson
2020-01-17 19:30 ` [PATCH v2 3/4] KVM: x86: Revert "KVM: X86: Fix fpu state crash in kvm guest" Sean Christopherson
2020-01-17 19:30 ` [PATCH v2 4/4] KVM: x86: Remove unused ctxt param from emulator's FPU accessors Sean Christopherson
2020-01-18 21:35 ` Paolo Bonzini [this message]
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=b8491683-3717-4dbe-637f-c3daeef08d81@redhat.com \
--to=pbonzini@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=derek@djy.llc \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kernel@najdan.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@thomaslambertz.de \
--cc=riel@surriel.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®