From: Jan Kiszka <jan.kiszka@siemens.com>
To: Florian Bezdeka <florian.bezdeka@siemens.com>,
Xenomai <xenomai@lists.linux.dev>,
Aaron Marcher <aaron@sigma-star.at>,
Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH] debian: Enable lores clock by default
Date: Wed, 9 Aug 2023 16:02:01 +0200 [thread overview]
Message-ID: <c0b1faa1-d791-4245-bbd9-d0156032d9cf@siemens.com> (raw)
In-Reply-To: <a4bfd7f4abdb40bd676030862b6e070c804d6b6c.camel@siemens.com>
On 09.08.23 15:54, Florian Bezdeka wrote:
> On Wed, 2023-08-09 at 15:32 +0200, Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Having the goal to be generically usable, the debian package should
>> enable also this feature so that pSOS and VxWorks libraries can be used.
>> It comes at the price of a slight overhead in time conversions for
>> hi-res interfaces such as cobalt and alchemy.
>
> Do I have to expect any performance problems now? How big is that
> "price of a slight overhead" especially on x86?
>
No recent idea, someone needs to measure this again.
> I'm asking because internal customers are using the debianization "as
> is", if there is now a need to deactivate this feature for them I have
> to be careful during the next release cycle.
>
> I see the need for activating it here to get CI running again but the
> test should not fail if the feature is not available, the tests should
> be skipped, no? Would say we have a "double fault" here.
Making the tests skip if the feature is not available remains a todo, yet.
Jan
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2023-08-09 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 13:32 [PATCH] debian: Enable lores clock by default Jan Kiszka
2023-08-09 13:54 ` Florian Bezdeka
2023-08-09 14:02 ` Jan Kiszka [this message]
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=c0b1faa1-d791-4245-bbd9-d0156032d9cf@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aaron@sigma-star.at \
--cc=florian.bezdeka@siemens.com \
--cc=richard@nod.at \
--cc=xenomai@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).