From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Alex Williamson
<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] iommu/vt-d: Report superpage support in sysfs
Date: Mon, 3 Aug 2015 16:30:29 +0200 [thread overview]
Message-ID: <20150803143029.GD20968@8bytes.org> (raw)
In-Reply-To: <20150714212459.11515.71211.stgit-GCcqpEzw8uZBDLzU/O5InQ@public.gmane.org>
On Tue, Jul 14, 2015 at 03:25:04PM -0600, Alex Williamson wrote:
> We already have the VT-d capability register printed raw, but it
> typically involves a trip to the code or the spec to figure out
> whether superpages are supported. Make this easier with "2M_pages"
> and "1G_pages" sysfs entries that clearly report Y/N.
>
> Signed-off-by: Alex Williamson <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
> drivers/iommu/intel-iommu.c | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
Can we make this a generic entry for all iommu types and export a
pagesize bitmap instead?
Joerg
next prev parent reply other threads:[~2015-08-03 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 21:24 [PATCH 0/2] iommu/vt-d: Additional sysfs entries Alex Williamson
[not found] ` <20150714211624.11515.25204.stgit-GCcqpEzw8uZBDLzU/O5InQ@public.gmane.org>
2015-07-14 21:24 ` [PATCH 1/2] iommu/vt-d: Report domain usage in sysfs Alex Williamson
[not found] ` <20150714212448.11515.38240.stgit-GCcqpEzw8uZBDLzU/O5InQ@public.gmane.org>
2015-08-03 14:31 ` Joerg Roedel
2015-07-14 21:25 ` [PATCH 2/2] iommu/vt-d: Report superpage support " Alex Williamson
[not found] ` <20150714212459.11515.71211.stgit-GCcqpEzw8uZBDLzU/O5InQ@public.gmane.org>
2015-08-03 14:30 ` Joerg Roedel [this message]
[not found] ` <20150803143029.GD20968-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-08-03 14:35 ` David Woodhouse
2015-08-03 15:09 ` Alex Williamson
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=20150803143029.GD20968@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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