[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55B8BE39.6080500@hurleysoftware.com>
Date: Wed, 29 Jul 2015 07:51:21 -0400
From: Peter Hurley <peter@...leysoftware.com>
To: Thomas Gleixner <tglx@...utronix.de>,
Taichi Kageyama <t-kageyama@...jp.nec.com>
CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"jiang.liu@...ux.intel.com" <jiang.liu@...ux.intel.com>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jslaby@...e.cz" <jslaby@...e.cz>,
"prarit@...hat.com" <prarit@...hat.com>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>
Subject: Re: [RFC PATCH v2 0/3] genirq, serial: 8250: Workaround to avoid
irq=0 for console
On 07/29/2015 06:32 AM, Thomas Gleixner wrote:
> On Wed, 29 Jul 2015, Taichi Kageyama wrote:
>> - Keep interrupt disabled on the CPU which is used to detect
>> an interrupt during the timeout of autoconfig_irq().
>> + Kick printk() on the CPU which detects interrupt
>> from a console serial port.
>
> This is wrong to begin with. How is that supposed to work on an UP
> machine? Not at all.
>
> So no, fix the code which has interrupts disabled accross autoprobing
> and do not try to apply bandaids somewhere else.
Like printk() from some unrelated driver?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists