Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Aug 2016 06:44:13 -0700
From:      John Baldwin <jhb@freebsd.org>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r303887 - head/tools/tools/dmardump
Message-ID:  <1854803.Mj8doirhqg@ralph.baldwin.cx>
In-Reply-To: <20160810074303.GC83214@kib.kiev.ua>
References:  <201608091906.u79J65Uq058283@repo.freebsd.org> <73543582.oU1jbu7riv@ralph.baldwin.cx> <20160810074303.GC83214@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, August 10, 2016 10:43:03 AM Konstantin Belousov wrote:
> On Tue, Aug 09, 2016 at 02:22:36PM -0700, John Baldwin wrote:
> > On Tuesday, August 09, 2016 07:06:05 PM John Baldwin wrote:
> > > Author: jhb
> > > Date: Tue Aug  9 19:06:05 2016
> > > New Revision: 303887
> > > URL: https://svnweb.freebsd.org/changeset/base/303887
> > > 
> > > Log:
> > >   Add a dmardump utility to dump the VT-d context tables.
> > >   
> > >   This tool parses the ACPI DMAR table looking for DMA remapping devices.
> > >   For each device it walks the root table and any context tables
> > >   referenced to display mapping info for PCI devices.
> > >   
> > >   Note that acpidump -t already parses the info in the ACPI DMAR tables
> > >   directly.  This tool examines some of the data structures the DMAR
> > >   remapping engines use to translate DMA requests.
> > >   
> > >   Reviewed by:	kib, grehan
> > >   MFC after:	1 month
> > >   Sponsored by:	Chelsio Communications
> > >   Differential Revision:	https://reviews.freebsd.org/D7444
> > 
> > I should have mentioned that this tool only supports "normal" context
> > entry tables.  It does not (yet) support extended context entry
> > tables.  However, neither bhyve nor ACPI_DMAR create extended context
> > entry tables.
> 
> I am not aware of existence of hardware supporting the extended context
> entries.  Even Skykale E3 v5 Xeons report ECS == 0.

That's completely fair, I was just going by what was in the recent spec.
I don't think it's worth implementing until anything actually uses it
certainly.

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1854803.Mj8doirhqg>