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//class
>
Le Thursday 02 April 2015 à 14:05 +0200, Michael S. Tsirkin a écrit :
> On Thu, Apr 02, 2015 at 01:15:30PM +0200, Jean Delvare wrote:
> > Le Thursday 02 April 2015 à 12:09 +0200, Michael S. Tsirkin a écrit :
> > > On Thu, Apr 02, 2015 at 11:04:16AM +0200, Jean Delvare wrote:
> > > > Le Thursday 02
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//class
VFIO also made this part of it's kernel API.
> Just use the
>
On Thu, Apr 02, 2015 at 01:15:30PM +0200, Jean Delvare wrote:
> Le Thursday 02 April 2015 à 12:09 +0200, Michael S. Tsirkin a écrit :
> > On Thu, Apr 02, 2015 at 11:04:16AM +0200, Jean Delvare wrote:
> > > Le Thursday 02 April 2015 à 01:23 -0700, Christoph Hellwig a écrit :
> > > > The class ids
Le Thursday 02 April 2015 à 12:09 +0200, Michael S. Tsirkin a écrit :
> On Thu, Apr 02, 2015 at 11:04:16AM +0200, Jean Delvare wrote:
> > Le Thursday 02 April 2015 à 01:23 -0700, Christoph Hellwig a écrit :
> > > The class ids are a hardware defintion, not a kernel API. Just use the
> > >
On Thu, Apr 02, 2015 at 11:04:16AM +0200, Jean Delvare wrote:
> Le Thursday 02 April 2015 à 01:23 -0700, Christoph Hellwig a écrit :
> > The class ids are a hardware defintion, not a kernel API. Just use the
> > definitions from libpci, or copy over the kernel header if you prefer
> > it over the
Le Thursday 02 April 2015 à 01:23 -0700, Christoph Hellwig a écrit :
> The class ids are a hardware defintion, not a kernel API. Just use the
> definitions from libpci, or copy over the kernel header if you prefer
> it over the libpci definutions.
I agree with Christoph, such defines would
The class ids are a hardware defintion, not a kernel API. Just use the
definitions from libpci, or copy over the kernel header if you prefer
it over the libpci definutions.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, Apr 02, 2015 at 09:44:24AM +0200, Jean Delvare wrote:
> It could be that a small subset of pci_ids.h could be shared with
> user-space. I'm thinking of classes, because that list is short and
> stable, so we can give some stability guarantees. But I don't know if
> the user-space projects
Hi Michael, Bjorn and all,
On Sun, 29 Mar 2015 15:36:55 +0200, Michael S. Tsirkin wrote:
> The macros in pci_ids.h are pretty useful for userspace
> using the pci sysfs interface, e.g. to decode class
> device and vendor sysfs files.
>
> At the moment userspace is forced to duplicate these
Le Thursday 02 April 2015 à 01:23 -0700, Christoph Hellwig a écrit :
The class ids are a hardware defintion, not a kernel API. Just use the
definitions from libpci, or copy over the kernel header if you prefer
it over the libpci definutions.
I agree with Christoph, such defines would better
On Thu, Apr 02, 2015 at 09:44:24AM +0200, Jean Delvare wrote:
It could be that a small subset of pci_ids.h could be shared with
user-space. I'm thinking of classes, because that list is short and
stable, so we can give some stability guarantees. But I don't know if
the user-space projects you
The class ids are a hardware defintion, not a kernel API. Just use the
definitions from libpci, or copy over the kernel header if you prefer
it over the libpci definutions.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
Hi Michael, Bjorn and all,
On Sun, 29 Mar 2015 15:36:55 +0200, Michael S. Tsirkin wrote:
The macros in pci_ids.h are pretty useful for userspace
using the pci sysfs interface, e.g. to decode class
device and vendor sysfs files.
At the moment userspace is forced to duplicate these macros
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.
Just use the
On Thu, Apr 02, 2015 at 11:04:16AM +0200, Jean Delvare wrote:
Le Thursday 02 April 2015 à 01:23 -0700, Christoph Hellwig a écrit :
The class ids are a hardware defintion, not a kernel API. Just use the
definitions from libpci, or copy over the kernel header if you prefer
it over the libpci
On Thu, Apr 02, 2015 at 01:15:30PM +0200, Jean Delvare wrote:
Le Thursday 02 April 2015 à 12:09 +0200, Michael S. Tsirkin a écrit :
On Thu, Apr 02, 2015 at 11:04:16AM +0200, Jean Delvare wrote:
Le Thursday 02 April 2015 à 01:23 -0700, Christoph Hellwig a écrit :
The class ids are a
Le Thursday 02 April 2015 à 12:09 +0200, Michael S. Tsirkin a écrit :
On Thu, Apr 02, 2015 at 11:04:16AM +0200, Jean Delvare wrote:
Le Thursday 02 April 2015 à 01:23 -0700, Christoph Hellwig a écrit :
The class ids are a hardware defintion, not a kernel API. Just use the
definitions from
Le Thursday 02 April 2015 à 14:05 +0200, Michael S. Tsirkin a écrit :
On Thu, Apr 02, 2015 at 01:15:30PM +0200, Jean Delvare wrote:
Le Thursday 02 April 2015 à 12:09 +0200, Michael S. Tsirkin a écrit :
On Thu, Apr 02, 2015 at 11:04:16AM +0200, Jean Delvare wrote:
Le Thursday 02 April
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
On Sun, Mar 29, 2015 at 10:59:45AM -0700, Joe Perches wrote:
> On Sun, 2015-03-29 at 15:36 +0200, Michael S. Tsirkin wrote:
> > The macros in pci_ids.h are pretty useful for userspace
> > using the pci sysfs interface, e.g. to decode class
> > device and vendor sysfs files.
> >
> > At the moment
On Sun, Mar 29, 2015 at 10:59:45AM -0700, Joe Perches wrote:
On Sun, 2015-03-29 at 15:36 +0200, Michael S. Tsirkin wrote:
The macros in pci_ids.h are pretty useful for userspace
using the pci sysfs interface, e.g. to decode class
device and vendor sysfs files.
At the moment userspace
On Mar 29 Michael S. Tsirkin wrote:
> The macros in pci_ids.h are pretty useful for userspace
> using the pci sysfs interface, e.g. to decode class
> device and vendor sysfs files.
>
> At the moment userspace is forced to duplicate these macros (e.g. QEMU does
> this, so does gpxe, seabios, etc),
On Sun, 2015-03-29 at 15:36 +0200, Michael S. Tsirkin wrote:
> The macros in pci_ids.h are pretty useful for userspace
> using the pci sysfs interface, e.g. to decode class
> device and vendor sysfs files.
>
> At the moment userspace is forced to duplicate these macros (e.g. QEMU does
> this, so
The macros in pci_ids.h are pretty useful for userspace
using the pci sysfs interface, e.g. to decode class
device and vendor sysfs files.
At the moment userspace is forced to duplicate these macros (e.g. QEMU does
this, so does gpxe, seabios, etc), it is better to export them in
The macros in pci_ids.h are pretty useful for userspace
using the pci sysfs interface, e.g. to decode class
device and vendor sysfs files.
At the moment userspace is forced to duplicate these macros (e.g. QEMU does
this, so does gpxe, seabios, etc), it is better to export them in
On Sun, 2015-03-29 at 15:36 +0200, Michael S. Tsirkin wrote:
The macros in pci_ids.h are pretty useful for userspace
using the pci sysfs interface, e.g. to decode class
device and vendor sysfs files.
At the moment userspace is forced to duplicate these macros (e.g. QEMU does
this, so does
On Mar 29 Michael S. Tsirkin wrote:
The macros in pci_ids.h are pretty useful for userspace
using the pci sysfs interface, e.g. to decode class
device and vendor sysfs files.
At the moment userspace is forced to duplicate these macros (e.g. QEMU does
this, so does gpxe, seabios, etc), it is
28 matches
Mail list logo
