[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <715c49ec-d2a8-45cb-8ace-c6b1b4b8f978@nvidia.com>
Date: Tue, 29 Sep 2020 11:59:55 -0700
From: John Hubbard <jhubbard@...dia.com>
To: Jason Gunthorpe <jgg@...pe.ca>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Jonathan Corbet <corbet@....net>,
Jérôme Glisse <jglisse@...hat.com>,
Ralph Campbell <rcampbell@...dia.com>,
Shuah Khan <shuah@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
<linux-kselftest@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<linux-s390@...r.kernel.org>
Subject: Re: [PATCH 2/8] selftests/vm: use a common gup_test.h
On 9/29/20 10:55 AM, Jason Gunthorpe wrote:
> On Tue, Sep 29, 2020 at 10:44:31AM -0700, John Hubbard wrote:
>> On 9/29/20 9:35 AM, Jason Gunthorpe wrote:
>>> On Mon, Sep 28, 2020 at 01:10:24PM -0700, John Hubbard wrote:
>>>> On 9/28/20 5:57 AM, Jason Gunthorpe wrote:
>>>>> On Sun, Sep 27, 2020 at 11:21:53PM -0700, John Hubbard wrote:
...
>> I don't see any "gcc -m" type of dependency generation pass happening
>> in this relatively simple Make system.
>
> It happens with -MD, all the deps are stored in files like mm/.init-mm.o.cmd
> and sucked into the build.
You are thinking of kbuild. This is not kbuild. There are no such artifacts
being generated.
>> And so, without including an explicit header file dependency (at
>> least, that's the simplest way), changes to gup_test.h are not
>> detected.
>
> Shouldn't be
>
>> Both the Makefile code and the observed behavior back this up. (I
>> expect that this is because there is less use of header files in
>> this area, because most unit tests are self-contained within a
>> single .c file.)
>
> Something else is very wrong then.
>
Not really, it's just a less-cabable system than kbuild.
thanks,
--
John Hubbard
NVIDIA
Powered by blists - more mailing lists