search for: 21,16

...from /usr/include/linux/vfs.h:4, from /usr/include/linux/fs.h:13, from /usr/include/linux/capability.h:17, from /usr/include/sys/capability.h:24, from include/includes.h:355, from dynconfig.c:21: /usr/include/asm-s390/statfs.h:20: redefinition of `struct statfs' make: *** [dynconfig.o] Error 1 Same thing for 3.0.2a, 3.0.3pre2 and 3.0.3rc1 (didn't try others) Any idea, anyone? Best regards Thomas

...daemon/daemon.h | 1 + daemon/fs-min-size.c | 50 ++++++++++++++++++++++++++++++++++++- generator/actions.ml | 6 ++++- 4 files changed, 124 insertions(+), 2 deletions(-) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index ddb029d..d2d85f3 100644 --- a/daemon/btrfs.c +++ b/daemon/btrfs.c @@ -2190,3 +2190,72 @@ do_btrfs_replace (const char *srcdev, const char *targetdev, return 0; } + +/* btrfs command add a new command + * inspect-internal min-dev-size <path> + * since v4.2 + * We could check whether 'btrfs' supports + * 'min-dev-size' command by checking the ou...

...drivers/vhost/Makefile | 4 ++++ net/vmw_vsock/Kconfig | 18 ++++++++++++++++++ net/vmw_vsock/Makefile | 2 ++ 4 files changed, 34 insertions(+) diff --git a/drivers/vhost/Kconfig b/drivers/vhost/Kconfig index 533eaf0..a1bb4c2 100644 --- a/drivers/vhost/Kconfig +++ b/drivers/vhost/Kconfig @@ -21,6 +21,16 @@ config VHOST_SCSI Say M here to enable the vhost_scsi TCM fabric module for use with virtio-scsi guests +config VHOST_VSOCK + tristate "vhost virtio-vsock driver" + depends on VSOCKETS && EVENTFD + select VIRTIO_VSOCKETS_COMMON + select VHOST + select VHOST_RING...

...work in either environment by checking for the existence of the `success' shell function. -- jim knoble jmknoble at pobox.com -------------- next part -------------- --- ./packages/redhat/sshd.init.orig-init Mon Nov 22 18:11:29 1999 +++ ./packages/redhat/sshd.init Sun Dec 5 02:06:27 1999 @@ -21,8 +21,16 @@ start) echo -n "Starting sshd: " if [ ! -f /var/run/sshd.pid ] ; then - /usr/sbin/sshd && success "sshd startup" || failure "sshd startup" - RETVAL=$? + case "`type -type success`" in + function) + /usr/sbin/sshd &am...

...+++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/sysprep/sysprep_operation.mli b/sysprep/sysprep_operation.mli index 61dde72..eb89db4 100644 --- a/sysprep/sysprep_operation.mli +++ b/sysprep/sysprep_operation.mli @@ -16,14 +16,16 @@ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. *) -(** Structure used to describe sysprep operations. *) +(** Defines the interface between the main program and sysprep operations. *) val prog : string type flag = [ `Created_files ] type callback = Guestfs.guestfs -> string -> flag list +(** [callback g root] is c...

...mber - * @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_...

...mber - * @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_...

.../vmw_vsock/Kconfig | 18 ++++++++++++++++++ > net/vmw_vsock/Makefile | 2 ++ > 4 files changed, 34 insertions(+) > > diff --git a/drivers/vhost/Kconfig b/drivers/vhost/Kconfig > index 533eaf0..a1bb4c2 100644 > --- a/drivers/vhost/Kconfig > +++ b/drivers/vhost/Kconfig > @@ -21,6 +21,16 @@ config VHOST_SCSI > Say M here to enable the vhost_scsi TCM fabric module > for use with virtio-scsi guests > > +config VHOST_VSOCK > + tristate "vhost virtio-vsock driver" > + depends on VSOCKETS && EVENTFD > + select VIRTIO_VSOCKETS_COMMON &g...

.../vmw_vsock/Kconfig | 18 ++++++++++++++++++ > net/vmw_vsock/Makefile | 2 ++ > 4 files changed, 34 insertions(+) > > diff --git a/drivers/vhost/Kconfig b/drivers/vhost/Kconfig > index 533eaf0..a1bb4c2 100644 > --- a/drivers/vhost/Kconfig > +++ b/drivers/vhost/Kconfig > @@ -21,6 +21,16 @@ config VHOST_SCSI > Say M here to enable the vhost_scsi TCM fabric module > for use with virtio-scsi guests > > +config VHOST_VSOCK > + tristate "vhost virtio-vsock driver" > + depends on VSOCKETS && EVENTFD > + select VIRTIO_VSOCKETS_COMMON &g...

..._t btrfs_minimum_size (const char *path); > > /*-- in ntfs.c --*/ > extern char *ntfs_get_label (const char *device); > diff --git a/daemon/fs-min-size.c b/daemon/fs-min-size.c > index 4f93f8c..cb67b6f 100644 > --- a/daemon/fs-min-size.c > +++ b/daemon/fs-min-size.c > @@ -21,16 +21,57 @@ > #include <stdio.h> > #include <stdlib.h> > #include <unistd.h> > +#include <mntent.h> > +#include <sys/stat.h> > +#include <sys/types.h> > > #include "daemon.h" > #include "actions.h" > >...

Hi, I am currently trying to set up new performance and regression testers for Polly and LLVM and would like to XFAIL two test cases. I am using the LNTBuilder instead of the NightlyTestBuilder out of the assumption that the LNTBuilder is the more modern solution. However, when trying to xfail test cases I realized the xfail=[] parameter of getLNTFactor is ignored. Previously this was not an

...ty > plain text document attachment (patch.llvm-ld-1.8) > diff -u'rF^function' tools/llvm-ld/Optimize.cpp tools/llvm-ld/Optimize.cpp > --- tools/llvm-ld/Optimize.cpp 2006-06-16 20:23:48.000000000 +0200 > +++ tools/llvm-ld/Optimize.cpp 2006-08-18 16:36:39.000000000 +0200 > @@ -21,8 +21,16 @@ > #include "llvm/Target/TargetData.h" > #include "llvm/Transforms/IPO.h" > #include "llvm/Transforms/Scalar.h" > +#include "llvm/Support/PassNameParser.h" > +#include "llvm/Support/PluginLoader.h" > using namespace...

Hi, Reid Spencer wrote: >> That's interesting! So, one only needs to add a 2-arg function called >> RunOptimizations to the module (can't check it right now)? >> > > That is correct. That function and only that function will be called. > What happens in that function is up to you :) > So, I tried this the last two days, but to no avail. I first

...tion\n" /* * Alternative instructions for different CPU types or capabilities. diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h index 2519c6c801c9..1be45a2fc00d 100644 --- a/arch/x86/include/asm/cpufeatures.h +++ b/arch/x86/include/asm/cpufeatures.h @@ -214,6 +214,7 @@ #define X86_FEATURE_VMMCALL ( 8*32+15) /* Prefer vmmcall to vmcall */ #define X86_FEATURE_XENPV ( 8*32+16) /* "" Xen paravirtual guest */ +#define X86_FEATURE_PV_OPS ( 8*32+17) /* Use pv ops alternatives */ /* Intel-defined CPU features, CPUID level 0x...

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than

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

Note: the virtio-vsock device specification is currently under review but not yet finalized. Please review this code but don't merge until I send an update when the spec is finalized. Thanks! v3: * Remove unnecessary 3-way handshake, just do REQUEST/RESPONSE instead of REQUEST/RESPONSE/ACK * Remove SOCK_DGRAM support and focus on SOCK_STREAM first (also drop v2 Patch 1, it's