search for: 22,21

Hi, I'm having trouble matching the symbols/color of the key to match those specifiec in the plot. Here is the code I used: xyplot(GCR+GCT ~ FRAC, data=RWF, type=c("g","p"),cex=1.2,pch=c(22,21), xlab=expression(italic("f")),ylab=expression(italic("S")), key=list(points=list(pch=c(22,21),cex=1.2), text=list(c("Targeted Deletion","Random Deletion")))) I'm, sorry if this is an apparently easy/obvious mistake on my part. With thanks Andrew h...

innetgr.. much easier.. Had a look for the user section but didn't find it in my 15 seconds of looking.. --- access.c 2003-07-30 16:12:27.000000000 +1000 +++ ../rsync-2.6.0-Linux/access.c 2004-02-01 23:21:12.000000000 +1100 @@ -22,10 +22,21 @@ */ #include "rsync.h" +#include <netdb.h> static int match_hostname(char *host, char *tok) { + char *netgroup; + + if(strlen(tok)>1){ + if(tok[0]=='@'){ + netgroup=tok+1; + if(inne...

...])+2)){ abline(h=i-1) } for(i in 1:20){ if(datenbankdaten[i,2]>=datenbankdaten[i,3]) farbe="red" else farbe="green" arrows(i,datenbankdaten[i,2],i,datenbankdaten[i,3],col=farbe,length=0,lwd=1. 5) points(i,datenbankdaten[i,2],pch=22,col="light blue",bg="light blue",cex=1.7) points(i,datenbankdaten[i,3],pch=21,col="grey",bg="grey",cex=1.5) } for(i in 1:20){ if(datenbankdaten[i,2]>datenbankdaten[i,3]) #dreieck nach oben points(i,date...

...right (c) 2014, NVIDIA CORPORATION. All rights reserved. + * Copyright (c) 2014-2016, NVIDIA CORPORATION. All rights reserved. * * Permission is hereby granted, free of charge, to any person obtaining a * copy of this software and associated documentation files (the "Software"), @@ -22,21 +22,14 @@ #include "priv.h" #include "gf100.h" -#include <core/memory.h> - -static void -gk20a_fb_init(struct nvkm_fb *fb) -{ - struct nvkm_device *device = fb->subdev.device; - nvkm_wr32(device, 0x100cc8, nvkm_memory_addr(fb->mmu_wr) >> 8); - nvkm_wr32(...

...* @maxlen: length of the memory to map + * @offset: map memory at the given offset in BAR + * @maxlen: max length of the memory to map * * Using this function you will get a __iomem address to your device BAR. * You can access it using ioread*() and iowrite*(). These functions hide @@ -21,16 +22,21 @@ * you expect from them in the correct way. * * @maxlen specifies the maximum length to map. If you want to get access to - * the complete BAR without checking for its length first, pass %0 here. + * the complete BAR from offset to the end, pass %0 here. * */ -void __iomem *pci_iomap(s...

...* @maxlen: length of the memory to map + * @offset: map memory at the given offset in BAR + * @maxlen: max length of the memory to map * * Using this function you will get a __iomem address to your device BAR. * You can access it using ioread*() and iowrite*(). These functions hide @@ -21,16 +22,21 @@ * you expect from them in the correct way. * * @maxlen specifies the maximum length to map. If you want to get access to - * the complete BAR without checking for its length first, pass %0 here. + * the complete BAR from offset to the end, pass %0 here. * */ -void __iomem *pci_iomap(s...

After observing random crashes on Tegra devices when patch "fb/gf100: defer DMA mapping of scratch page to oneinit() hook" was applied, I noticed that moving the 100c10 page allocation to the oneinit() hook resulted in that page being now allocated for Tegra as well, and accesses be made to members of gf100_fb which were not accessible because gk20a_fb_new() called nvkm_fb_new_()

...+++++++++++++++++++++++++--------- v2v/utils.ml | 15 ++++++++++++++ v2v/utils.mli | 3 +++ v2v/vCenter.ml | 16 +-------------- 4 files changed, 61 insertions(+), 24 deletions(-) diff --git a/v2v/parse_libvirt_xml.ml b/v2v/parse_libvirt_xml.ml index 4ac9b51a5..ed2266232 100644 --- a/v2v/parse_libvirt_xml.ml +++ b/v2v/parse_libvirt_xml.ml @@ -23,6 +23,7 @@ open Common_utils open Types open Xpath_helpers +open Utils type parsed_disk = { p_source_disk : source_disk; @@ -43,12 +44,38 @@ let get_drive_slot str offset = warning (f_"could not...

...sh/virt-p2v-make-disk +/bash/virt-p2v-make-kickstart +/bash/virt-p2v-make-kiwi +/bash/virt-resize /bash/virt-sysprep /bash/virt-sparsify +/bash/virt-tar-in +/bash/virt-tar-out /build-aux/.gitignore /build-aux/ar-lib /build-aux/compile diff --git a/bash/Makefile.am b/bash/Makefile.am index 2c8e722..c95c99f 100644 --- a/bash/Makefile.am +++ b/bash/Makefile.am @@ -1,5 +1,5 @@ # libguestfs -# Copyright (C) 2013 Red Hat Inc. +# Copyright (C) 2013-2016 Red Hat Inc. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License a...

Hi, this small series moves the OCaml Checksums module from virt-builder to mllib, adding more features to use it also for v2v. Thanks, Pino Toscano (4): mllib: move Checksums from builder mllib, builder: add and use Checksums.of_string mllib: add SHA1 support in Checksums v2v: -i ova: use Checksums builder/Makefile.am | 2 -- builder/builder.ml | 6 +++-

....5 2817.4 Pipe Throughput 1063.2 1036.7 Pipe-based Context Switching 284.7 281.1 Process Creation 679.6 649.1 Shell Scripts (1 concurrent) 1933.2 1922.9 Shell Scripts (8 concurrent) 5003.3 4899.8 System Call Overhead 900.6 896.8 ========================== System Benchmarks Index Score 1139.3 1133.0 -------------------...

....5 2817.4 Pipe Throughput 1063.2 1036.7 Pipe-based Context Switching 284.7 281.1 Process Creation 679.6 649.1 Shell Scripts (1 concurrent) 1933.2 1922.9 Shell Scripts (8 concurrent) 5003.3 4899.8 System Call Overhead 900.6 896.8 ========================== System Benchmarks Index Score 1139.3 1133.0 -------------------...

Changes since v2: handling for devices without config space (e.g. rng) reduce # of mappings for VQs These patches seem to work fine on my virtio-1.0 qemu branch. There haven't been any bugs since v2: just minor cleanups and enhancements. QEMU side is still undergoing polishing, but is already testable. Rusty, what do you think? Let's merge these for 3.20? Also - will you be doing that

Changes since v2: handling for devices without config space (e.g. rng) reduce # of mappings for VQs These patches seem to work fine on my virtio-1.0 qemu branch. There haven't been any bugs since v2: just minor cleanups and enhancements. QEMU side is still undergoing polishing, but is already testable. Rusty, what do you think? Let's merge these for 3.20? Also - will you be doing that

This implements most of RHBZ#1367738. I didn't bother with virt-v2v-copy-to-local and virt-win-reg, but all the other tools now have full bash completion. Rich.

This is on top of 3.19 master + my bugfix patches, and adds virtio 1.0 support to virtio pci. This is 3.20 material I think. Would like to get feedback on s390 change as it's untested. Michael S Tsirkin (2): pci: add pci_iomap_range s390: add pci_iomap_range Michael S. Tsirkin (2): virtio_pci: modern driver virtio_pci: macros for PCI layout offsets. Rusty Russell (1): virtio-pci:

This is on top of 3.19 master + my bugfix patches, and adds virtio 1.0 support to virtio pci. This is 3.20 material I think. Would like to get feedback on s390 change as it's untested. Michael S Tsirkin (2): pci: add pci_iomap_range s390: add pci_iomap_range Michael S. Tsirkin (2): virtio_pci: modern driver virtio_pci: macros for PCI layout offsets. Rusty Russell (1): virtio-pci:

....5 2817.4 Pipe Throughput 1063.2 1036.7 Pipe-based Context Switching 284.7 281.1 Process Creation 679.6 649.1 Shell Scripts (1 concurrent) 1933.2 1922.9 Shell Scripts (8 concurrent) 5003.3 4899.8 System Call Overhead 900.6 896.8 ========================== System Benchmarks Index Score 1139.3 1133.0 -------------------...

....5 2817.4 Pipe Throughput 1063.2 1036.7 Pipe-based Context Switching 284.7 281.1 Process Creation 679.6 649.1 Shell Scripts (1 concurrent) 1933.2 1922.9 Shell Scripts (8 concurrent) 5003.3 4899.8 System Call Overhead 900.6 896.8 ========================== System Benchmarks Index Score 1139.3 1133.0 -------------------...

This patchset is for more paravirtualization on ia64/pv_ops. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full