[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 0/2] Final series to make Arm MISRA allcode green


  • To: "Orzel, Michal" <michal.orzel@xxxxxxx>, Nicola Vetrini <nicola.vetrini@xxxxxxxxxxx>
  • From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • Date: Wed, 8 Apr 2026 11:42:19 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=grxqa1yLMqOmik0XxpmDAOQUuYcxU2vGrAB6N1h61z8=; b=zRWlZ3X3RwDdZWUTXZpW4km0+sMe3k9itWUUybV9Fr2BKdm70FGAMbgbMu4rh2mELUafP6beP/GGBQeLq9RcKTEMf6K1I5S3CbDa0CWMXWk8whNWBX5R+F6+WIduYiaFdkZ7WN1X0F4yVPszmvfyHdD8XBnHCHkJW2wt3TzPfPbsimsc2g8+wAMa0nHXY62MCdD1VJfVH3uNY9kkhaf0YWp9KgEh6joXjUX8xfaF2gnbdKEISCHY8ZJnAvZX/skrCOq4m0gotymjwza1pnSDZrVa4OOaEX0gm9mXrFq2y5SarqxECDUyCACClPxQ9MU2E0+URyutYXlWuQNOku8TAg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=vM1OICFmyp+uPZWpAxQqdLCDyugWCFbb6hBMyifO6gkF7nycnrYVkpU+4ZvvJZf43PMZmUgOuK3GVkifWabnwBb4oDdt5cJ2oCZAuMLDPk7Bj1VqVEU1lpsZyCNhBScYz3Sn5DO060maPN7wCAC4B5I888t+LwLzb5J3zF3BygYOiMrBJd79Er0MvcjJflBBR92SwXDTbHKh35slE3rmyN1X/kJMPye1OSKj0whstZS91H2FhMUf61+skNKIhN7o2DlrHwvQ08D0y4lbMRLyyh9TrZSO2ISkQdjA/WXjK/ZHxAWDvvYwo1PGVpfaMi1NHV/upQv46llkYTi11xv7ag==
  • Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=selector1 header.d=citrix.com header.i="@citrix.com" header.h="From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck"
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, Julien Grall <julien@xxxxxxx>, Rahul Singh <rahul.singh@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Bertrand Marquis <bertrand.marquis@xxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>
  • Delivery-date: Wed, 08 Apr 2026 10:53:36 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 08/04/2026 11:36 am, Orzel, Michal wrote:
>
> On 08/04/2026 12:21, Nicola Vetrini wrote:
>> On 2026-04-08 11:51, Andrew Cooper wrote:
>>> On 08/04/2026 10:46 am, Nicola Vetrini wrote:
>>>> On 2026-04-08 11:22, Andrew Cooper wrote:
>>>>> On 07/04/2026 11:34 am, Michal Orzel wrote:
>>>>>> No more regressions for clean guidelines:
>>>>>> https://gitlab.com/xen-project/people/morzel/xen/-/pipelines/2433943072
>>>>>>
>>>>>> Michal Orzel (2):
>>>>>>   iommu/arm: smmu: Fix variable shadowing
>>>>>>   iommu/arm: ipmmu-vmsa: Fix variable shadowing
>>>>>>
>>>>>>  xen/drivers/passthrough/arm/ipmmu-vmsa.c | 6 ++----
>>>>>>  xen/drivers/passthrough/arm/smmu.c       | 7 +++----
>>>>>>  2 files changed, 5 insertions(+), 8 deletions(-)
>>>>> If all the violations are fixed, should this test be made blocking?
>>>>>
>>>>> ~Andrew
>>>> Only if they are also clean on x86; otherwise an arm-specific list of
>>>> clean rules should be made (probably better). @Michal what do you 
>>>> prefer?
>>>>
>>> All I'm suggesting is this:
>>>
>>> xen.git/xen$ git diff
>>> diff --git a/automation/gitlab-ci/analyze.yaml 
>>> b/automation/gitlab-ci/analyze.yaml
>>> index 4e9af9d60224..f01798c5dee6 100644
>>> --- a/automation/gitlab-ci/analyze.yaml
>>> +++ b/automation/gitlab-ci/analyze.yaml
>>> @@ -149,7 +149,7 @@ eclair-ARM64-allcode:
>>>        CONFIG_STACK_PROTECTOR=y
>>>        CONFIG_UNSUPPORTED=y
>>>        CONFIG_VM_EVENT=y
>>> -  allow_failure: true
>>> +  allow_failure: false
>>>  
>>>  eclair-ARM64-testing:
>>>    extends: eclair-ARM64-allcode
>>>
>>>
>>> so regressions become blocking.
>>>
>>> ~Andrew
>> Ah, yes, indeed. I didn't look at the patches but given the diff it 
>> makes sense
> In general that's a good idea and something I had in mind. That said, we will
> likely be expanding the list of enabled features there as soon as one arrives.
> What should we do in that case? Make sure that before adding new =y option, 
> the
> allcode passes in our Xen fork?

New code could be clean as it goes in.  At this point, it's not
interestingly different from "does it compile" as a prerequisite.

~Andrew



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.