similar to: [pciutils patch v2] 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 | 59

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

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

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

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

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-

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

I''ve seen this topic has been discussed a couple of times. However, I''m wondering if a method exists in rails to test a name against the reserved words listed on the wiki? Just wanted to check before I write this myself (and type in all of those names -- including PostgreSQL). To explain the application: I''ve written a project that manages ldap data. On a fresh

The model.frame function has trouble with a certain type of really long formula. Here is a test: tname <- paste('var', 1:50, sep='') tmat <- matrix(rnorm(500), ncol=50, dimnames=list(NULL, tname)) tdata <- data.frame(tmat) temp1 <- paste( paste(tname, tname, sep='='), collapse=', ') temp2 <- paste("~1 + cbind(", temp1, ")")

In the past 2 months another change occurred in the CVS code that broke my ssh-keyscan patch. Here's an updated version that tweaks the changed name (in the Kex struct) and also causes an attempt to grab an ssh2 key from an older server (without ssh2 support) to fail earlier and without an error message (Stuart Pearlman emailed me some code for this). This patch is based on the BSD CVS

llvm-dev, Thanks so much in advance for any help, tips, or advice you may be able to offer me. I'm going to try to avoid the big-picture description of the project I'm working on, and only talk about the parts that I have trouble with / currently need to implement. -- I've been starting by taking the source code from the "llvm-mc" tool, and working that down into a

LLVMers, So, I'm trying to write a pass that changes the names of the basic blocks through the use of Value, so: Value *V = *BasicBlockPtr; const Twine Tname("new_name"); V->setName(Tname); But when I run the opt and look at the IR output nothing is changed? Not sure what I'm doing wrong. Thanks. -------------- next part -------------- An HTML attachment was

I'm working on translating llvm's optimized intermediate code to another compiler's intermediate code, and I'm working on the PHI instruction. Here's an example phi instruction to help explain what I'm trying to do: %inc25 = phi i32 [ 1, %entry ], [ %inc, %for.body ] What I would want to do here is allocate some memory memory (i'm trying to use %phi1 = alloca i32,