From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Murali Karicheri <m-karicheri2@ti.com>,
Richard Zhu <hongxing.zhu@nxp.com>,
Lucas Stach <l.stach@pengutronix.de>,
Andrew Murray <andrew.murray@arm.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: imx6 and keystone PCIe abort handling
Date: Fri, 13 Dec 2019 00:51:09 +0000 [thread overview]
Message-ID: <20191213005109.GP25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191213003236.GA43783@google.com>
On Thu, Dec 12, 2019 at 06:32:36PM -0600, Bjorn Helgaas wrote:
> Hi folks,
>
> Why are ks_pcie_fault() and imx6q_pcie_abort_handler() different? I
> think they're doing the same thing, and the "instr & 0x0e100090" part
> is the same, but only imx6 has the "instr & 0x0c100000" part. And the
> return values are different in some cases.
Here's the opcodes for the three different types of loads that would
be interesting.
0: e5910000 ldr r0, [r1] ; 32-bit
4: e5d10000 ldrb r0, [r1] ; 8-bit
8: e1d100b0 ldrh r0, [r1] ; 16-bit
So, (instr & 0x0e100090) == 0x00100090 is trie for the ldrh case.
(instr & 0x0c100000) == 0x04100000 is true for the ldr and ldrb case.
So, the keystone version only traps ldrh instructions, whereas the
imx6 traps them all.
> Could/should these be shared somehow? They're both under #ifdef
> CONFIG_ARM, so maybe it could be provided by arch/arm?
>
> static int ks_pcie_fault(unsigned long addr, unsigned int fsr,
> struct pt_regs *regs)
> {
> unsigned long instr = *(unsigned long *) instruction_pointer(regs);
>
> if ((instr & 0x0e100090) == 0x00100090) {
> int reg = (instr >> 12) & 15;
>
> regs->uregs[reg] = -1;
> regs->ARM_pc += 4;
> }
>
> return 0;
> }
>
> static int imx6q_pcie_abort_handler(unsigned long addr,
> unsigned int fsr, struct pt_regs *regs)
> {
> unsigned long pc = instruction_pointer(regs);
> unsigned long instr = *(unsigned long *)pc;
> int reg = (instr >> 12) & 15;
>
> /*
> * If the instruction being executed was a read,
> * make it look like it read all-ones.
> */
> if ((instr & 0x0c100000) == 0x04100000) {
> unsigned long val;
>
> if (instr & 0x00400000)
> val = 255;
> else
> val = -1;
>
> regs->uregs[reg] = val;
> regs->ARM_pc += 4;
> return 0;
> }
>
> if ((instr & 0x0e100090) == 0x00100090) {
> regs->uregs[reg] = -1;
> regs->ARM_pc += 4;
> return 0;
> }
>
> return 1;
> }
>
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Richard Zhu <hongxing.zhu@nxp.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Murali Karicheri <m-karicheri2@ti.com>,
Andrew Murray <andrew.murray@arm.com>,
linux-arm-kernel@lists.infradead.org,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: imx6 and keystone PCIe abort handling
Date: Fri, 13 Dec 2019 00:51:09 +0000 [thread overview]
Message-ID: <20191213005109.GP25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191213003236.GA43783@google.com>
On Thu, Dec 12, 2019 at 06:32:36PM -0600, Bjorn Helgaas wrote:
> Hi folks,
>
> Why are ks_pcie_fault() and imx6q_pcie_abort_handler() different? I
> think they're doing the same thing, and the "instr & 0x0e100090" part
> is the same, but only imx6 has the "instr & 0x0c100000" part. And the
> return values are different in some cases.
Here's the opcodes for the three different types of loads that would
be interesting.
0: e5910000 ldr r0, [r1] ; 32-bit
4: e5d10000 ldrb r0, [r1] ; 8-bit
8: e1d100b0 ldrh r0, [r1] ; 16-bit
So, (instr & 0x0e100090) == 0x00100090 is trie for the ldrh case.
(instr & 0x0c100000) == 0x04100000 is true for the ldr and ldrb case.
So, the keystone version only traps ldrh instructions, whereas the
imx6 traps them all.
> Could/should these be shared somehow? They're both under #ifdef
> CONFIG_ARM, so maybe it could be provided by arch/arm?
>
> static int ks_pcie_fault(unsigned long addr, unsigned int fsr,
> struct pt_regs *regs)
> {
> unsigned long instr = *(unsigned long *) instruction_pointer(regs);
>
> if ((instr & 0x0e100090) == 0x00100090) {
> int reg = (instr >> 12) & 15;
>
> regs->uregs[reg] = -1;
> regs->ARM_pc += 4;
> }
>
> return 0;
> }
>
> static int imx6q_pcie_abort_handler(unsigned long addr,
> unsigned int fsr, struct pt_regs *regs)
> {
> unsigned long pc = instruction_pointer(regs);
> unsigned long instr = *(unsigned long *)pc;
> int reg = (instr >> 12) & 15;
>
> /*
> * If the instruction being executed was a read,
> * make it look like it read all-ones.
> */
> if ((instr & 0x0c100000) == 0x04100000) {
> unsigned long val;
>
> if (instr & 0x00400000)
> val = 255;
> else
> val = -1;
>
> regs->uregs[reg] = val;
> regs->ARM_pc += 4;
> return 0;
> }
>
> if ((instr & 0x0e100090) == 0x00100090) {
> regs->uregs[reg] = -1;
> regs->ARM_pc += 4;
> return 0;
> }
>
> return 1;
> }
>
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
_______________________________________________
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:[~2019-12-13 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 0:32 imx6 and keystone PCIe abort handling Bjorn Helgaas
2019-12-13 0:32 ` Bjorn Helgaas
2019-12-13 0:51 ` Russell King - ARM Linux admin [this message]
2019-12-13 0:51 ` Russell King - ARM Linux admin
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=20191213005109.GP25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew.murray@arm.com \
--cc=helgaas@kernel.org \
--cc=hongxing.zhu@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=m-karicheri2@ti.com \
/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.