From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vitaly Kuznetsov Subject: Re: [PATCH v3 3/7] x86/hyper-v: reenlightenment notifications support Date: Tue, 23 Jan 2018 15:07:44 +0100 Message-ID: <877es8brdb.fsf@vitty.brq.redhat.com> References: <20180116182700.1042-4-vkuznets@redhat.com> <201801191841.QZ26OYif%fengguang.wu@intel.com> <87o9lqdt15.fsf@vitty.brq.redhat.com> <877esacd24.fsf@vitty.brq.redhat.com> <87d120bslq.fsf@vitty.brq.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Thomas Gleixner , kbuild test robot , "kbuild-all\@01.org" , "kvm\@vger.kernel.org" , "x86\@kernel.org" , Stephen Hemminger , Radim =?utf-8?B?S3LEjW3DocWZ?= , Haiyang Zhang , "linux-kernel\@vger.kernel.org" , "devel\@linuxdriverproject.org" , Ingo Molnar , Roman Kagan , Andy Lutomirski , "H. Peter Anvin" , Paolo Bonzini , Mohammed Gamal To: "Michael Kelley \(EOSG\)" Return-path: In-Reply-To: (Michael Kelley's message of "Tue, 23 Jan 2018 14:02:07 +0000") Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org "Michael Kelley (EOSG)" writes: > Vitaly Kuznetsov writes: >> >> > "Michael Kelley (EOSG)" writes: >> > >> >> On Fri, 19 Jan 2018, Thomas Gleixner wrote: >> >> >> >>> >> >>> You added '#include ' to mshyperv.h which is included in >> >>> vclock_gettime.c and pulls in other stuff which fails to expand.... >> >> >> >> Is the declaration of hyperv_reenlightenment_intr() even needed in >> >> mshyperv.h? The '#include ' is there for the __irq_entry >> >> annotation on that declaration. There's a declaration of the parallel (and >> >> unannotated) hyperv_vector_handler(), but that looks like a fossil that >> >> isn't needed either. >> >> >> > >> > True, >> > >> > the only need for the declaration in mshyperv.h is to silence "warning: >> > no previous prototype for ‘hyperv_reenlightenment_intr’"; I'm not sure >> > if this actually needs fixing. >> >> It seems we can get away with dropping '__visible' and '__irq_entry' >> qualifiers from 'hyperv_reenlightenment_intr' declaration in mshyperv.h >> while keeping them in hv_init.c for the implementation. This way we can >> avoid the nasty 'no previous prototype' warning and not have to add >> '#include ' to mshyperv.h breaking vdso. > > Where exactly is the 'no previous prototype' warning being generated? It is generated while compiling the implementation in hv_init.c, every non-static function needs a previously defined prototype. -- Vitaly