All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>, 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 21:22:28 +0200	[thread overview]
Message-ID: <20160419192228.GA25335@potion> (raw)
In-Reply-To: <jpgk2jt8lyr.fsf@linux.bootlegged.copy>

2016-04-19 14:58-0400, Bandan Das:
> Radim Krčmář <rkrcmar@redhat.com> writes:
>> 2016-04-19 13:08-0400, Bandan Das:
>>> 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. 
>>> [...]                                               But please let's
>>> not make it difficult to write arm/powerpc tests just because someone's on
>>> x86 :)
>>
>> In the kernel, environment can override configuration, so you'd do
>>
>>   % ARCH=arm make cscope
>>
>> and it doesn't matter what arch is being compiled.  I think this would
>> be a better solution for kvm-unit-tests too.
>>
>> I agree with Drew that other arches would mostly clutter searches if
>> they were included by default, but we can also add a rule in case
> 
> Since you mentioned the kernel, it looks like both the kernel/qemu
> include all by default which makes sense to me.

qemu does, kernel doesn't (e.g. search for sys_sigreturn).

>                                                 As I mentioned above,
> you definitely don't want to modify a common library function only to
> realize that you forgot to modify all sites. Looking at all sites adds
> visibility, not introduce clutter.
> 
>> indexing all arches is desired (like when changing the prototype of some
>> generic function?).
> 
> kvm-unit-tests is small enough that this can be the default.

I don't see a reason to add results that we'd then have to mentally
filter regardless of their amount.

>                                                              That said, this
> is a trivial change and I am happy to live with it in my local branch. (Unless
> ofcourse both Linux and Qemu decide to make this default behavior too!)

I think we'll agree on something that can be merged -- the present
situation is bad.

For me, "include all" is a matter of `cscope -bk **/*.[chS]` and getting
only arch-specific cscope is harder, so having an option to generate
cscope just for target arch would be nice.

(I don't care about the default much, `ARCH=$sth make cscope` is easy
 to type if the default included all.)

  reply	other threads:[~2016-04-19 19:22 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
2016-04-19 18:38     ` Radim Krčmář
2016-04-19 18:58       ` Bandan Das
2016-04-19 19:22         ` Radim Krčmář [this message]
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=20160419192228.GA25335@potion \
    --to=rkrcmar@redhat.com \
    --cc=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.