Linux Trace Development
 help / color / mirror / Atom feed
From: Yordan Karadzhov <y.karadz@gmail.com>
To: Hongzhan Chen <hongzhan.chen@intel.com>,
	linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH V4 3/3] kernel-shark: Add plugin for handling Xenomai cobalt_context_switch
Date: Mon, 10 Jan 2022 15:21:06 +0200	[thread overview]
Message-ID: <630880f4-7056-84a4-66ad-17198fcd5400@gmail.com> (raw)
In-Reply-To: <20220110042518.9376-3-hongzhan.chen@intel.com>



On 10.01.22 г. 6:25 ч., Hongzhan Chen wrote:
> +	eventFieldIntervalPlot(argvCpp,
> +			       plugin_ctx->cs_data, checkFieldCS,
> +			       plugin_ctx->cs_data, checkEntryPid,
> +			       makeLatencyBox<XenomaiSwitchBox>,
> +			       {0, 0, KS_COBALT_BLUE}, // Cobalt Blue
> +			       -1);         // Default size

Hi Hongzhan,

I meant something different with my comment about 'cobalt blue'. Here you define the color with RGB coordinates (0, 0, 
255). This means 255 on the blue axis and zeros on the red and green. This is what I meant by 'just blue'. The RGB 
coordinates of the 'cobalt blue' color are (0, 71, 171). This means it is some mixture between green and blue.

Cheers,
Yordan

  reply	other threads:[~2022-01-10 13:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10  4:25 [PATCH V4 1/3] kernel-shark: fix typo in sched_events.h Hongzhan Chen
2022-01-10  4:25 ` [PATCH V4 2/3] kernel-shark: Move common APIs and definitions out to avoid duplication Hongzhan Chen
2022-01-10 13:10   ` Yordan Karadzhov
2022-01-11  8:03     ` Chen, Hongzhan
2022-01-11  8:32       ` Yordan Karadzhov
2022-01-10  4:25 ` [PATCH V4 3/3] kernel-shark: Add plugin for handling Xenomai cobalt_context_switch Hongzhan Chen
2022-01-10 13:21   ` Yordan Karadzhov [this message]
2022-01-10 12:30 ` [PATCH V4 1/3] kernel-shark: fix typo in sched_events.h Yordan Karadzhov

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=630880f4-7056-84a4-66ad-17198fcd5400@gmail.com \
    --to=y.karadz@gmail.com \
    --cc=hongzhan.chen@intel.com \
    --cc=linux-trace-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox