From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: "Collin L. Walling" <walling@linux.vnet.ibm.com>,
cohuck@redhat.com, borntraeger@de.ibm.com
Cc: thuth@redhat.com, bwalk@linux.vnet.ibm.com, david@redhat.com,
pmorel@linux.vnet.ibm.com, qemu-devel@nongnu.org, agraf@suse.de,
jjherne@linux.vnet.ibm.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v4] s390-ccw: print carriage return with new lines
Date: Fri, 27 Oct 2017 19:40:55 +0200 [thread overview]
Message-ID: <5eddee30-b571-cd24-3643-dffb60dde6e2@linux.vnet.ibm.com> (raw)
In-Reply-To: <1509120893-28054-1-git-send-email-walling@linux.vnet.ibm.com>
On 10/27/2017 06:14 PM, Collin L. Walling wrote:
> The sclp console in the s390 bios writes raw data,
> leading console emulators (such as virsh console) to
> treat a new line ('\n') as just a new line instead
> of as a Unix line feed. Because of this, output
> appears in a "stair case" pattern.
>
> Let's print \r\n on every occurrence of a new line
> in the string passed to write to amend this issue.
>
> This is in sync with the guest Linux code in
> drivers/s390/char/sclp_vt220.c which also does a line feed
> conversion in the console part of the driver.
>
> This fixes the s390-ccw and s390-netboot output like
> $ virsh start test --console
> Domain test started
> Connected to domain test
> Escape character is ^]
> Network boot starting...
> Using MAC address: 02:01:02:03:04:05
> Requesting information via DHCP: 010
>
> Signed-off-by: Collin L. Walling <walling@linux.vnet.ibm.com>
Reviewed-by: Halil Pasic <pasic@linux.vnet.ibm.com>
> ---
> pc-bios/s390-ccw/sclp.c | 24 +++++++++++++++++++++---
> 1 file changed, 21 insertions(+), 3 deletions(-)
>
> diff --git a/pc-bios/s390-ccw/sclp.c b/pc-bios/s390-ccw/sclp.c
> index 486fce1..e6a0898 100644
> --- a/pc-bios/s390-ccw/sclp.c
> +++ b/pc-bios/s390-ccw/sclp.c
> @@ -68,17 +68,35 @@ void sclp_setup(void)
> long write(int fd, const void *str, size_t len)
> {
> WriteEventData *sccb = (void *)_sccb;
> + const char *p = str;
> + size_t data_len = 0;
> + size_t i;
>
> if (fd != 1 && fd != 2) {
> return -EIO;
> }
>
> - sccb->h.length = sizeof(WriteEventData) + len;
> + for (i = 0; i < len; i++) {
> + if ((data_len + 1) >= SCCB_DATA_LEN) {
> + /* We would overflow the sccb buffer, abort early */
> + len = i;
> + break;
> + }
> +
> + if (*p == '\n') {
> + /* Terminal emulators might need \r\n, so generate it */
> + sccb->data[data_len++] = '\r';
> + }
> +
> + sccb->data[data_len++] = *p;
> + p++;
> + }
> +
> + sccb->h.length = sizeof(WriteEventData) + data_len;
> sccb->h.function_code = SCLP_FC_NORMAL_WRITE;
> - sccb->ebh.length = sizeof(EventBufferHeader) + len;
> + sccb->ebh.length = sizeof(EventBufferHeader) + data_len;
> sccb->ebh.type = SCLP_EVENT_ASCII_CONSOLE_DATA;
> sccb->ebh.flags = 0;
> - memcpy(sccb->data, str, len);
>
> sclp_service_call(SCLP_CMD_WRITE_EVENT_DATA, sccb);
>
next prev parent reply other threads:[~2017-10-27 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 16:14 [Qemu-devel] [PATCH v4] s390-ccw: print carriage return with new lines Collin L. Walling
2017-10-27 17:40 ` Halil Pasic [this message]
2017-10-27 20:25 ` Farhan Ali
2017-10-28 6:58 ` Cornelia Huck
2017-10-29 1:58 ` Alexander Graf
2017-10-30 8:08 ` Christian Borntraeger
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=5eddee30-b571-cd24-3643-dffb60dde6e2@linux.vnet.ibm.com \
--to=pasic@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=bwalk@linux.vnet.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
--cc=walling@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).