xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Artem Mygaiev <artem_mygaiev@epam.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Lars Kurth <lars.kurth@citrix.com>,
	Julien Grall <julien.grall@arm.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Artem Mygaiev <joculator@gmail.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [COVERITY ACCESS] for Embedded/Automotive team
Date: Tue, 22 Nov 2016 15:54:56 +0200	[thread overview]
Message-ID: <3fc1366f-6ab7-a14f-ea9f-761e82f85f5d@epam.com> (raw)
In-Reply-To: <5f1aae1b-15e7-fd1b-2047-21372332d960@citrix.com>

On 22.11.16 15:42, Andrew Cooper wrote:
> On 22/11/16 11:55, Lars Kurth wrote:
>> On 22/11/2016 11:51, "Julien Grall" <julien.grall@arm.com> wrote:
>>
>>> Hi Lars,
>>>
>>> On 19/11/16 16:53, Lars Kurth wrote:
>>>> On 18/11/2016 20:55, "Julien Grall" <julien.grall@arm.com> 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, I understand, thanks.

Would it be still possible to get Scan model files for us? We would like
to update them for use with ARM. BTW, we could set up ARM build Coverity
Scan with GitHub/Travis only limited by amount of runs per week
(depending on number LOC number).

BR, Artem


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

  reply	other threads:[~2016-11-22 13:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 13:36 [COVERITY ACCESS] for Embedded/Automotive team Artem Mygaiev
2016-11-18 13:56 ` Andrew Cooper
2016-11-18 15:28   ` Konrad Rzeszutek Wilk
2016-11-18 20:55     ` Julien Grall
2016-11-19 16:53       ` Lars Kurth
2016-11-22 11:51         ` Julien Grall
2016-11-22 11:55           ` Lars Kurth
2016-11-22 13:06             ` Artem Mygaiev
2016-11-22 13:42             ` Andrew Cooper
2016-11-22 13:54               ` Artem Mygaiev [this message]
2016-11-28 10:27                 ` Lars Kurth
2016-11-28 11:01                   ` Artem Mygaiev
2016-11-29 14:21                     ` Artem Mygaiev
2016-11-29 14:27                       ` Julien Grall
2016-11-29 15:04                         ` Lars Kurth
2016-11-30 11:14                           ` Artem Mygaiev
2016-11-29 15:09                         ` Artem Mygaiev
2016-11-29 16:12                           ` Julien Grall
2016-11-29 18:19                           ` Stefano Stabellini
2016-11-30 11:15                             ` Artem Mygaiev
2016-11-30 19:10                               ` Stefano Stabellini
2016-11-30 19:21                           ` Andrew Cooper
2016-12-01 13:44                             ` Artem Mygaiev
2016-11-22  9:00       ` Artem Mygaiev

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=3fc1366f-6ab7-a14f-ea9f-761e82f85f5d@epam.com \
    --to=artem_mygaiev@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=joculator@gmail.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lars.kurth@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).