From: Jassi Brar <jassisinghbrar@gmail.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Rob Herring <robh@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Frank Rowand <frowand.list@gmail.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Devicetree List <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] dt-bindings: mailbox: add doorbell support to ARM MHU
Date: Fri, 5 Jun 2020 10:42:54 -0500 [thread overview]
Message-ID: <CABb+yY2TR7tuMx6u8yah6mO2GwZ5SWYOO80EQRL-i=ybgn=Wog@mail.gmail.com> (raw)
In-Reply-To: <20200605085830.GA32372@bogus>
On Fri, Jun 5, 2020 at 3:58 AM Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> > > > >> bash-1526 [000] 1149.472553: scmi_xfer_begin: transfer_id=1538 msg_id=6 protocol_id=21 seq=0 poll=0
> > > > >> <idle>-0 [001] 1149.472733: scmi_xfer_begin: transfer_id=1539 msg_id=7 protocol_id=19 seq=1 poll=1
> > > > >
> > > > Here another request is started before the first is finished.
> > >
> > > Ah, the prints are when the client requested. It is not when the mailbox
> > > started it. So this just indicates the beginning of the transfer from the
> > > client.
> > >
> > There maybe condition on a sensor read to finish within 1ms, but there
> > is no condition for the read to _start_ at this very moment (usually
> > there are sleeps in the path to sensor requests).
> >
>
> Again I wasn't clear. The trace logs are at the point just before calling
> mbox_send_messages. So any delay in sensor drivers won't get include. It
> is after the point sensor driver request to read the value and before we
> send the request via mailbox.
>
No, you were clear, I wasn't. Let me try again.
Since origin upto scmi_xfer, there can be many forms of sleep like
schedule/mutexlock etc.... think of some userspace triggering sensor
or dvfs operation. Linux does not provide real-time guarantees. Even
if remote (scmi) firmware guarantee RT response, it makes sense to
timeout a response only after the _request is on the bus_ and not
when you submit a request to the api (unless you serialise it).
IOW, start the timeout from mbox_client.tx_prepare() when the
message actually gets on the bus.
> > You have shared only 'bad' log without serialising access. Please
> > share log after serialising access to the channel and the 'good' log
> > with virtual channels. That should put the topic to rest.
> >
>
> I didn't realise that, sorry for missing that earlier. Attached both
> now, thanks for asking.
>
Interesting logs ! The time taken to complete _successful_ requests
are arguably better in bad_trace ... there are many <10usec responses
in bad_trace, while the fastest response in good_trace is 53usec.
And the requests that 'fail/timeout' are purely the result of not
serialising them or checkout for timeout at wrong place as explained
above.
thanks.
next prev parent reply other threads:[~2020-06-05 15:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 5:17 [RFC] dt-bindings: mailbox: add doorbell support to ARM MHU Viresh Kumar
2020-05-15 16:46 ` Jassi Brar
2020-05-18 7:35 ` Viresh Kumar
2020-05-19 0:53 ` Jassi Brar
2020-05-19 4:39 ` Viresh Kumar
2020-05-19 1:29 ` Bjorn Andersson
2020-05-19 3:40 ` Viresh Kumar
2020-05-19 4:05 ` Jassi Brar
2020-06-03 18:31 ` Sudeep Holla
2020-06-03 18:42 ` Jassi Brar
2020-06-03 18:28 ` Sudeep Holla
2020-05-28 19:20 ` Rob Herring
2020-05-29 4:07 ` Viresh Kumar
2020-06-03 18:04 ` Sudeep Holla
2020-06-03 18:17 ` Sudeep Holla
2020-06-04 5:59 ` Viresh Kumar
2020-06-04 8:28 ` Sudeep Holla
2020-06-03 18:32 ` Jassi Brar
2020-06-04 9:20 ` Sudeep Holla
2020-06-04 15:15 ` Jassi Brar
2020-06-05 4:56 ` Sudeep Holla
2020-06-05 6:30 ` Jassi Brar
2020-06-05 8:58 ` Sudeep Holla
2020-06-05 15:42 ` Jassi Brar [this message]
2020-06-10 9:33 ` Viresh Kumar
2020-06-11 10:00 ` Sudeep Holla
2020-06-12 0:34 ` Jassi Brar
2020-06-12 5:28 ` Viresh Kumar
2020-09-08 9:14 ` Arnd Bergmann
2020-09-08 9:27 ` Viresh Kumar
2020-09-08 13:26 ` Sudeep Holla
2020-09-09 3:23 ` Jassi Brar
2020-09-09 4:46 ` Viresh Kumar
2020-09-09 9:31 ` Sudeep Holla
2020-05-29 5:20 ` Jassi Brar
2020-05-29 6:27 ` Viresh Kumar
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='CABb+yY2TR7tuMx6u8yah6mO2GwZ5SWYOO80EQRL-i=ybgn=Wog@mail.gmail.com' \
--to=jassisinghbrar@gmail.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).