From: Alex Williamson <alex.williamson@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jean Delvare <jdelvare@suse.de>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Dave Jones <davej@redhat.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH 00/86] pci: export pci_ids.h and related cleanups
Date: Thu, 02 Apr 2015 08:34:19 -0600 [thread overview]
Message-ID: <1427985259.5567.371.camel@redhat.com> (raw)
In-Reply-To: <20150402140519-mutt-send-email-mst@redhat.com>
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.
prev parent reply other threads:[~2015-04-02 14:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 13:36 [PATCH 00/86] pci: export pci_ids.h and related cleanups Michael S. Tsirkin
2015-03-29 13:37 ` [PATCH 01/86] pci: export pci_ids.h Michael S. Tsirkin
2015-03-29 15:49 ` Joe Perches
2015-03-29 20:40 ` Greg KH
2015-03-30 6:48 ` Michael S. Tsirkin
2015-03-30 6:55 ` Greg KH
2015-03-30 7:15 ` Michael S. Tsirkin
2015-03-30 7:53 ` Greg KH
2015-03-30 8:31 ` Michael S. Tsirkin
2015-03-30 10:07 ` Greg KH
2015-03-30 10:46 ` Michael S. Tsirkin
2015-03-30 10:57 ` Greg KH
2015-03-30 11:19 ` Michael S. Tsirkin
2015-03-30 11:35 ` Greg KH
2015-03-30 11:41 ` Michael S. Tsirkin
2015-03-29 13:38 ` [PATCH 12/86] x86/pci/sta2x11: use uapi/linux/pci_ids.h directly Michael S. Tsirkin
2015-03-29 13:41 ` [PATCH 58/86] pci-label: " Michael S. Tsirkin
2015-03-29 13:43 ` [PATCH 77/86] linux/pci: " Michael S. Tsirkin
2015-03-29 13:43 ` [PATCH 78/86] linux/pci: drop include/linux/pci_ids.h Michael S. Tsirkin
2015-03-29 17:59 ` [PATCH 00/86] pci: export pci_ids.h and related cleanups Joe Perches
2015-03-30 6:52 ` Michael S. Tsirkin
2015-03-29 23:15 ` Stefan Richter
2015-04-02 7:44 ` Jean Delvare
2015-04-02 7:49 ` Michael S. Tsirkin
2015-04-02 8:23 ` Christoph Hellwig
2015-04-02 9:04 ` Jean Delvare
2015-04-02 10:09 ` Michael S. Tsirkin
2015-04-02 11:15 ` Jean Delvare
2015-04-02 12:05 ` Michael S. Tsirkin
2015-04-02 13:17 ` Jean Delvare
2015-04-02 12:09 ` Michael S. Tsirkin
2015-04-02 14:34 ` 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=1427985259.5567.371.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).