From: Lu Baolu <baolu.lu@linux.intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: baolu.lu@linux.intel.com, "Longpeng (Mike,
Cloud Infrastructure Service Product Dept.)"
<longpeng2@huawei.com>,
dwmw2@infradead.org, joro@8bytes.org, will@kernel.org,
iommu@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
chenjiashang@huawei.com
Subject: Re: A problem of Intel IOMMU hardware ？
Date: Thu, 18 Mar 2021 10:58:30 +0800 [thread overview]
Message-ID: <87a5f90a-d1ea-fe7a-2577-fdfdf25f8fd7@linux.intel.com> (raw)
In-Reply-To: <20210317091820.5f4ab69e@omen.home.shazbot.org>
Hi Alex,
On 3/17/21 11:18 PM, Alex Williamson wrote:
>>> {MAP, 0x0, 0xc0000000}, --------------------------------- (b)
>>> use GDB to pause at here, and then DMA read IOVA=0,
>> IOVA 0 seems to be a special one. Have you verified with other addresses
>> than IOVA 0?
> It is??? That would be a problem.
>
No problem from hardware point of view as far as I can see. Just
thought about software might handle it specially.
Best regards,
baolu
WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: chenjiashang@huawei.com, dwmw2@infradead.org,
LKML <linux-kernel@vger.kernel.org>,
iommu@lists.linux-foundation.org,
"Gonglei \(Arei\)" <arei.gonglei@huawei.com>,
"Longpeng \(Mike,
Cloud Infrastructure Service Product Dept.\)"
<longpeng2@huawei.com>,
will@kernel.org
Subject: Re: A problem of Intel IOMMU hardware ？
Date: Thu, 18 Mar 2021 10:58:30 +0800 [thread overview]
Message-ID: <87a5f90a-d1ea-fe7a-2577-fdfdf25f8fd7@linux.intel.com> (raw)
In-Reply-To: <20210317091820.5f4ab69e@omen.home.shazbot.org>
Hi Alex,
On 3/17/21 11:18 PM, Alex Williamson wrote:
>>> {MAP, 0x0, 0xc0000000}, --------------------------------- (b)
>>> use GDB to pause at here, and then DMA read IOVA=0,
>> IOVA 0 seems to be a special one. Have you verified with other addresses
>> than IOVA 0?
> It is??? That would be a problem.
>
No problem from hardware point of view as far as I can see. Just
thought about software might handle it specially.
Best regards,
baolu
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-03-18 3:08 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 3:16 A problem of Intel IOMMU hardware ？ Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-17 3:16 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-17 5:16 ` Lu Baolu
2021-03-17 5:16 ` Lu Baolu
2021-03-17 9:40 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-17 9:40 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-17 15:18 ` Alex Williamson
2021-03-17 15:18 ` Alex Williamson
2021-03-18 2:58 ` Lu Baolu [this message]
2021-03-18 2:58 ` Lu Baolu
2021-03-18 4:46 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-18 4:46 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-18 7:48 ` Nadav Amit
2021-03-18 7:48 ` Nadav Amit
2021-03-17 5:46 ` Nadav Amit
2021-03-17 5:46 ` Nadav Amit
2021-03-17 9:35 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-17 9:35 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-17 18:12 ` Nadav Amit
2021-03-17 18:12 ` Nadav Amit
2021-03-18 3:03 ` Lu Baolu
2021-03-18 3:03 ` Lu Baolu
2021-03-18 8:20 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-18 8:20 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-18 8:27 ` Tian, Kevin
2021-03-18 8:27 ` Tian, Kevin
2021-03-18 8:38 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-18 8:38 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-18 8:43 ` Tian, Kevin
2021-03-18 8:43 ` Tian, Kevin
2021-03-18 8:54 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-18 8:54 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-18 8:56 ` Tian, Kevin
2021-03-18 8:56 ` Tian, Kevin
2021-03-18 9:25 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-18 9:25 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-18 16:46 ` Nadav Amit
2021-03-18 16:46 ` Nadav Amit
2021-03-21 23:51 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-21 23:51 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-22 0:27 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-22 0:27 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2021-03-27 2:31 ` Lu Baolu
2021-03-27 2:31 ` Lu Baolu
2021-03-27 4:36 ` Nadav Amit
2021-03-27 4:36 ` Nadav Amit
2021-03-27 5:27 ` Lu Baolu
2021-03-27 5:27 ` Lu Baolu
2021-03-19 0:15 ` Lu Baolu
2021-03-19 0:15 ` Lu Baolu
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=87a5f90a-d1ea-fe7a-2577-fdfdf25f8fd7@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=alex.williamson@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=chenjiashang@huawei.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=will@kernel.org \
/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.