kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Stephen Hemminger" <sthemmin@microsoft.com>,
	kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
	"Haiyang Zhang" <haiyangz@microsoft.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>,
	"Ingo Molnar" <mingo@redhat.com>,
	kbuild-all@01.org, "Andy Lutomirski" <luto@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	devel@linuxdriverproject.org,
	"Mohammed Gamal" <mmorsy@redhat.com>,
	"Roman Kagan" <rkagan@virtuozzo.com>
Subject: Re: [PATCH v3 3/7] x86/hyper-v: reenlightenment notifications support
Date: Mon, 22 Jan 2018 11:41:43 +0100	[thread overview]
Message-ID: <87shaych08.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1801200846210.1998@nanos> (Thomas Gleixner's message of "Sat, 20 Jan 2018 08:48:07 +0100 (CET)")

Thomas Gleixner <tglx@linutronix.de> writes:

> On Fri, 19 Jan 2018, Vitaly Kuznetsov wrote:
>> kbuild test robot <lkp@intel.com> writes:
>> 
>> > Hi Vitaly,
>> >
>> > Thank you for the patch! Perhaps something to improve:
>> >
>> > [auto build test WARNING on tip/auto-latest]
>> > [also build test WARNING on v4.15-rc8 next-20180118]
>> > [cannot apply to tip/x86/core kvm/linux-next]
>> > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>> >
>> > url:    https://github.com/0day-ci/linux/commits/Vitaly-Kuznetsov/x86-kvm-hyperv-stable-clocksorce-for-L2-guests-when-running-nested-KVM-on-Hyper-V/20180119-160814
>> > config: x86_64-allmodconfig (attached as .config)
>> > compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
>> > reproduce:
>> >         # save the attached .config to linux build tree
>> >         make ARCH=x86_64 
>> >
>> > All warnings (new ones prefixed by >>):
>> >
>> >    In file included from include/linux/kasan.h:17:0,
>> >                     from include/linux/slab.h:129,
>> >                     from include/linux/irq.h:26,
>> >                     from arch/x86/include/asm/hardirq.h:6,
>> >                     from include/linux/hardirq.h:9,
>> >                     from include/linux/interrupt.h:13,
>> >                     from arch/x86/include/asm/mshyperv.h:8,
>> >                     from arch/x86//entry/vdso/vdso32/../vclock_gettime.c:20,
>> >                     from arch/x86//entry/vdso/vdso32/vclock_gettime.c:33:
>> >    arch/x86/include/asm/pgtable.h: In function 'clone_pgd_range':
>> >    arch/x86/include/asm/pgtable.h:1129:9: error: implicit declaration of function 'kernel_to_user_pgdp'; did you mean 'u64_to_user_ptr'? [-Werror=implicit-function-declaration]
>> >      memcpy(kernel_to_user_pgdp(dst), kernel_to_user_pgdp(src),
>> >             ^~~~~~~~~~~~~~~~~~~
>> 
>> Sorry but I'm failing to see how this (and all the rest) is related to
>> my patch ...
>
> You added '#include <linux/interrupt.h>' to mshyperv.h which is included in
> vclock_gettime.c and pulls in other stuff which fails to expand....
>

Oh, right, thanks! I'll see what can be done.

-- 
  Vitaly

  parent reply	other threads:[~2018-01-22 10:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 18:26 [PATCH v3 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V Vitaly Kuznetsov
2018-01-16 18:26 ` [PATCH v3 1/7] x86/hyper-v: check for required priviliges in hyperv_init() Vitaly Kuznetsov
2018-01-16 18:26 ` [PATCH v3 2/7] x86/hyper-v: add a function to read both TSC and TSC page value simulateneously Vitaly Kuznetsov
2018-01-16 18:26 ` [PATCH v3 3/7] x86/hyper-v: reenlightenment notifications support Vitaly Kuznetsov
2018-01-16 18:33   ` Thomas Gleixner
2018-01-19 10:21   ` kbuild test robot
2018-01-19 10:47     ` Vitaly Kuznetsov
2018-01-20  7:48       ` Thomas Gleixner
2018-01-22  1:22         ` Michael Kelley (EOSG)
2018-01-22 12:06           ` Vitaly Kuznetsov
2018-01-23 13:41             ` Vitaly Kuznetsov
2018-01-23 14:02               ` Michael Kelley (EOSG)
2018-01-23 14:07                 ` Vitaly Kuznetsov
2018-01-22 10:41         ` Vitaly Kuznetsov [this message]
2018-01-19 11:11   ` kbuild test robot
2018-01-16 18:26 ` [PATCH v3 4/7] x86/hyper-v: redirect reenlightment notifications on CPU offlining Vitaly Kuznetsov
2018-01-16 18:31   ` Thomas Gleixner
2018-01-16 18:26 ` [PATCH v3 5/7] x86/irq: Count Hyper-V reenlightenment interrupts Vitaly Kuznetsov
2018-01-16 18:32   ` Thomas Gleixner
2018-01-16 18:26 ` [PATCH v3 6/7] x86/kvm: pass stable clocksource to guests when running nested on Hyper-V Vitaly Kuznetsov
2018-01-16 18:27 ` [PATCH v3 7/7] x86/kvm: support Hyper-V reenlightenment Vitaly Kuznetsov
2018-01-19 11:15   ` [RFC PATCH] x86/kvm: kvm_hyperv_tsc_notifier() can be static kbuild test robot
2018-01-19 11:15   ` [PATCH v3 7/7] x86/kvm: support Hyper-V reenlightenment kbuild test robot

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=87shaych08.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=Michael.H.Kelley@microsoft.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=mmorsy@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkagan@virtuozzo.com \
    --cc=rkrcmar@redhat.com \
    --cc=sthemmin@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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).