From: Bandan Das <bsd@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: KVM <kvm@vger.kernel.org>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH kvm-unit-tests] cscope: fix database generation
Date: Tue, 19 Apr 2016 13:08:25 -0400 [thread overview]
Message-ID: <jpgd1pl1q7q.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <20160419052510.t2xkdunwjmwvry77@hawk.localdomain> (Andrew Jones's message of "Tue, 19 Apr 2016 07:25:10 +0200")
Andrew Jones <drjones@redhat.com> writes:
> On Mon, Apr 18, 2016 at 07:04:55PM -0400, Bandan Das wrote:
>>
>> The cscope.files that we generate doesn't include all
>> source files that are potentially interesting. We should
>> include all $(ARCH)es and not the just the one configure
>> finds. Moreover, $(ARCH) expands to x86_64 which is not the
>> correct path for x86 sources. Generate cscope.files by searching
>> for all files starting from root.
>
> No thanks :-) I'd rather not get hits for x86 and powerpc when
I don't think that's a good idea. Just because you don't like to
see x86 bits when jumping around in arm code doesn't mean you should
hide all references to a given function. And if the arm code is
segregated enough that there are no common functions, you won't
see them anyway.
> jumping around in arm code. It's true that $(ARCH) expands to
> x86_64, but $(TEST_DIR) expands to x86, so the current find
> does find all x86 source.
Yep, you are right. It still prints a warning message about non-existent
dirs though which needs to be fixed.
>>
>> While we are there, remove the unnecessary sed substitution
>> and modify find to include a few other file name extensions.
>
> I can't remember why the sed was necessary, so it could maybe go
> away. Does it hurt anything though?
No, it doesn't hurt anything. Looks like it was meant to replace
"./" with "". So, I really don't know what it was meant to do
because that substitution doesn't seem right either.
> Looks like you've added .cc, .sh, and .bash. I don't want to mix
> scripts with C source. As for api/*.{cc|hh}, we could change the
> API configure variable to a path ('./api') instead of a boolean,
> and then use it in the current cscope line, along with adding
> both .cc and .hh to the name extension list. (On a side note, we
> should probably create ./api its own makefile and look into
> getting it to work with other architectures at some point).
Ok, this I agree with. We can separate the scripts from the c sources
and probably have a variable that sets adding them. But please let's
not make it difficult to write arm/powerpc tests just because someone's on
x86 :)
> Thanks,
> drew
>
>>
>> Signed-off-by: Bandan Das <bsd@redhat.com>
>> ---
>> Makefile | 9 +++------
>> configure | 2 ++
>> 2 files changed, 5 insertions(+), 6 deletions(-)
>>
>> diff --git a/Makefile b/Makefile
>> index 5d7506e..458d0f0 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -92,11 +92,8 @@ distclean: clean libfdt_clean
>> $(RM) lib/asm config.mak $(TEST_DIR)-run test.log msr.out cscope.*
>> $(RM) -r tests
>>
>> -cscope: cscope_dirs = lib lib/libfdt lib/linux
>> -cscope: cscope_dirs += lib/$(ARCH)/asm lib/$(TEST_DIR)/asm lib/asm-generic
>> -cscope: cscope_dirs += $(TEST_DIR) lib/$(TEST_DIR) lib/$(ARCH)
>> cscope:
>> - $(RM) ./cscope.*
>> - find -L $(cscope_dirs) -maxdepth 1 \
>> - -name '*.[chsS]' -print | sed 's,^\./,,' | sort -u > ./cscope.files
>> + $(RM) $(SRCDIR)/cscope.*
>> + find -L $(SRCDIR) -maxdepth 3 \
>> + -regex '.*\.\(c\|h\|cc\|S\|sh\|bash\|s\)$$' -print | sort -u > ./cscope.files
>> cscope -bk
>> diff --git a/configure b/configure
>> index ba6c55b..3153fb9 100755
>> --- a/configure
>> +++ b/configure
>> @@ -12,6 +12,7 @@ host=$arch
>> cross_prefix=
>> endian=""
>> pretty_print_stacks=yes
>> +srcdir=`pwd`
>>
>> usage() {
>> cat <<-EOF
>> @@ -159,4 +160,5 @@ TEST_DIR=$testdir
>> FIRMWARE=$firmware
>> ENDIAN=$endian
>> PRETTY_PRINT_STACKS=$pretty_print_stacks
>> +SRCDIR=$srcdir
>> EOF
>> --
>> 2.5.5
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-19 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 23:04 [PATCH kvm-unit-tests] cscope: fix database generation Bandan Das
2016-04-19 5:25 ` Andrew Jones
2016-04-19 17:08 ` Bandan Das [this message]
2016-04-19 18:38 ` Radim Krčmář
2016-04-19 18:58 ` Bandan Das
2016-04-19 19:22 ` Radim Krčmář
2016-04-19 19:44 ` Bandan Das
2016-04-20 8:43 ` Andrew Jones
2016-04-20 14:31 ` Bandan Das
2016-04-20 14:45 ` Andrew Jones
2016-05-10 13:55 ` Paolo Bonzini
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=jpgd1pl1q7q.fsf@linux.bootlegged.copy \
--to=bsd@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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.