From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Huang Shijie <shijie.huang-5wv7dgnIgG8@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
nd-5wv7dgnIgG8@public.gmane.org,
will.deacon-5wv7dgnIgG8@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] iommu/arm-smmu: add a shortcut when the @dev_node is NULL
Date: Wed, 20 Jan 2016 13:02:25 +0100 [thread overview]
Message-ID: <20160120120225.GD18805@8bytes.org> (raw)
In-Reply-To: <1452564905-2662-1-git-send-email-shijie.huang-5wv7dgnIgG8@public.gmane.org>
On Tue, Jan 12, 2016 at 10:15:05AM +0800, Huang Shijie wrote:
> This patch adds a shortcut for the code when the @device_node is NULL.
> In my juno-r1 board, the boot time can be faster by 0.004014s.
How have you made sure this number is reliable and not just noise in the
boot process?
Joerg
next prev parent reply other threads:[~2016-01-20 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 2:15 [PATCH] iommu/arm-smmu: add a shortcut when the @dev_node is NULL Huang Shijie
[not found] ` <1452564905-2662-1-git-send-email-shijie.huang-5wv7dgnIgG8@public.gmane.org>
2016-01-20 12:02 ` Joerg Roedel [this message]
[not found] ` <20160120120225.GD18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-01-20 13:34 ` Huang Shijie
[not found] ` <20160120133401.GA3487-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2016-01-20 14:46 ` Robin Murphy
2016-01-20 16:00 ` Jon Medhurst (Tixy)
[not found] ` <569F9DCA.3030808-5wv7dgnIgG8@public.gmane.org>
2016-01-21 2:04 ` Huang Shijie
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=20160120120225.GD18805@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nd-5wv7dgnIgG8@public.gmane.org \
--cc=shijie.huang-5wv7dgnIgG8@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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