search for: 690004

...nd 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 ... 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? Also note: [root at fedora ~]# ~kraxel/projects/pciutils/lspci -vvsa 00:0a.0 Communication controller: Red Hat, Inc Virtio console [ ... ] Capabilities: [64] VirtIO: Notify BAR=2 offset=00003000 size=00400000 multiplier=00010000 [ ... ] Why...

...nd 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 ... 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? Also note: [root at fedora ~]# ~kraxel/projects/pciutils/lspci -vvsa 00:0a.0 Communication controller: Red Hat, Inc Virtio console [ ... ] Capabilities: [64] VirtIO: Notify BAR=2 offset=00003000 size=00400000 multiplier=00010000 [ ... ] Why...

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 | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ls-caps.c | 9 ++++++++- lspci.h | 4 ++++ 4...

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 | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ls-caps.c | 9 ++++++++- lspci.h | 4 ++++ 4...

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 patch needs an update too (because I've made it decode the broken qemu capabilities). Will come as separate mail with proper commit message in a moment. > I...

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 patch needs an update too (because I've made it decode the broken qemu capabilities). Will come as separate mail with proper commit message in a moment. > I...

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 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ls-caps.c | 2 +- lspci.h | 4 +++ 4 files c...

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 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ls-caps.c | 2 +- lspci.h | 4 +++ 4 files c...

...:-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 ... > > 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! I sent patches to fix this all up. You can try my qemu and linux virtio-net branches now, they should be spec compliant. -- MST

...n wrote: > 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 patch needs an update too (because I've made it decode the > broken qemu capabilities). Will come as separate mail with proper &...

...: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 capabilities to lspci. > > I like the patch, except for a couple of details: > > (1) Please follow the coding style of the rest of pciutils. I've tried. What specifically doesn't match? > (2) You assume that...

...:-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 ... > > 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! I sent patches to fix this all up. You can try my qemu and linux virtio-net branches now, they should be spec compliant. -- MST

...n wrote: > 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 patch needs an update too (because I've made it decode the > broken qemu capabilities). Will come as separate mail with proper &...

...: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 capabilities to lspci. > > I like the patch, except for a couple of details: > > (1) Please follow the coding style of the rest of pciutils. I've tried. What specifically doesn't match? > (2) You assume that...

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 coding style of the rest of pciutils. (2) You assume that PCI_CAP_ID_VNDR of all Redhat devices contains virtio, but the comment nearby refers...

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 coding style of the rest of pciutils. (2) You assume that PCI_CAP_ID_VNDR of all Redhat devices contains virtio, but the comment nearby refers...

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 -vxxx) of a virtio device as a test case? Martin

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 -vxxx) of a virtio device as a test case? Martin

As described below, external network connections to the campus of the University of Wisconsin - Madison will be either inaccessible or slow from 20:00 CST 2000/01/03 until 01:00 CST 2000/01/04. CST is our local time zone: Central Standard Time in North America. These local times correspond to 04:00 - 07:00 GMT Tuesday 2000/01/04. This planned outage will affect the r-project.org, omegahat.org,

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