From: Lu Baolu <baolu.lu@linux.intel.com>
To: Qian Cai <cai@lca.pw>
Cc: kevin.tian@intel.com, ashok.raj@intel.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
jacob.jun.pan@intel.com, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v2 1/1] iommu/vt-d: Add Kconfig option to enable/disable scalable mode
Date: Tue, 12 Nov 2019 13:48:12 +0800 [thread overview]
Message-ID: <fefea7dd-8cde-889d-0883-7d94b8d85f20@linux.intel.com> (raw)
In-Reply-To: <77EC0C76-22C1-4982-8E0A-9AD7223B3410@lca.pw>
Hi,
On 11/11/19 10:05 PM, Qian Cai wrote:
>
>
>> On Nov 11, 2019, at 12:23 AM, Lu Baolu <baolu.lu@linux.intel.com> wrote:
>>
>> The scalable mode is defined in VT-d 3.0. The scalable mode capability
>> could be checked by reading /sys/devices/virtual/iommu/dmar*/intel-
>> iommu/ecap. It's currently not friendly for reading. You need to decode
>> it according to the spec.
>
> This looks like some perfect information to put in the Kconfig description.
>
Okay. Will add it in the next version.
Best regards,
baolu
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Qian Cai <cai@lca.pw>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
David Woodhouse <dwmw2@infradead.org>,
kevin.tian@intel.com, ashok.raj@intel.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
jacob.jun.pan@intel.com
Subject: Re: [PATCH v2 1/1] iommu/vt-d: Add Kconfig option to enable/disable scalable mode
Date: Tue, 12 Nov 2019 13:48:12 +0800 [thread overview]
Message-ID: <fefea7dd-8cde-889d-0883-7d94b8d85f20@linux.intel.com> (raw)
In-Reply-To: <77EC0C76-22C1-4982-8E0A-9AD7223B3410@lca.pw>
Hi,
On 11/11/19 10:05 PM, Qian Cai wrote:
>
>
>> On Nov 11, 2019, at 12:23 AM, Lu Baolu <baolu.lu@linux.intel.com> wrote:
>>
>> The scalable mode is defined in VT-d 3.0. The scalable mode capability
>> could be checked by reading /sys/devices/virtual/iommu/dmar*/intel-
>> iommu/ecap. It's currently not friendly for reading. You need to decode
>> it according to the spec.
>
> This looks like some perfect information to put in the Kconfig description.
>
Okay. Will add it in the next version.
Best regards,
baolu
next prev parent reply other threads:[~2019-11-12 5:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 3:40 [PATCH v2 1/1] iommu/vt-d: Add Kconfig option to enable/disable scalable mode Lu Baolu
2019-11-09 3:40 ` Lu Baolu
2019-11-09 3:59 ` Qian Cai
2019-11-09 3:59 ` Qian Cai
2019-11-11 1:27 ` Lu Baolu
2019-11-11 1:27 ` Lu Baolu
2019-11-11 2:00 ` Qian Cai
2019-11-11 2:00 ` Qian Cai
2019-11-11 2:17 ` Lu Baolu
2019-11-11 2:17 ` Lu Baolu
2019-11-11 2:58 ` Qian Cai
2019-11-11 2:58 ` Qian Cai
2019-11-11 5:20 ` Lu Baolu
2019-11-11 5:20 ` Lu Baolu
2019-11-11 14:05 ` Qian Cai
2019-11-11 14:05 ` Qian Cai
2019-11-12 5:48 ` Lu Baolu [this message]
2019-11-12 5:48 ` 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=fefea7dd-8cde-889d-0883-7d94b8d85f20@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=cai@lca.pw \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=kevin.tian@intel.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 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.