From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
thuth@redhat.com, david@redhat.com, nsg@linux.ibm.com,
nrb@linux.ibm.com
Subject: Re: [kvm-unit-tests RFC 1/3] lib: s390x: sclp: Add carriage return to line feed
Date: Mon, 3 Jul 2023 14:04:10 +0200 [thread overview]
Message-ID: <20230703140410.6d1907d5@p-imbrenda> (raw)
In-Reply-To: <6ad06172-ad8e-4615-ad20-d254dcb3f380@linux.ibm.com>
On Mon, 3 Jul 2023 13:46:29 +0200
Janosch Frank <frankja@linux.ibm.com> wrote:
> On 6/30/23 17:12, Claudio Imbrenda wrote:
> > On Fri, 30 Jun 2023 14:54:47 +0000
> > Janosch Frank <frankja@linux.ibm.com> wrote:
> >
> >> Without the \r the output of the ASCII console takes a lot of
> >> additional effort to read in comparison to the line mode console.
> >>
> >> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> >> ---
> >> lib/s390x/sclp-console.c | 15 ++++++++++++++-
> >> 1 file changed, 14 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/lib/s390x/sclp-console.c b/lib/s390x/sclp-console.c
> >> index 19c74e46..384080b0 100644
> >> --- a/lib/s390x/sclp-console.c
> >> +++ b/lib/s390x/sclp-console.c
> >> @@ -97,14 +97,27 @@ static void sclp_print_ascii(const char *str)
> >> {
> >> int len = strlen(str);
> >> WriteEventData *sccb = (void *)_sccb;
> >> + char *str_dest = (char *)&sccb->msg;
> >> + int i = 0;
> >>
> >> sclp_mark_busy();
> >> memset(sccb, 0, sizeof(*sccb));
> >> +
> >> + for (; i < len; i++) {
> >> + *str_dest = str[i];
> >> + str_dest++;
> >> + /* Add a \r to the \n */
> >> + if (str[i] == '\n') {
> >> + *str_dest = '\r';
> >> + str_dest++;
> >> + }
> >> + }
> >> +
> >> + len = (uintptr_t)str_dest - (uintptr_t)&sccb->msg;
> >
> > some strings will therefore potentially overflow the SCCB
> >
> > sclp_print() refuses to print more than 2kB, with this patch that limit
> > could potentially be crossed
> >
> > can you please briefly explain in a comment why that is ok? (or maybe
> > that is not ok? then fix it somehow :) )
>
> I'd like to see someone find a useful application for printing 2kb in a
> single printf() call.
I'm with you there
>
> Anyway, I could truncate the ASCII after the 2KB limit when adding the \r.
sounds like a plan
>
> I'm wondering how the line-mode console interprets the \r. If it ignores
> it, then we could also convert to \n\r for both consoles and check for
> 2kb when converting.
is \n\r the right order? what about \r\n ?
next prev parent reply other threads:[~2023-07-03 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 14:54 [kvm-unit-tests RFC 0/3] s390x: Improve console handling Janosch Frank
2023-06-30 14:54 ` [kvm-unit-tests RFC 1/3] lib: s390x: sclp: Add carriage return to line feed Janosch Frank
2023-06-30 15:12 ` Claudio Imbrenda
2023-07-03 11:46 ` Janosch Frank
2023-07-03 12:04 ` Claudio Imbrenda [this message]
2023-06-30 14:54 ` [kvm-unit-tests RFC 2/3] lib: s390x: sclp: Clear ASCII screen on setup Janosch Frank
2023-06-30 15:25 ` Claudio Imbrenda
2023-07-03 11:36 ` Janosch Frank
2023-07-03 11:57 ` Claudio Imbrenda
2023-07-03 12:30 ` Janosch Frank
2023-06-30 14:54 ` [kvm-unit-tests RFC 3/3] lib: s390x: sclp: Add line mode input handling Janosch Frank
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=20230703140410.6d1907d5@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=thuth@redhat.com \
/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