[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Discussion on unexpected behavior of ARINC653 scheduler
- To: Juergen Gross <jgross@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: "Choi, Anderson" <Anderson.Choi@xxxxxxxxxx>
- Date: Thu, 13 Mar 2025 09:27:54 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=boeing.com; dmarc=pass action=none header.from=boeing.com; dkim=pass header.d=boeing.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector5401; 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=1Zra/gtpCyFy2nbulS28Cl1sl68BEoSNougHHCrp1DY=; b=mv29O+25hM0aJOze91cJ4rQuw+7w5vy/TLnJjNW7N2OAJ4re1nRU5QuxKJbJD2WWWrcIcbQNWfOpPdrGtUkbEMqgQY1VEQnbcOrb5dh5R8Q5iS5DqzXtfZUc7iWz7kqnEvPqwSOH+i80GoMHYN4JzqNKR2mUAsjWIDdXCBUvjjgpmMawBzgfkSPfnLIGvvOFeGe2ixasotdAmc9SA82XN0poB4Ccxc55fk5gDRAAJptMFnsB1lY9gqMO0P7gw2UzmDDrBWqXRDVcqstT+vLcfK6NFRk6C0hdIi48bb5hbTF1EqadIZGSzE+kk7CqNTNBUk+HWHnNtduHPuCT+aRPLQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector5401; d=microsoft.com; cv=none; b=ImFHzwZFBb688j+beXu9WQQ1j9bow0zQaTBrJ/1xo5Qw2t4ys/sEMA6ser5WNqZusTHL/XST8q/H2sr1e0YIdO14CWfWI8hpBU/X34S3VcP+Et6Q6E8ycaCENao69xFW4yL5Pp8Ps/0T3S43uza+VxvYvKcujib9/9dQPGtcqoUVREJRAwP24nzU12Q9R+YF5nsWkEb/rjY+yt5sS/12+cPt/UO/4pYCOzw70Ft5gemn3ijxSPav2UBtNhY+gDz+8zk8Yao0GUoaaug2/AVYxpt2/t39aJuHATdu7srQuTeKT9pEkjqsCie3WsO5b8lcTXpjSY6IlWRn5X+C8fgN8g==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=boeing.com;
- Cc: "nathan.studer@xxxxxxxxxxxxxxx" <nathan.studer@xxxxxxxxxxxxxxx>, "stewart@xxxxxxx" <stewart@xxxxxxx>, "Weber (US), Matthew L" <matthew.l.weber3@xxxxxxxxxx>, "Whitehead (US), Joshua C" <joshua.c.whitehead@xxxxxxxxxx>
- Delivery-date: Thu, 13 Mar 2025 09:28:20 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Thread-index: AduT5GPU8k+LryI1RQGgVtY2Yt6hPwAA8CSAAAP0WWA=
- Thread-topic: Discussion on unexpected behavior of ARINC653 scheduler
Juergen,
> On 13.03.25 07:51, Choi, Anderson wrote:
>> We are observing an incorrect or unexpected behavior with ARINC653
> scheduler when we set up multiple ARINC653 CPU pools and assign a
> different number of domains to each CPU pool.
>
> ...
>
>> It seems there's a corner condition in using the global variables
>> "sched_index"
> and "next_switch_time" when multiple ARINC653 cpupools are running on
> different physical CPUs
>>
>> The variables sched_index and next_switch_time are defined as static
>> at xen/common/sched/arinc653.c as shown below.
>>
>> static void cf_check
>> a653sched_do_schedule(
>> const struct scheduler *ops, struct sched_unit *prev, s_time_t
>> now, bool tasklet_work_scheduled) { struct sched_unit *new_task =
>> NULL; static unsigned int sched_index = 0; <== static s_time_t
>> next_switch_time; <==
>
> Thanks for the report!
>
> Could you please verify the attached patch is fixing your problem?
>
> And please tell me whether adding you as "Reported-by:" is fine with you!
>
> Juergen
Thanks for the quick patch. I have verified the patch fixes the issue and I can
see domains are running at the programmed interval.
And I am totally fine with "Reported-by".
May I know when you think it would be mainlined? And will it be applied to all
branches, like 4.19 and 4.20?
Regards,
Anderson
|
