From: Zhang Zheng <zhangzheng@iscas.ac.cn>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Connor Davis" <connojdavis@gmail.com>,
"Baptiste Le Duc" <baptiste.le-duc@vates.tech>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger@xenproject.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 2/2] xen/ns16550: drain TX before reinitializing
Date: Thu, 15 Oct 2026 12:46:55 +0800 [thread overview]
Message-ID: <atBapx7kJAjjgI4Z@iscas-ws> (raw)
In-Reply-To: <2415e2b7-3066-450b-9917-d1267a1c2b90@suse.com>
On Mon, Oct 12, 2026 at 03:00:19PM +0200, Jan Beulich wrote:
> On 12.10.2026 12:20, Oleksii Kurochko wrote:
> > On 10/10/26 5:14 AM, Zhang Zheng wrote:
> >> --- a/xen/drivers/char/ns16550.c
> >> +++ b/xen/drivers/char/ns16550.c
> >> @@ -427,6 +427,10 @@ static void __init cf_check ns16550_init_preirq(struct serial_port *port)
> >> #endif
> >> }
> >>
> >> + /* Preserve output queued by firmware before taking over the UART. */
> > я'
> > Could the comment say why the wait is needed at this point? Something
> > like:
> >
> > /*
> > * Output written before ns16550 takes over (e.g. by firmware or the
> > * early console) may still be in the transmitter. Let it drain before
> > * ns16550_setup_preirq() reprograms the line settings and resets the
> > * FIFOs.
> > */
> >
> >> + while ( !(ns_read_reg(uart, UART_LSR) & UART_LSR_TEMT) )
> >> + cpu_relax();
> >> +
> >
> > IMO waiting for TEMT rather than THRE is the right choice: besides
> > resetting the FIFOs, ns16550_setup_preirq() reprograms the divisor and
> > LCR, which would corrupt a character still being shifted out. (Linux
> > waits for UART_LSR_BOTH_EMPTY, i.e. THRE | TEMT, but on a 16550 TEMT
> > already implies THRE.)
>
> Then again we have the .lsr_mask field. Not using it here would then call
> for justification in the description.
>
> Jan
I will clarify this distinction in the commit message.
Zhang
next prev parent reply other threads:[~2026-10-15 4:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 3:14 [PATCH v2 0/2] xen/ns16550: preserve UART operation across firmware handover Zhang Zheng
2026-10-10 3:14 ` [PATCH v2 1/2] xen/ns16550: detect and preserve UART_IER_UUE Zhang Zheng
2026-10-10 22:11 ` Baptiste Le Duc
2026-10-12 9:27 ` Oleksii Kurochko
2026-10-15 3:22 ` Zhang Zheng
2026-10-12 9:20 ` Oleksii Kurochko
2026-10-12 12:50 ` Jan Beulich
2026-10-12 13:24 ` Oleksii Kurochko
2026-10-15 4:50 ` Zhang Zheng
2026-10-15 3:44 ` Zhang Zheng
2026-10-12 12:52 ` Jan Beulich
2026-10-15 4:40 ` Zhang Zheng
2026-10-15 7:16 ` Jan Beulich
[not found] ` <20261010031406.2057735-3-zhangzheng@iscas.ac.cn>
2026-10-10 22:13 ` [PATCH v2 2/2] xen/ns16550: drain TX before reinitializing Baptiste Le Duc
2026-10-12 10:20 ` Oleksii Kurochko
2026-10-12 12:56 ` Jan Beulich
2026-10-12 13:25 ` Oleksii Kurochko
2026-10-15 4:52 ` Zhang Zheng
2026-10-12 13:00 ` Jan Beulich
2026-10-15 4:46 ` Zhang Zheng [this message]
2026-10-15 6:48 ` Zhang Zheng
[not found] ` <atB2HqxU_D481PBk@iscas-ws>
2026-10-15 7:54 ` Oleksii Kurochko
2026-10-15 8:49 ` Zhang Zheng
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=atBapx7kJAjjgI4Z@iscas-ws \
--to=zhangzheng@iscas.ac.cn \
--cc=alistair.francis@wdc.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=baptiste.le-duc@vates.tech \
--cc=connojdavis@gmail.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger@xenproject.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.