linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: early_printk: use printascii() rather than printch()
Date: Mon, 2 Oct 2017 07:20:32 +0200	[thread overview]
Message-ID: <20171002052032.5ohpvogewio6axdr@pengutronix.de> (raw)
In-Reply-To: <20171002020618.23924-4-nicolas.pitre@linaro.org>

Hello Nicolas,

On Sun, Oct 01, 2017 at 10:06:18PM -0400, Nicolas Pitre wrote:
> With printch() the console messages are sent out one character at a time
> which is agonizingly slow especially with semihosting as the whole trap
> intercept, remote byte access, and system resume danse is performed for

s/danse/dance/ ?

> every single character across a relatively slow remote debug connection.
> Let's use printascii() to send a whole string at once. This is also going
> to be more efficient, albeit to a quite lesser extent, with serial ports
> as well.
> 
> Signed-off-by: Nicolas Pitre <nico@linaro.org>
> ---
>  arch/arm/kernel/early_printk.c | 16 ++++++++++------
>  1 file changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/arch/arm/kernel/early_printk.c b/arch/arm/kernel/early_printk.c
> index 4307653696..9257736ec9 100644
> --- a/arch/arm/kernel/early_printk.c
> +++ b/arch/arm/kernel/early_printk.c
> @@ -11,16 +11,20 @@
>  #include <linux/kernel.h>
>  #include <linux/console.h>
>  #include <linux/init.h>
> +#include <linux/string.h>
>  
> -extern void printch(int);
> +extern void printascii(const char *);
>  
>  static void early_write(const char *s, unsigned n)
>  {
> -	while (n-- > 0) {
> -		if (*s == '\n')
> -			printch('\r');
> -		printch(*s);
> -		s++;
> +	char buf[128];
> +	while (n) {
> +		unsigned l = min(n, sizeof(buf)-1);
> +		memcpy(buf, s, l);
> +		buf[l] = 0;
> +		s += l;
> +		n -= l;
> +		printascii(buf);

I wonder if it is a usual case that n < 128 and s[n] == '\0'. If so this
could be tested for and then the memcpy could be dropped.
(The downside of course is that s[n] might also be something completely
different?)

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2017-10-02  5:20 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02  2:06 [PATCH 0/3] a few debug_ll fixes and improvements Nicolas Pitre
2017-10-02  2:06 ` [PATCH 1/3] ARM: debug.S: move hexbuf to a writable section Nicolas Pitre
2017-10-02  2:06 ` [PATCH 2/3] ARM: semihosting: use proper instruction on v7m processors Nicolas Pitre
2017-10-02  2:06 ` [PATCH 3/3] ARM: early_printk: use printascii() rather than printch() Nicolas Pitre
2017-10-02  5:20   ` Uwe Kleine-König [this message]
2017-10-02 14:09     ` Nicolas Pitre
2017-10-31 11:28   ` Chris Brandt
2017-10-31 16:22     ` Nicolas Pitre
2017-10-31 16:38       ` Robin Murphy
2017-10-31 17:06         ` Nicolas Pitre
2017-10-31 17:16           ` Russell King - ARM Linux
2017-10-31 17:48             ` Nicolas Pitre
2017-10-31 17:53               ` Russell King - ARM Linux
2017-10-31 18:15                 ` Nicolas Pitre
2017-10-31 18:20                   ` Russell King - ARM Linux
2017-10-31 18:35                     ` Nicolas Pitre
2017-10-31 19:12                       ` Chris Brandt
2017-10-31 19:28                         ` Nicolas Pitre
2017-10-31 21:50                           ` Russell King - ARM Linux
2017-10-31 23:35                             ` Nicolas Pitre
2017-10-31 23:50                               ` Russell King - ARM Linux
2017-11-02  0:09                         ` Russell King - ARM Linux
2017-11-02  3:59                           ` Nicolas Pitre
2017-11-02  4:16                             ` Nicolas Pitre
2017-11-02 11:09                               ` Russell King - ARM Linux
2017-11-02 15:12                                 ` Nicolas Pitre
2017-11-02 11:06                             ` Chris Brandt
2017-11-02 11:20                               ` Russell King - ARM Linux
2017-11-02 11:28                                 ` Chris Brandt
2017-11-02 13:04                                   ` Russell King - ARM Linux
2017-11-02 15:04                                   ` Nicolas Pitre
2017-11-02 15:18                                     ` Robin Murphy
2017-11-02 15:22                                       ` Russell King - ARM Linux
2017-11-02 15:25                                       ` Chris Brandt
2017-11-02 15:23                                     ` Chris Brandt
2017-11-02 15:35                                       ` Nicolas Pitre
2017-11-02 16:06                                         ` Nicolas Pitre
2017-11-02 16:38                                           ` Chris Brandt
2017-11-02 17:10                                             ` Russell King - ARM Linux
2017-11-02 17:20                                               ` Nicolas Pitre
2017-11-02 17:28                                               ` Chris Brandt
2017-11-02 18:29                                               ` Robin Murphy
2017-11-02 21:46                                                 ` syntax unified, was " Nicolas Pitre
2017-11-02 15:48                                       ` Russell King - ARM Linux
2017-11-02 16:30                                         ` Chris Brandt

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=20171002052032.5ohpvogewio6axdr@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).