All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Matlack <dmatlack@google.com>
To: kernel test robot <lkp@intel.com>
Cc: kvm@vger.kernel.org, kbuild-all@lists.01.org,
	Ben Gardon <bgardon@google.com>, Joerg Roedel <joro@8bytes.org>,
	Jim Mattson <jmattson@google.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Junaid Shahid <junaids@google.com>,
	Andrew Jones <drjones@redhat.com>
Subject: Re: [PATCH v2 4/6] KVM: x86/mmu: fast_page_fault support for the TDP MMU
Date: Thu, 1 Jul 2021 18:27:28 +0000	[thread overview]
Message-ID: <YN4JEBLXE9vVBjC5@google.com> (raw)
In-Reply-To: <202107011212.FwmbO1RX-lkp@intel.com>

On Thu, Jul 01, 2021 at 12:27:58PM +0800, kernel test robot wrote:
> 
> >> arch/x86/kvm/mmu/mmu.c:3119:6: error: no previous prototype for 'get_last_sptep_lockless' [-Werror=missing-prototypes]
>     3119 | u64 *get_last_sptep_lockless(struct kvm_vcpu *vcpu, gpa_t gpa, u64 *spte)
>          |      ^~~~~~~~~~~~~~~~~~~~~~~

get_last_sptep_lockless should be static. I will include a fix in the
next version of this series.

WARNING: multiple messages have this Message-ID (diff)
From: David Matlack <dmatlack@google.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 4/6] KVM: x86/mmu: fast_page_fault support for the TDP MMU
Date: Thu, 01 Jul 2021 18:27:28 +0000	[thread overview]
Message-ID: <YN4JEBLXE9vVBjC5@google.com> (raw)
In-Reply-To: <202107011212.FwmbO1RX-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 429 bytes --]

On Thu, Jul 01, 2021 at 12:27:58PM +0800, kernel test robot wrote:
> 
> >> arch/x86/kvm/mmu/mmu.c:3119:6: error: no previous prototype for 'get_last_sptep_lockless' [-Werror=missing-prototypes]
>     3119 | u64 *get_last_sptep_lockless(struct kvm_vcpu *vcpu, gpa_t gpa, u64 *spte)
>          |      ^~~~~~~~~~~~~~~~~~~~~~~

get_last_sptep_lockless should be static. I will include a fix in the
next version of this series.

  reply	other threads:[~2021-07-01 18:27 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30 21:47 [PATCH v2 0/6] KVM: x86/mmu: Fast page fault support for the TDP MMU David Matlack
2021-06-30 21:47 ` [PATCH v2 1/6] KVM: x86/mmu: Rename cr2_or_gpa to gpa in fast_page_fault David Matlack
2021-07-12 20:01   ` Sean Christopherson
2021-06-30 21:47 ` [PATCH v2 2/6] KVM: x86/mmu: Fix use of enums in trace_fast_page_fault David Matlack
2021-07-12 16:14   ` Ben Gardon
2021-07-12 18:11     ` David Matlack
2021-07-12 19:53       ` Sean Christopherson
2021-07-12 20:38         ` David Matlack
2021-06-30 21:47 ` [PATCH v2 3/6] KVM: x86/mmu: Make walk_shadow_page_lockless_{begin,end} interoperate with the TDP MMU David Matlack
2021-07-12 17:02   ` Ben Gardon
2021-07-12 18:11     ` David Matlack
2021-07-12 20:20       ` Sean Christopherson
2021-07-12 20:23   ` Sean Christopherson
2021-06-30 21:48 ` [PATCH v2 4/6] KVM: x86/mmu: fast_page_fault support for " David Matlack
2021-07-01  2:54   ` kernel test robot
2021-07-01  2:54     ` kernel test robot
2021-07-01  4:27   ` kernel test robot
2021-07-01  4:27     ` kernel test robot
2021-07-01 18:27     ` David Matlack [this message]
2021-07-01 18:27       ` David Matlack
2021-07-09 18:45   ` David Matlack
2021-07-12 17:49   ` Ben Gardon
2021-07-12 18:20     ` David Matlack
2021-07-12 21:03     ` Sean Christopherson
2021-07-12 21:24       ` David Matlack
2021-06-30 21:48 ` [PATCH v2 5/6] KVM: selftests: Fix missing break in dirty_log_perf_test arg parsing David Matlack
2021-06-30 21:48 ` [PATCH v2 6/6] KVM: selftests: Introduce access_tracking_perf_test David Matlack
2021-07-01  1:15 ` [PATCH v2 0/6] KVM: x86/mmu: Fast page fault support for the TDP MMU Matthew Wilcox
     [not found]   ` <CABgObfZUFWCAvKoxDzGjmksFnwZgbnpX9GuC+nhiVLa-Fhwj6A@mail.gmail.com>
2021-07-01 12:08     ` Matthew Wilcox
2021-07-01 16:50       ` David Matlack
2021-07-01 17:00 ` David Hildenbrand
2021-07-01 22:11   ` David Matlack
2021-07-02  7:53     ` David Hildenbrand

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=YN4JEBLXE9vVBjC5@google.com \
    --to=dmatlack@google.com \
    --cc=bgardon@google.com \
    --cc=drjones@redhat.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=junaids@google.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kvm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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 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.