Re: [Xen-devel] [COVERITY ACCESS] for Embedded/Automotive team

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 22/11/16 11:55, Lars Kurth wrote:
>
> On 22/11/2016 11:51, "Julien Grall" <julien.grall@xxxxxxx> wrote:
>
>> Hi Lars,
>>
>> On 19/11/16 16:53, Lars Kurth wrote:
>>> On 18/11/2016 20:55, "Julien Grall" <julien.grall@xxxxxxx> wrote:
>>>> Coverity has been proven useful on x86 to catch some bugs. A such
>>>> things
>>>> would be nice for ARM too. Is there anything we can do to get coverity
>>>> testing ARM? (CC Lars).
>>> Coverity does static code analysis. It analyses our entire tree,
>>> although
>>> I don't know whether we updated it to point it to new repos such as the
>>> mini-os one.
>> I thought coverity was hooking into the build system by replacing the
>> compiler, right?
>>
>> If so, how does coverity analyze xen/arch/arm?
> I guess that is a question for someone else who is more familiar with the
> set-up. But there shouldn't be any technical reason which prevents
> Coverity scan from running on any CPU specific code.

There is no technical problem with using Coverity for ARM.  Coverity, as
a product, is capable of doing this.

The problem is that Coverity Scan only offers us one stream for the Xen
Project, and we cannot mix architectures within a single stream.  (Not
that we physically can't, but that the change tracking of defects would
be meaningless).

The only way we could scan for ARM is if we could be given multiple
different streams (one per arch) to use, and Coverity have already said
no to this request.  This is a politics problem, not a technical problem.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel