From: "Furkan Çalışkan" <frn1furkan10@gmail.com>
To: "Jan Beulich" <jbeulich@suse.com>, "Jürgen Groß" <jgross@suse.com>
Cc: andrew.cooper3@citrix.com, roger@xenproject.org,
dfaggioli@suse.com, anthony.perard@vates.tech, julien@xen.org,
sstabellini@kernel.org, gwd@xenproject.org, enr0n@ubuntu.com,
michal.orzel@amd.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH 1/5] xen/sched: rtds: add global-EDF utilization admission control
Date: Mon, 14 Sep 2026 13:34:50 +0300 [thread overview]
Message-ID: <85e6a89a-edc4-4d2e-9d75-5933af44f7fc@gmail.com> (raw)
In-Reply-To: <67395a7d-ccd7-41a3-a925-8679e5d37911@suse.com>
On 9/14/26 12:45, Jan Beulich wrote:
> On 14.09.2026 11:33, Jürgen Groß wrote:
>> On 14.09.26 11:13, Jan Beulich wrote:
>>> On 14.09.2026 11:10, Juergen Gross wrote:
>>>> On 26.08.26 06:57, Furkan Caliskan wrote:
>>>>> @@ -892,8 +983,19 @@ rt_alloc_udata(const struct scheduler *ops, struct sched_unit *unit, void *dd)
>>>>> static void cf_check
>>>>> rt_free_udata(const struct scheduler *ops, void *priv)
>>>>> {
>>>>> + struct rt_private *prv = rt_priv(ops);
>>>>> struct rt_unit *svc = priv;
>>>>>
>>>>> + if ( svc && !is_idle_unit(svc->unit) )
>>>>> + {
>>>>> + unsigned long flags;
>>>>> +
>>>>> + spin_lock_irqsave(&prv->lock, flags);
>>>>> + rt_admission_test(prv, svc->unit->domain,
>>>>> + svc->period, svc->budget, 0, 0);
>>>>
>>>> This use case clearly shows you are not only testing. :-)
>>>
>>> Yet at the same time ignoring possible errors.
>>
>> I don't see how this could happen, as new_period and new_budget are both 0 here.
>
> Okay, that's simply entirely invisible here. So before freeing the two
> items are somehow zeroed?
>
> Jan
Can you please clarify what do you mean here?
Furkan
next prev parent reply other threads:[~2026-09-14 10:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 4:57 [PATCH 0/5] xen/sched: rtds: add per-cpupool admission control Furkan Caliskan
2026-08-26 4:57 ` [PATCH 1/5] xen/sched: rtds: add global-EDF utilization " Furkan Caliskan
2026-09-14 9:10 ` Juergen Gross
2026-09-14 9:13 ` Jan Beulich
2026-09-14 9:33 ` Jürgen Groß
2026-09-14 9:45 ` Jan Beulich
2026-09-14 10:34 ` Furkan Çalışkan [this message]
2026-09-14 11:29 ` Jan Beulich
2026-09-14 10:30 ` Furkan Çalışkan
2026-09-14 11:15 ` Furkan Çalışkan
2026-08-26 4:57 ` [PATCH 2/5] xen/sched: rtds: enforce admission control in xl sched-rtds Furkan Caliskan
2026-09-14 9:16 ` Juergen Gross
2026-09-14 9:21 ` Jan Beulich
2026-09-14 10:40 ` Furkan Çalışkan
2026-09-18 7:46 ` Jürgen Groß
2026-09-18 7:51 ` Furkan Çalışkan
2026-08-26 4:57 ` [PATCH 3/5] xen/sched: rtds: report utilization and cap via debug key Furkan Caliskan
2026-09-14 9:18 ` Juergen Gross
2026-08-26 4:57 ` [PATCH 4/5] xen/sched: rtds: make admission control cpupool-wide toggleable Furkan Caliskan
2026-08-26 6:14 ` Jan Beulich
2026-09-14 10:45 ` Furkan Çalışkan
2026-09-14 9:24 ` Juergen Gross
2026-08-26 4:57 ` [PATCH 5/5] tools: expose admission control toggle via xl sched-rtds Furkan Caliskan
2026-09-11 12:25 ` [PATCH 0/5] xen/sched: rtds: add per-cpupool admission control Furkan Çalışkan
2026-09-11 12:57 ` Jürgen Groß
2026-09-11 13:05 ` Furkan Çalışkan
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=85e6a89a-edc4-4d2e-9d75-5933af44f7fc@gmail.com \
--to=frn1furkan10@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dfaggioli@suse.com \
--cc=enr0n@ubuntu.com \
--cc=gwd@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger@xenproject.org \
--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.