From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: ian.jackson@citrix.com, Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
george.dunlap@citrix.com,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: SRSL People... [PATCH v11 0/9] misc safety certification fixes
Date: Fri, 08 Mar 2019 08:46:12 -0700 [thread overview]
Message-ID: <5C828E44020000780021CBB9@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <d0793749-a837-b094-d3b0-8a148bfff400@citrix.com>
>>> On 08.03.19 at 16:26, <andrew.cooper3@citrix.com> wrote:
> On 05/03/2019 22:38, Stefano Stabellini wrote:
>> Hi all,
>>
>> This version of the series makes use of the macro suggested by Jan with
>> few modifications. See each patch for a description of the changes.
>>
>> The following changes since commit 808cff4c2af66afd61973451aeb7e708732abf90:
>>
>> sched/credit2: remove stale comment (2019-01-09 15:46:05 +0100)
>>
>> are available in the git repository at:
>>
>> http://xenbits.xenproject.org/git-http/people/sstabellini/xen-unstable.git
> certifications-11
>>
>> for you to fetch changes up to 26fb02b5ae59b48b51ca788be91510d8df48ab0a:
>>
>> xen: explicit casts when DECLARE_BOUNDS cannot be used (2019-03-05
> 14:29:51 -0800)
>>
>> ----------------------------------------------------------------
>> Stefano Stabellini (9):
>> xen: use __UINTPTR_TYPE__ for uintptr_t
>> xen: introduce ptrdiff_t
>> xen: introduce DECLARE_BOUNDS
>> xen/arm: use DECLARE_BOUNDS as required
>> xen/x86: use DECLARE_BOUNDS as required
>> xen/common: use DECLARE_BOUNDS as required
>> xen: use DECLARE_BOUNDS as required
>> xen: use DECLARE_BOUNDS in alternative.c
>> xen: explicit casts when DECLARE_BOUNDS cannot be used
>
> Seriously. Everyone take a step back from their keyboards and apply
> some common sense.
>
> This argument has gone on far beyond the only answer which matters. WTF
> is still continuing for? (This is a rhetorical question - I don't expect
> an answer.)
>
>
> The rational for this series is to satisfy MISRA. MISRA have said in no
> uncertain terms that all of these tricks are unacceptable, and have
> identified the one acceptable option. By not doing what MISRA said,
> this series doesn't move Xen any closer to passing certification.
Iirc they said to use casts in a central place. Am I misremembering?
Because that's what the series does.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-03-08 15:46 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 22:38 [PATCH v11 0/9] misc safety certification fixes Stefano Stabellini
2019-03-05 22:38 ` [PATCH v11 1/9] xen: use __UINTPTR_TYPE__ for uintptr_t Stefano Stabellini
2019-03-06 7:47 ` Jan Beulich
2019-03-06 21:16 ` Stefano Stabellini
2019-03-07 8:29 ` Jan Beulich
2019-03-07 15:43 ` Ian Jackson
2019-03-08 7:23 ` Jan Beulich
2019-03-08 14:18 ` Andrew Cooper
2019-03-08 15:19 ` Ian Jackson
2019-03-05 22:38 ` [PATCH v11 2/9] xen: introduce ptrdiff_t Stefano Stabellini
2019-03-05 22:38 ` [PATCH v11 3/9] xen: introduce DECLARE_BOUNDS Stefano Stabellini
2019-03-06 15:24 ` Jan Beulich
2019-03-06 20:55 ` Stefano Stabellini
2019-03-07 8:39 ` Jan Beulich
2019-03-07 14:16 ` Ian Jackson
2019-03-08 8:15 ` Jan Beulich
2019-03-08 15:31 ` Ian Jackson
2019-03-05 22:38 ` [PATCH v11 4/9] xen/arm: use DECLARE_BOUNDS as required Stefano Stabellini
2019-03-05 22:38 ` [PATCH v11 5/9] xen/x86: " Stefano Stabellini
2019-03-06 15:33 ` Jan Beulich
2019-03-06 21:05 ` Stefano Stabellini
2019-03-07 8:40 ` Jan Beulich
2019-03-07 14:02 ` Ian Jackson
2019-03-07 14:42 ` George Dunlap
2019-03-08 8:46 ` Jan Beulich
2019-03-08 8:55 ` Juergen Gross
2019-03-08 15:33 ` Ian Jackson
2019-03-06 15:48 ` Jan Beulich
2019-03-06 21:38 ` Stefano Stabellini
2019-03-07 8:50 ` Jan Beulich
2019-03-07 14:43 ` Ian Jackson
2019-03-08 8:22 ` Jan Beulich
2019-03-08 15:36 ` Ian Jackson
2019-03-08 15:57 ` Jan Beulich
2019-03-07 14:00 ` Ian Jackson
2019-03-08 15:43 ` Ian Jackson
2019-03-08 15:49 ` Jan Beulich
2019-03-05 22:38 ` [PATCH v11 6/9] xen/common: " Stefano Stabellini
2019-03-06 15:37 ` Jan Beulich
2019-03-06 21:08 ` Stefano Stabellini
2019-03-05 22:38 ` [PATCH v11 7/9] xen: " Stefano Stabellini
2019-03-05 22:38 ` [PATCH v11 8/9] xen: use DECLARE_BOUNDS in alternative.c Stefano Stabellini
2019-03-06 16:35 ` Jan Beulich
2019-03-06 21:38 ` Stefano Stabellini
2019-03-05 22:38 ` [PATCH v11 9/9] xen: explicit casts when DECLARE_BOUNDS cannot be used Stefano Stabellini
2019-03-07 11:40 ` Jan Beulich
2019-03-07 15:25 ` [PATCH v11 9/9] xen: explicit casts when DECLARE_BOUNDS cannot be used [and 1 more messages] Ian Jackson
2019-03-07 22:55 ` Stefano Stabellini
2019-03-08 15:39 ` [PATCH v11 9/9] xen: explicit casts when DECLARE_BOUNDS cannot be used [and 1 more messages] " Ian Jackson
2019-03-08 8:28 ` [PATCH v11 9/9] xen: explicit casts when DECLARE_BOUNDS cannot be used " Jan Beulich
2019-03-08 15:26 ` SRSL People... [PATCH v11 0/9] misc safety certification fixes Andrew Cooper
2019-03-08 15:44 ` Ian Jackson
2019-03-08 15:46 ` Jan Beulich [this message]
2019-03-08 20:14 ` Stefano Stabellini
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=5C828E44020000780021CBB9@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=julien.grall@arm.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 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.