search for: cs01

...atch 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 ... 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 m...

...atch 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 ... 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 m...

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 ++++++++...

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 ++++++++...

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 comm...

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 comm...

...IV/AIS) is not restricted by the >> architecture. > > The size of vcdev->indicators is restricted or defined by the virtio > specification. Please have a look at '4.3.2.6.1 Setting Up Classic Queue > Indicators' here: > https://docs.oasis-open.org/virtio/virtio/v1.1/cs01/virtio-v1.1-cs01.html#x1-1630002 > > Since with Linux on s390 only 64 bit is supported, both the sizes are in > line with the specification. Using u64 would semantically match the spec > better, modulo pre virtio 1.0 which ain't specified. I did not want to > do changes that are...

...IV/AIS) is not restricted by the >> architecture. > > The size of vcdev->indicators is restricted or defined by the virtio > specification. Please have a look at '4.3.2.6.1 Setting Up Classic Queue > Indicators' here: > https://docs.oasis-open.org/virtio/virtio/v1.1/cs01/virtio-v1.1-cs01.html#x1-1630002 > > Since with Linux on s390 only 64 bit is supported, both the sizes are in > line with the specification. Using u64 would semantically match the spec > better, modulo pre virtio 1.0 which ain't specified. I did not want to > do changes that are...

Is there any documentation on what machine interface (mi) commands are implemented in lldb-mi, and how compatible those commands are with gdb's mi? I'm asking for this project: https://github.com/cs01/gdbgui -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170310/667d44df/attachment.html>

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 +- lspc...

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 +- lspc...

...t; architecture. >>> >>> The size of vcdev->indicators is restricted or defined by the virtio >>> specification. Please have a look at '4.3.2.6.1 Setting Up Classic Queue >>> Indicators' here: >>> https://docs.oasis-open.org/virtio/virtio/v1.1/cs01/virtio-v1.1-cs01.html#x1-1630002 >>> >>> Since with Linux on s390 only 64 bit is supported, both the sizes are in >>> line with the specification. Using u64 would semantically match the spec >>> better, modulo pre virtio 1.0 which ain't specified. I did not w...

...t; architecture. >>> >>> The size of vcdev->indicators is restricted or defined by the virtio >>> specification. Please have a look at '4.3.2.6.1 Setting Up Classic Queue >>> Indicators' here: >>> https://docs.oasis-open.org/virtio/virtio/v1.1/cs01/virtio-v1.1-cs01.html#x1-1630002 >>> >>> Since with Linux on s390 only 64 bit is supported, both the sizes are in >>> line with the specification. Using u64 would semantically match the spec >>> better, modulo pre virtio 1.0 which ain't specified. I did not w...

...ing the device by setting an incorrect hdr_len." There is a plan to support this feature in our emulated device. A device of SolidRun offers this feature bit. They claim this feature will save the device a few cycles for every GSO packet. Link: https://docs.oasis-open.org/virtio/virtio/v1.2/cs01/virtio-v1.2-cs01.html#x1-230006x3 Signed-off-by: Jiri Pirko <jiri at nvidia.com> Reviewed-by: Parav Pandit <parav at nvidia.com> Reviewed-by: Alvaro Karsz <alvaro.karsz at solid-run.com> Acked-by: Michael S. Tsirkin <mst at redhat.com> --- v2->v3: - changed the first para...

...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? 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

...12:31:08PM +0100, Gerd Hoffmann 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 com...

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 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...

...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? 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

...12:31:08PM +0100, Gerd Hoffmann 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 com...

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 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...