From: Tejun Heo <tj@kernel.org>
To: Tirumalesh Chalamarla <tchalamarla@caviumnetworks.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
stripathi@apm.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3] AHCI: Workaround for ThunderX Errata#22536
Date: Mon, 29 Feb 2016 16:12:23 -0500 [thread overview]
Message-ID: <20160229211223.GZ3965@htj.duckdns.org> (raw)
In-Reply-To: <56CF64B9.4080605@caviumnetworks.com>
Hello,
Sorry about the delay.
On Thu, Feb 25, 2016 at 12:31:53PM -0800, Tirumalesh Chalamarla wrote:
> On 02/17/2016 08:12 AM, Thomas Gleixner wrote:
> >On Tue, 16 Feb 2016, tchalamarla@caviumnetworks.com wrote:
> >>+#ifdef CONFIG_ARM64
> >>+/* Due to ERRATA#22536, ThunderX need to handle
> >>+ * HOST_IRQ_STAT differently.
> >>+ * Work around is to make sure all pending IRQs
> >>+ * are served before leaving handler
> >>+ */
> >>+static irqreturn_t ahci_thunderx_irq_handler(int irq, void *dev_instance)
> >>+{
> >>+ struct ata_host *host = dev_instance;
> >>+ struct ahci_host_priv *hpriv;
> >>+ unsigned int rc = 0;
> >>+ void __iomem *mmio;
> >>+ u32 irq_stat, irq_masked;
> >>+ unsigned int handled = 1;
> >>+
> >>+ VPRINTK("ENTER\n");
> >
> >Come on. This VPRINK stuff is really pointless. Enable irq tracepoints, they
> >already track the enter/exit of interrupt handlers ....
>
> sure. waiting for some more comments if any.
Yeah, VPRINTK way predates tracepoints and is kinda silly at this
point. That said, it's used relatively consistently across libata and
some people still use it for debugging. We can replace them with
proper tracepoints but that's a work for another patchset. For now,
let's leave it in for consistency with counterparts.
Thanks.
--
tejun
next prev parent reply other threads:[~2016-02-29 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 20:08 tchalamarla
2016-02-17 16:12 ` Thomas Gleixner
2016-02-25 20:31 ` Tirumalesh Chalamarla
2016-02-29 21:12 ` Tejun Heo [this message]
2016-02-24 0:00 ` Tirumalesh Chalamarla
2016-02-29 21:17 ` Tejun Heo
2016-02-29 22:00 ` Tirumalesh Chalamarla
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=20160229211223.GZ3965@htj.duckdns.org \
--to=tj@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stripathi@apm.com \
--cc=tchalamarla@caviumnetworks.com \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®