linux-kernel - Re: [PATCH 00/86] pci: export pci

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 02 Apr 2015 08:34:19 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	"Michael S. Tsirkin" <mst@...hat.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Jean Delvare <jdelvare@...e.de>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Dave Jones <davej@...hat.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH 00/86] pci: export pci_ids.h and related cleanups

On Thu, 2015-04-02 at 14:09 +0200, Michael S. Tsirkin wrote:
> On Thu, Apr 02, 2015 at 01:23:06AM -0700, Christoph Hellwig wrote:
> > The class ids are a hardware defintion, not a kernel API.
> 
> It's part of the API, it's used to decode values in this sysfs file:
> /sys/bus/pci/devices/<address>/class
> VFIO also made this part of it's kernel API.

vfio-pci does expose PCI config space, but it also exposes memory mapped
and io port mapped regions of the device.  Do we consider the memory
mapped config space of every device that can be exposed through vfio to
be part of the kernel API?  I don't think so.  PCI config space is
obviously more standardized and vfio-pci plays a greater role in
intercepting and interacting with standardized portions, but we don't
really care where userspace gets their definitions for config space
offsets.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/