From: Richard Palethorpe <rpalethorpe@suse.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 3/7] fzsync: Correctly print positive lower delay range bound
Date: Fri, 19 Mar 2021 09:18:33 +0000 [thread overview]
Message-ID: <20210319091837.27319-4-rpalethorpe@suse.com> (raw)
In-Reply-To: <20210319091837.27319-1-rpalethorpe@suse.com>
If the magnitude of delay_bias is large enough then it can turn the
lower bound positive.
Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
---
include/tst_fuzzy_sync.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/tst_fuzzy_sync.h b/include/tst_fuzzy_sync.h
index b8841d96d..4063e95cb 100644
--- a/include/tst_fuzzy_sync.h
+++ b/include/tst_fuzzy_sync.h
@@ -518,9 +518,9 @@ static void tst_fzsync_pair_update(struct tst_fzsync_pair *pair)
tst_res(TINFO,
"Reached deviation ratios < %.2f, introducing randomness",
pair->max_dev_ratio);
- tst_res(TINFO, "Delay range is [-%d, %d]",
- (int)(pair->diff_sb.avg / per_spin_time) + pair->delay_bias,
- (int)(pair->diff_sa.avg / per_spin_time) - pair->delay_bias);
+ tst_res(TINFO, "Delay range is [%d, %d]",
+ -(int)(pair->diff_sb.avg / per_spin_time) + pair->delay_bias,
+ (int)(pair->diff_sa.avg / per_spin_time) + pair->delay_bias);
tst_fzsync_pair_info(pair);
pair->sampling = -1;
}
--
2.30.1
next prev parent reply other threads:[~2021-03-19 9:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 9:18 [LTP] [PATCH v3 0/7] Fuzzy Sync single core support and tests Richard Palethorpe
2021-03-19 9:18 ` [LTP] [PATCH v3 1/7] fzsync: Add self tests Richard Palethorpe
2021-04-08 15:13 ` Cyril Hrubis
2021-04-09 9:34 ` Richard Palethorpe
2021-04-12 13:57 ` Li Wang
2021-04-13 6:42 ` Richard Palethorpe
2021-03-19 9:18 ` [LTP] [PATCH v3 2/7] fzsync: Reset delay bias Richard Palethorpe
2021-04-07 15:38 ` Cyril Hrubis
2021-03-19 9:18 ` Richard Palethorpe [this message]
2021-04-07 15:40 ` [LTP] [PATCH v3 3/7] fzsync: Correctly print positive lower delay range bound Cyril Hrubis
2021-03-19 9:18 ` [LTP] [PATCH v3 4/7] fzsync: Add sched_yield for single core machine Richard Palethorpe
2021-03-19 9:18 ` [LTP] [PATCH v3 5/7] fzsync: Move yield check out of loop and add yield to delay Richard Palethorpe
2021-04-08 12:45 ` Cyril Hrubis
2021-03-19 9:18 ` [LTP] [PATCH v3 6/7] API: Add tst_ncpus_available Richard Palethorpe
2021-04-07 15:39 ` Cyril Hrubis
2021-03-19 9:18 ` [LTP] [PATCH v3 7/7] fzsync: Check processor affinity Richard Palethorpe
2021-04-08 12:47 ` Cyril Hrubis
2021-04-09 7:18 ` Li Wang
2021-04-09 9:50 ` Richard Palethorpe
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=20210319091837.27319-4-rpalethorpe@suse.com \
--to=rpalethorpe@suse.com \
--cc=ltp@lists.linux.it \
/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