From: John Garry <john.garry@huawei.com>
To: <Ajish.Koshy@microchip.com>
Cc: <jinpu.wang@cloud.ionos.com>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <Viswas.G@microchip.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<damien.lemoal@opensource.wdc.com>, <Niklas.Cassel@wdc.com>,
<Vasanthalakshmi.Tharmarajan@microchip.com>
Subject: Re: [PATCH] scsi: pm8001: Fix phys_to_virt() usage on dma_addr_t
Date: Tue, 7 Dec 2021 13:54:24 +0000 [thread overview]
Message-ID: <6ee6fe1b-e811-cada-0c18-78149c313358@huawei.com> (raw)
In-Reply-To: <PH0PR11MB5112E2E7D00D95F32C86677AEC6E9@PH0PR11MB5112.namprd11.prod.outlook.com>
On 07/12/2021 10:36, Ajish.Koshy@microchip.com wrote:
> Well I could see this kernel panic [ 126.843958] RIP: 0010:pm80xx_chip_smp_req+0x1d6/0x2e0 [pm80xx] with respect to existing driver on my current system x86 64bit after enabling the following 2 kernel boot arguments:
> -intel_iommu=on
> -iommu.passthrough=0
>
OK, so it seems that it was the kernel which was just not enabling the
IOMMU previously, which would be consistent with what Niklas mentioned.
Anyway, please supply reviewed-by and/or tested-by tags so that the SCSI
maintainers can pick it up.
I suppose that we should also have:
Fixes: f5860992db55 ("[SCSI] pm80xx: Added SPCv/ve specific hardware
functionalities and relevant changes in common files")
Thanks for testing,
John
next prev parent reply other threads:[~2021-12-07 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 15:35 [PATCH] scsi: pm8001: Fix phys_to_virt() usage on dma_addr_t John Garry
2021-11-29 10:46 ` Ajish.Koshy
2021-12-06 9:42 ` John Garry
2021-12-06 13:24 ` Niklas Cassel
2021-12-07 10:36 ` Ajish.Koshy
2021-12-07 13:54 ` John Garry [this message]
2021-12-09 12:04 ` Ajish.Koshy
2021-12-09 12:19 ` John Garry
2021-12-09 22:38 ` Damien Le Moal
2021-12-09 23:09 ` John Garry
2021-12-09 23:55 ` Damien Le Moal
2021-12-10 10:35 ` John Garry
2021-12-11 0:19 ` Damien Le Moal
2021-12-09 22:26 ` Damien Le Moal
2021-12-09 13:46 ` John Garry
2021-12-10 10:23 ` Ajish.Koshy
2021-12-10 10:44 ` John Garry
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=6ee6fe1b-e811-cada-0c18-78149c313358@huawei.com \
--to=john.garry@huawei.com \
--cc=Ajish.Koshy@microchip.com \
--cc=Niklas.Cassel@wdc.com \
--cc=Vasanthalakshmi.Tharmarajan@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jejb@linux.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox