similar to: [pciutils patch] add virtio vendor capability support

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 76

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 76

Hi, > BTW: is there a tool (or pciutils patch) which can decode the virtio > capabilities? Searched for a patch today, and all google found me was this mail asking for one :-o So I went ahead and coded one up. Attached. While hacking it up I've noticed spec doesn't match reality. The "Virtio Structure PCI Capabilities" section here ...

Hi, > BTW: is there a tool (or pciutils patch) which can decode the virtio > capabilities? Searched for a patch today, and all google found me was this mail asking for one :-o So I went ahead and coded one up. Attached. While hacking it up I've noticed spec doesn't match reality. The "Virtio Structure PCI Capabilities" section here ...

Hello! > virtio uses vendor-specific capabilities to specify the location of > the virtio register ranges. The specification can be found here: > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > This patch adds support for decoding these capabilities to lspci. I like the patch, except for a couple of details: (1) Please follow the

Hello! > virtio uses vendor-specific capabilities to specify the location of > the virtio register ranges. The specification can be found here: > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > This patch adds support for decoding these capabilities to lspci. I like the patch, except for a couple of details: (1) Please follow the

On Mi, 2015-01-21 at 15:57 +0100, Martin Mares wrote: > Hello! > > > virtio uses vendor-specific capabilities to specify the location of > > the virtio register ranges. The specification can be found here: > > > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > > > This patch adds support for decoding these

On Mi, 2015-01-21 at 15:57 +0100, Martin Mares wrote: > Hello! > > > virtio uses vendor-specific capabilities to specify the location of > > the virtio register ranges. The specification can be found here: > > > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > > > This patch adds support for decoding these

Hi! > virtio uses vendor-specific capabilities to specify the location of > the virtio register ranges. The specification can be found here: > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > This patch adds support for decoding these capabilities to lspci. Thanks, applied. One more request: could you please provide a hexdump (lspci

Hi! > virtio uses vendor-specific capabilities to specify the location of > the virtio register ranges. The specification can be found here: > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > This patch adds support for decoding these capabilities to lspci. Thanks, applied. One more request: could you please provide a hexdump (lspci

Hi, > > While hacking it up I've noticed spec doesn't match reality. The > > "Virtio Structure PCI Capabilities" section here ... > > > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > > > ... doesn't match what qemu is doing. Huh? > > Thanks a lot for the report, and the tool! pciutils

Hi, > > While hacking it up I've noticed spec doesn't match reality. The > > "Virtio Structure PCI Capabilities" section here ... > > > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > > > ... doesn't match what qemu is doing. Huh? > > Thanks a lot for the report, and the tool! pciutils

On Do, 2015-01-22 at 22:46 +0100, Martin Mares wrote: > > Attached is a dump of a virtio-net device (both verbose=2 and hex). > > Thanks! > > I have cleaned up the code a little, could you please check that > it still works for you? Works fine. cheers, Gerd

> Attached is a dump of a virtio-net device (both verbose=2 and hex). Thanks! I have cleaned up the code a little, could you please check that it still works for you? Martin

On Do, 2015-01-22 at 10:10 +0100, Martin Mares wrote: > lspci -vxxx Attached is a dump of a virtio-net device (both verbose=2 and hex). cheers, Gerd -------------- next part -------------- 00:09.0 Ethernet controller: Red Hat, Inc Virtio network device Subsystem: Red Hat, Inc Virtio network device Physical Slot: 9 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-

On Do, 2015-01-22 at 10:10 +0100, Martin Mares wrote: > lspci -vxxx Attached is a dump of a virtio-net device (both verbose=2 and hex). cheers, Gerd -------------- next part -------------- 00:09.0 Ethernet controller: Red Hat, Inc Virtio network device Subsystem: Red Hat, Inc Virtio network device Physical Slot: 9 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-

On Thu, Jan 15, 2015 at 10:18:18PM +0100, Gerd Hoffmann wrote: > Hi, > > > QEMU side is still undergoing polishing, but is already testable. > > Looked art the qemu side for now, commenting here due to qemu patches > not being posted to the list yet (guess that is at least partly already > on your todo list): Absolutely. > * Both legacy and modern should be

On Thu, Jan 15, 2015 at 10:18:18PM +0100, Gerd Hoffmann wrote: > Hi, > > > QEMU side is still undergoing polishing, but is already testable. > > Looked art the qemu side for now, commenting here due to qemu patches > not being posted to the list yet (guess that is at least partly already > on your todo list): Absolutely. > * Both legacy and modern should be

Hi all, It''s my first xenification and I''m affronting to a lot of erreurs : This is a recapitulation to my manipulation : I copied all my / into the img file (whithout /proc /sys /boot) My machine to virtualise is a Red Hat Enterprise Linux ES release 4 (Nahant Update 7) (2.6.9-78.0.1.ELsmp) I downloaded kernel-xenU-2.6.9-42.0.3.EL.xs0.4.0.263.i686.rpm and

Hello, writing some R code to cleanse a data set, if the following set of symbols are identified then perform some actions. trying to write the minimum code to do this. tname = "VIX" checkticker = c("VIX", "TYX", "TNX", "IRX") if (tname == checkticker) { //perform some operations } result i get is > tname == checkticker