From: Lu Baolu <baolu.lu@linux.intel.com>
To: "Jim,Yan" <jimyan@baidu.com>, Jerry Snitselaar <jsnitsel@redhat.com>
Cc: baolu.lu@linux.intel.com,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 答复: 答复: 答复: 答复: 答复: [PATCH] iommu/vt-d: Don't reject nvme host due to scope mismatch
Date: Wed, 25 Dec 2019 10:37:45 +0800 [thread overview]
Message-ID: <f5ceee32-4a21-a09c-1e1b-d3f0539ace4c@linux.intel.com> (raw)
In-Reply-To: <eccacec618c04a58be66809a541a95bf@baidu.com>
Hi,
On 12/25/19 10:05 AM, Jim,Yan wrote:
> Hi,
>
>> -----邮件原件-----
>> 发件人: Lu Baolu [mailto:baolu.lu@linux.intel.com]
>> 发送时间: 2019年12月25日 10:01
>> 收件人: Jim,Yan <jimyan@baidu.com>; Jerry Snitselaar <jsnitsel@redhat.com>
>> 抄送: iommu@lists.linux-foundation.org; linux-kernel@vger.kernel.org
>> 主题: Re: 答复: 答复: 答复: 答复: [PATCH] iommu/vt-d: Don't reject nvme
>> host due to scope mismatch
>>
>> Hi,
>>
>> On 2019/12/25 9:52, Jim,Yan wrote:
>>> Hi,
>>>
>>>> -----邮件原件-----
>>>> 发件人: Lu Baolu [mailto:baolu.lu@linux.intel.com]
>>>> 发送时间: 2019年12月24日 19:27
>>>> 收件人: Jim,Yan <jimyan@baidu.com>; Jerry Snitselaar
>>>> <jsnitsel@redhat.com>
>>>> 抄送: iommu@lists.linux-foundation.org; linux-kernel@vger.kernel.org
>>>> 主题: Re: 答复: 答复: 答复: [PATCH] iommu/vt-d: Don't reject nvme host
>> due to
>>>> scope mismatch
>>>>
>>>> Hi,
>>>>
>>>> On 2019/12/24 16:18, Jim,Yan wrote:
>>>>>>>> For both cases, a quirk flag seems to be more reasonable, so that
>>>>>>>> unrelated devices will not be impacted.
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> baolu
>>>>>>> Hi Baolu,
>>>>>>> Thanks for your advice. And I modify the patch as follow.
>>>>>> I just posted a patch for both NTG and NVME cases. Can you please
>>>>>> take a
>>>> look?
>>>>>> Does it work for you?
>>>>>>
>>>>>> Best regards,
>>>>>> baolu
>>>>>>
>>>>> I have tested your patch. It does work for me. But I prefer my
>>>>> second version,
>>>> it is more flexible, and may use for similar unknown devices.
>>>>>
>>>>
>>>> I didn't get your point. Do you mind explaining why it's more flexible?
>>>>
>>>> Best regards,
>>>> Baolu
>>> For example, an unknown device has a normal PCI header and bridge scope
>> and a class of PCI_CLASS_BRIDGE_PCI.
>>> These devices do have a class of PCI_BASE_CLASS_BRIDGE in common.
>>
>> This is not a common case. It's only for devices on the marketing and hard for
>> the VT-d users to get it fixed in the OEM firmware.
>>
>> Best regards,
>> Baolu
>
> Got it. Then I am OK with this patch. I have tested it yesterday. It does work for me.
> Thanks.
Can I add your Tested-by?
Best regards,
baolu
next prev parent reply other threads:[~2019-12-25 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 3:24 答复: 答复: [PATCH] iommu/vt-d: Don't reject nvme host due to scope mismatch Jim,Yan
2019-12-24 6:27 ` Lu Baolu
2019-12-24 8:18 ` 答复: " Jim,Yan
2019-12-24 11:26 ` Lu Baolu
2019-12-25 1:52 ` 答复: " Jim,Yan
2019-12-25 2:00 ` Lu Baolu
2019-12-25 2:05 ` 答复: " Jim,Yan
2019-12-25 2:37 ` Lu Baolu [this message]
2019-12-25 2:40 ` 答复: " Jim,Yan
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=f5ceee32-4a21-a09c-1e1b-d3f0539ace4c@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jimyan@baidu.com \
--cc=jsnitsel@redhat.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox