From: dmkhn@proton.me
To: Jan Beulich <jbeulich@suse.com>
Cc: andrew.cooper3@citrix.com, anthony.perard@vates.tech,
julien@xen.org, michal.orzel@amd.com, roger.pau@citrix.com,
sstabellini@kernel.org, dmukhin@ford.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] ns16550: ensure polling timer is disarmed
Date: Thu, 31 Jul 2025 21:42:01 +0000 [thread overview]
Message-ID: <aIvjJP6bpJpsQRtQ@kraken> (raw)
In-Reply-To: <78128ec6-b79f-4d4c-a298-72315b190036@suse.com>
On Thu, Jul 31, 2025 at 08:54:10AM +0200, Jan Beulich wrote:
> On 30.07.2025 20:31, dmkhn@proton.me wrote:
> > On Wed, Jul 30, 2025 at 10:12:54AM +0200, Jan Beulich wrote:
> >> On 30.07.2025 05:13, dmkhn@proton.me wrote:
> >>> From: Denis Mukhin <dmukhin@ford.com>
> >>>
> >>> As it stands, polling timer is kept in the list of timers even after the
> >>> interrupts have been enabled / polling disabled on ns16550-compatible UART.
> >>>
> >>> Ensure polling timer is removed from the timer list once UART interrupts are
> >>> enabled.
> >>>
> >>> Signed-off-by: Denis Mukhin <dmukhin@ford.com>
> >>
> >> Wasn't it Andrew(?) who suggested something along these lines? That would
> >> want reflecting by a tag then.
> >
> > Yes, indeed.
> >
> >>
> >> Also, what's the real problem you want to solve here? The timer function
> >> would be run one more time after ->intr_works is set, and then the timer
> >> will be permanently inactive (up to a possible S3 resume). Is it being on
> >> an inactive list an actual problem? (IOW I'd like to understand if the
> >> change is merely cosmetic, or if there is some actual benefit.)
> >
> > My understanding is running polling timer one more time after the interrupts
> > are enabled is the issue: if there's a pending timer when it is known the
> > timer not needed, then the timer should be canceled.
>
> And the effort of canceling outweighs the one extra running of the timer?
I think so, because intr_works will not flip at run-time once set.
If so, no need to keep the timer ready to be rearmed.
>
> Jan
next prev parent reply other threads:[~2025-07-31 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 3:13 [PATCH] ns16550: ensure polling timer is disarmed dmkhn
2025-07-30 8:12 ` Jan Beulich
2025-07-30 18:31 ` dmkhn
2025-07-31 6:54 ` Jan Beulich
2025-07-31 21:42 ` dmkhn [this message]
2025-08-01 7:34 ` Jan Beulich
2025-08-06 10:53 ` Roger Pau Monné
2025-08-06 11:44 ` Jan Beulich
2025-08-06 10:47 ` Roger Pau Monné
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=aIvjJP6bpJpsQRtQ@kraken \
--to=dmkhn@proton.me \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dmukhin@ford.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--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.