From: Sean Christopherson <seanjc@google.com>
To: Ben Gardon <bgardon@google.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Shier <pshier@google.com>,
Jim Mattson <jmattson@google.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2 4/4] KVM: x86/mmu: Store the address space ID in the TDP iterator
Date: Mon, 15 Mar 2021 15:23:24 -0700 [thread overview]
Message-ID: <YE/eXP60IVki7csd@google.com> (raw)
In-Reply-To: <20210315182643.2437374-5-bgardon@google.com>
On Mon, Mar 15, 2021, Ben Gardon wrote:
Missing "From: Sean Christopherson <seanjc@google.com>", i.e. the commit in your
local tree needs "git commit --amend --author="Sean Christopherson <seanjc@google.com>".
Alternatively, you could just erase my SOB ;-)
> Store the address space ID in the TDP iterator so that it can be
> retrieved without having to bounce through the root shadow page. This
> streamlines the code and fixes a Sparse warning about not properly using
> rcu_dereference() when grabbing the ID from the root on the fly.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> Signed-off-by: Ben Gardon <bgardon@google.com>
> ---
prev parent reply other threads:[~2021-03-15 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 18:26 [PATCH v2 0/4] Fix RCU warnings in TDP MMU Ben Gardon
2021-03-15 18:26 ` [PATCH v2 1/4] KVM: x86/mmu: Fix RCU usage in handle_removed_tdp_mmu_page Ben Gardon
2021-03-15 18:26 ` [PATCH v2 2/4] KVM: x86/mmu: Fix RCU usage when atomically zapping SPTEs Ben Gardon
2021-03-15 22:26 ` Sean Christopherson
2021-03-15 18:26 ` [PATCH v2 3/4] KVM: x86/mmu: Factor out tdp_iter_return_to_root Ben Gardon
2021-03-15 22:24 ` Sean Christopherson
2021-03-15 18:26 ` [PATCH v2 4/4] KVM: x86/mmu: Store the address space ID in the TDP iterator Ben Gardon
2021-03-15 22:23 ` Sean Christopherson [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=YE/eXP60IVki7csd@google.com \
--to=seanjc@google.com \
--cc=bgardon@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pbonzini@redhat.com \
--cc=pshier@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.