From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Linux regressions mailing list" <regressions@lists.linux.dev>,
"Stefan Wahren" <stefan.wahren@i2se.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Stefan Wahren" <stefan.wahren@chargebyte.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sergey Organov" <sorganov@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
linux-serial@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Fabio Estevam" <festevam@gmail.com>,
"Tomasz Moń" <tomasz.mon@camlingroup.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>
Subject: Re: Regression: serial: imx: overrun errors on debug UART
Date: Wed, 21 Jun 2023 10:43:39 +0200 [thread overview]
Message-ID: <2023062116-skintight-royal-39d8@gregkh> (raw)
In-Reply-To: <20230620192748.ey4oah22resbblej@pengutronix.de>
On Tue, Jun 20, 2023 at 09:27:48PM +0200, Uwe Kleine-König wrote:
> Hello Greg,
>
> On Tue, Jun 20, 2023 at 04:59:18PM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Jun 20, 2023 at 04:47:10PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> > > On 24.05.23 15:07, Stefan Wahren wrote:
> > > >
> > > > Am 23.05.23 um 21:44 schrieb Sergey Organov:
> > > >> "Linux regression tracking (Thorsten Leemhuis)"
> > > >> <regressions@leemhuis.info> writes:
> > > >>
> > > >> Solving this would need to identify the cause of interrupts being
> > > >> disabled for prolonged times, and nobody volunteered to investigate this
> > > >> further. One suspect, the Linux serial console, has been likely excluded
> > > >> already though, as not actually being in use for printk() output.
> > > >>
> > > >
> > > > I don't think that we can exclude the serial console as a whole, i never
> > > > made such a observation. But at least we can exclude kernel logging on
> > > > the debug UART.
> > >
> > > Stefan, just wondering: was this ever addressed upstream? I assume it's
> > > not, just wanted to be sure.
> > >
> > > I'm a bit unsure what to do with this and consider asking Greg for
> > > advice, as he applied the patch. On one hand it's *IMHO* clearly a
> > > regression (but for the record, some people involved in the discussion
> > > claim it's not). OTOH the culprit was applied more than a year ago now,
> > > so reverting it might cause more trouble than it's worth at this point,
> > > as that could lead to regressions for other users.
> >
> > I'll be glad to revert this, but for some reason I thought that someone
> > was working on a "real fix" here. Stefan, is that not the case?
>
> Sergey Organov already said something similar, but not very explicit:
> With the current understanding reverting said commit is wrong. It is
> expected that the commit increases irq latency for imx-serial a bit for
> the benefit of less interrupts and so serves the overall system
> performance. That this poses a problem only means that on the reporter's
> machine there is already an issue that results in a longer period with
> disabled irqs. While reverting the imx-serial commit would (maybe) solve
> that, the actual problem is the other issue that disables preemption for
> a longer timespan.
>
> So TL;DR: Please don't revert the imx-serial patch.
Ok, will leave this alone, it shouldn't be marked as a regression.
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-21 8:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 8:57 Regression: serial: imx: overrun errors on debug UART Stefan Wahren
2023-03-24 10:12 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-03-24 11:47 ` Ilpo Järvinen
2023-03-24 12:26 ` Francesco Dolcini
2023-03-24 12:35 ` Ilpo Järvinen
2023-03-24 12:49 ` Stefan Wahren
2023-03-24 13:06 ` Francesco Dolcini
2023-03-24 12:57 ` Fabio Estevam
2023-03-24 13:37 ` Uwe Kleine-König
2023-03-24 14:19 ` Stefan Wahren
2023-03-24 14:39 ` Uwe Kleine-König
2023-03-24 21:57 ` Sergey Organov
2023-03-24 15:00 ` Stefan Wahren
2023-03-25 11:31 ` Stefan Wahren
2023-03-25 12:23 ` Fabio Estevam
2023-03-25 15:11 ` Uwe Kleine-König
2023-03-25 17:05 ` Stefan Wahren
2023-03-25 19:00 ` Sergey Organov
2023-03-26 18:21 ` Francesco Dolcini
2023-03-27 8:07 ` Tomasz Moń
2023-03-25 18:30 ` Sergey Organov
2023-03-27 14:42 ` Stefan Wahren
2023-03-27 15:11 ` Sergey Organov
2023-03-27 15:30 ` Russell King (Oracle)
2023-04-16 13:43 ` Stefan Wahren
2023-04-17 16:50 ` Sergey Organov
2023-04-17 18:40 ` Stefan Wahren
2023-04-18 16:16 ` Stefan Wahren
2023-05-22 9:25 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-23 15:12 ` Stefan Wahren
2023-05-23 19:44 ` Sergey Organov
2023-05-24 10:48 ` Thorsten Leemhuis
2023-05-24 12:41 ` Uwe Kleine-König
2023-05-24 13:45 ` Sergey Organov
2023-05-24 13:07 ` Stefan Wahren
2023-06-20 14:47 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-20 14:59 ` Greg Kroah-Hartman
2023-06-20 15:34 ` Sergey Organov
2023-06-20 16:30 ` Stefan Wahren
2023-06-20 16:40 ` Lucas Stach
2023-06-20 16:55 ` Stefan Wahren
2023-06-20 19:27 ` Uwe Kleine-König
2023-06-21 8:43 ` Greg Kroah-Hartman [this message]
2023-06-21 6:23 ` Stefan Wahren
2023-06-21 13:42 ` Linux regression tracking (Thorsten Leemhuis)
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=2023062116-skintight-royal-39d8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=festevam@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-serial@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=sorganov@gmail.com \
--cc=stefan.wahren@chargebyte.com \
--cc=stefan.wahren@i2se.com \
--cc=tomasz.mon@camlingroup.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).