From: Christoph Hellwig <hch@infradead.org>
To: Jian-Hong Pan <jian-hong@endlessm.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org,
Linux Upstreaming Team <linux@endlessm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iommu/intel-iommu: set as DUMMY_DEVICE_DOMAIN_INFO if no IOMMU
Date: Wed, 5 Feb 2020 23:32:21 -0800 [thread overview]
Message-ID: <20200206073221.GA27797@infradead.org> (raw)
In-Reply-To: <CAPpJ_efn0jwHf8rWjBm0=BwrFd=z7MATWkNsqNfHuyrn4wAt+w@mail.gmail.com>
On Thu, Feb 06, 2020 at 03:25:48PM +0800, Jian-Hong Pan wrote:
> Here is the original issue: There are more and more laptops equipped
> with Intel Rapid Storage Technology (RST) feature. That makes the
> NVMe SSD hidden and as the cache. However, there is no built in
> driver for it. So, Daniel prepares a driver called intel-nvme-remap
> [1] to remap and show up the hidden NVMe SSD and make it as a normal
> SSD. The driver is developed and refers to
> drivers/pci/controller/vmd.c.
>
> Recently, we get a laptop with Intel RST feature enabled in BIOS and
> two NVMe SSDs after the RAID bus controller. So, those two NVMe SSDs
> are hidden by Intel RST. Then, intel-nvme-remap is going to remap and
> show up the NVMe SSDs. But it hits two issues:
So you are using a driver that has been rejeced because it and the
Intel magic it tries to work around are completely broken, and then
complain it doesn't work? There is no reason to hack up the intel-iommu
to work around your broken patched kernel then.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-02-06 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 9:10 [PATCH] iommu/intel-iommu: set as DUMMY_DEVICE_DOMAIN_INFO if no IOMMU Jian-Hong Pan
2020-02-04 6:11 ` Lu Baolu
2020-02-04 9:25 ` Jian-Hong Pan
2020-02-05 1:28 ` Lu Baolu
2020-02-05 10:06 ` Jian-Hong Pan
2020-02-06 7:25 ` Jian-Hong Pan
2020-02-06 7:32 ` Christoph Hellwig [this message]
2020-02-06 10:49 ` Lu Baolu
2020-02-07 7:32 ` Jian-Hong Pan
2020-02-08 6:29 ` Lu Baolu
2020-02-11 9:26 ` Daniel Drake
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=20200206073221.GA27797@infradead.org \
--to=hch@infradead.org \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jian-hong@endlessm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.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;
as well as URLs for NNTP newsgroup(s).