From: Alex Williamson <alex.williamson@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org, dwmw2@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iommu/vt-d: Report superpage support in sysfs
Date: Mon, 03 Aug 2015 09:09:00 -0600 [thread overview]
Message-ID: <1438614540.13460.112.camel@redhat.com> (raw)
In-Reply-To: <20150803143029.GD20968@8bytes.org>
On Mon, 2015-08-03 at 16:30 +0200, Joerg Roedel wrote:
> 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@redhat.com>
> > ---
> > 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?
Are you suggesting a bitmap in order to have a consistent interface,
independently implemented by each IOMMU driver, or are you suggesting a
common interface implemented by iommu_ops.pgsize_bitmap? The latter is
pretty well broken already. It can't represent different IOMMU hardware
units having different capabilities, and it's broken by drivers like
intel-iommu that don't expose native hardware page sizes, but anything
that can be broken down into native hardware page size, so ~(4k-1).
Programatically, a bitmap is a concise way to expose multiple page
sizes, but for human consumption, it's not an ideal solution. Thanks,
Alex
prev parent reply other threads:[~2015-08-03 15:09 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
2015-07-14 21:24 ` [PATCH 1/2] iommu/vt-d: Report domain usage in sysfs Alex Williamson
2015-08-03 14:31 ` Joerg Roedel
2015-07-14 21:25 ` [PATCH 2/2] iommu/vt-d: Report superpage support " Alex Williamson
2015-08-03 14:30 ` Joerg Roedel
2015-08-03 14:35 ` David Woodhouse
2015-08-03 15:09 ` Alex Williamson [this message]
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=1438614540.13460.112.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--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