search for: dtb

This is the libguestfs companion patch to: https://www.redhat.com/archives/libguestfs/2013-September/msg00045.html Rich.

...h for supermin implements device trees (for ARM). The first patch introduces a more rational way to handle command line arguments in 'supermin-helper'. See the commit message for details. The old style is still supported for compatibility. The second patch adds an extra supermin-helper --dtb parameter specifying a wildcard. A device tree file which matches the selected kernel and this wildcard is linked to (or copied if --copy-kernel). The intended use is from libguestfs (on ARM) which can now do: supermin-helper -f ext2 --dtb 'vexpress-*a9.dtb' [etc] which will create a...

.../xc_dom_arm.c b/tools/libxc/xc_dom_arm.c index ffe575b..366061d 100644 --- a/tools/libxc/xc_dom_arm.c +++ b/tools/libxc/xc_dom_arm.c @@ -290,6 +290,8 @@ int arch_setup_meminit(struct xc_dom_image *dom) else /* otherwise at top of RAM */ dom->devicetree_seg.vstart = ramend - dtbsize; + dom->devicetree_seg.vstart &= XC_PAGE_MASK; + dom->devicetree_seg.vend = dom->devicetree_seg.vstart + dom->devicetree_size; DOMPRINTF("%s: devicetree: 0x%" PRIx64 " -> 0x%" PRIx64 "", -- 1.7.10.4

...e interested to is not located in the module being compiled (if you created it as an auxiliary function, for example), you could create this information by simply creating a DominatorTreeBase of your function and using it to calculate the LoopInfo, as below: DominatorTreeBase<BasicBlock> *DTB; DTB = new DominatorTreeBase<BasicBlock>(false); DTB->recalculate(*AuxFunction); LoopInfoBase<BasicBlock, Loop> LIB; LIB.Calculate(*DTB); Cheers, -- Cristianno Martins PhD Student of Computer Science University of Campinas cmartins at ic.unicamp.br On Thursday,...

Hi, Now that the Arndale board is supported in upstream Xen I don''t get any output on the serial console. I followed the instructions on the wiki with no luck: The xen repository I''m using is: git://xenbits.xen.org/xen.git last commit: 61c6dfce3296da2643c4c4f90eaab6fa3c1cf8b3 The linux repository is: git://xenbits.xen.org/people/julieng/linux-arm.git last commit:

...+++++++++++++++++++------------------------------ 1 file changed, 44 insertions(+), 45 deletions(-) diff --git a/src/kernel.ml b/src/kernel.ml index 9b0e8a2..2e061d8 100644 --- a/src/kernel.ml +++ b/src/kernel.ml @@ -40,28 +40,7 @@ let patt_of_cpu host_cpu = let rec build_kernel debug host_cpu dtb_wildcard copy_kernel kernel dtb = (* Locate the kernel. *) - let kernel_name, kernel_version = - find_kernel debug host_cpu copy_kernel kernel in - - (* If the user passed --dtb option, locate dtb. *) - (match dtb_wildcard with - | None -> () - | Some wildcard -> - find_dtb debu...

Document what each module does, using *.mli files. Remove the --dtb option, it's obsolete. Rename modules according to their purpose. Rich.

* Richard W.M. Jones: > On Sat, Apr 26, 2014 at 02:27:07PM +0200, Hilko Bengen wrote: >> --- >> src/kernel.ml | 43 ++++++++++++++++++++++++++++--------------- >> 1 file changed, 28 insertions(+), 15 deletions(-) >> >> diff --git a/src/kernel.ml b/src/kernel.ml >> index ed5aea3..436b1b0 100644 >> --- a/src/kernel.ml >> +++ b/src/kernel.ml

...e interested to is not located in the module being compiled (if you created it as an auxiliary function, for example), you could create this information by simply creating a DominatorTreeBase of your function and using it to calculate the LoopInfo, as below: DominatorTreeBase<BasicBlock> *DTB; DTB = new DominatorTreeBase<BasicBlock>(false); DTB->recalculate(*AuxFunction); LoopInfoBase<BasicBlock, Loop> LIB; LIB.Calculate(*DTB); Cheers, -- Cristianno Martins PhD Student of Computer Science University of Campinas cmartins at ic.unicamp.br On Thursday, 2...

...+ arm,v2m-memory-map = "rs1"; + }; +}; diff --git a/arch/arm/mach-vexpress/Makefile.boot b/arch/arm/mach-vexpress/Makefile.boot index 318d308..38dbaac 100644 --- a/arch/arm/mach-vexpress/Makefile.boot +++ b/arch/arm/mach-vexpress/Makefile.boot @@ -7,4 +7,5 @@ initrd_phys-y := 0x60800000 dtb-$(CONFIG_ARCH_VEXPRESS_DT) += vexpress-v2p-ca5s.dtb \ vexpress-v2p-ca9.dtb \ vexpress-v2p-ca15-tc1.dtb \ - vexpress-v2p-ca15_a7.dtb + vexpress-v2p-ca15_a7.dtb \ + xenvm-4.2.dtb diff --git a/arch/arm/mach-vexpress/v2m.c b/arch/arm/mach-vexpress/v2m.c index 4e567f7.....

Hi Rich But there is no src/kernel.ml file on my ubuntu powerpc to which the above patch is reffering. I have installed supermin as supermin_5.1.8-2_powerpc.deb debian package. Thanks On Tue, Jun 3, 2014 at 7:16 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, Jun 03, 2014 at 06:55:49PM +0530, abhishek jain wrote: > > supermin: failed to find a suitable kernel

...least the CallGraph to it? Oh, and btw, my module pass has only this in its body (I just assumed I'm using it right, but maybe the problem is here): virtual bool runOnModule(Module &M) { CallGraph& cg = getAnalysis<CallGraph>(); DominatorTreeBase<CallGraphNode> *DTB; DTB = new DominatorTreeBase<CallGraphNode>(false); DTB->recalculate(cg); errs() << "DomTreeBase:"; DTB->print(errs()); return false; } virtual void getAnalysisUsage(AnalysisUsage &AU) const { AU.addRequired<CallGraph>();...

...r's to manipulate, and that QEMU shouldn't touch it at all (just pass it through). (Conversely, QEMU shouldn't require the user to specify odd kernel command line arguments in order to make things work.) (Having talked with Grant Likely I now have a reasonable plan for manipulating the dtb to add virtio nodes, so I'm happy that that's the right way to go.) As it happens, if you use the command line to specify a virtio device it doesn't make the same complaint about bad magic number as if you specify it via dtb, but that should probably be fixed in the kernel :-) > Ho...

...r's to manipulate, and that QEMU shouldn't touch it at all (just pass it through). (Conversely, QEMU shouldn't require the user to specify odd kernel command line arguments in order to make things work.) (Having talked with Grant Likely I now have a reasonable plan for manipulating the dtb to add virtio nodes, so I'm happy that that's the right way to go.) As it happens, if you use the command line to specify a virtio device it doesn't make the same complaint about bad magic number as if you specify it via dtb, but that should probably be fixed in the kernel :-) > Ho...

...m32.581s [Qualcomm Snapdragon LLVM/clang + Android NDK r17 binutils(ld and as)] : 4m44.779s *LONGEST AND SHORTEST BUILD* Code: ##### Longest build #### Name : Main LLVM/clang + Android NDK r13b binutils(ld and as) Time : 6m8.064s boot.img : boot-main-llvm-clang-ndk-r13b-binutils-ld-as.img zImage-dtb : zImage-dtb-main-llvm-clang-ndk-r13b-binutils-ld-as ##### Shortest build #### Name : Android NDK r13b : LLVM/clang + binutils(ld and as) Time : 4m3.665s boot.img : boot-ndk-r13b-clang-llvm-binutils-ld-as.img zImage-dtb : zImage-dtb-ndk-r13b-clang-llvm-binutils-ld-as *LARGEST AND SMALLEST IMAG...

...t; | _ when String.length host_cpu >= 5 && String.sub host_cpu 0 5 = > "armv7" -> ["armmp"] > | _ -> [host_cpu] > in > List.map (fun model -> sprintf "vmlinu?-*-%s" model) models > > let rec build_kernel debug host_cpu dtb_wildcard copy_kernel kernel dtb = > (* Locate the kernel. *) > let kernel_name, kernel_version = > find_kernel debug host_cpu copy_kernel kernel in > > (* If the user passed --dtb option, locate dtb. *) > (match dtb_wildcard with > | None -> () > | Some wi...

Biggest change is to switch the new DTB node to /xen-core-devices instead of /xen at Stefano''s request. I also dropped the few patches title HACK etc which weren''t supposed to be there and fixed up some bits and pieces which folks commented on. George, WRT the freeze I think this is functionality which we cannot ship...

...rnel && > - virSecurityDACRestoreFileLabel(priv, def->os.kernel) < 0) > - rc = -1; > - > - if (def->os.initrd && > - virSecurityDACRestoreFileLabel(priv, def->os.initrd) < 0) > - rc = -1; > - > if (def->os.dtb && > virSecurityDACRestoreFileLabel(priv, def->os.dtb) < 0) > rc = -1; > diff --git i/src/security/security_selinux.c w/src/security/security_selinux.c > index 721c451..475cdbc 100644 > --- i/src/security/security_selinux.c > +++ w/src/security/secu...

...17:47, Pawel Moll <pawel.moll at arm.com> wrote: > On Fri, 2013-06-21 at 17:41 +0100, Peter Maydell wrote: >> As it happens, if you use the command line to specify >> a virtio device it doesn't make the same complaint about >> bad magic number as if you specify it via dtb, but that >> should probably be fixed in the kernel :-) > > I don't really see how this would be possible - the "complaining code" > is just a normal platform device probe function. Sorry, you're correct and I misremembered. I just retested with specifying via comm...

...17:47, Pawel Moll <pawel.moll at arm.com> wrote: > On Fri, 2013-06-21 at 17:41 +0100, Peter Maydell wrote: >> As it happens, if you use the command line to specify >> a virtio device it doesn't make the same complaint about >> bad magic number as if you specify it via dtb, but that >> should probably be fixed in the kernel :-) > > I don't really see how this would be possible - the "complaining code" > is just a normal platform device probe function. Sorry, you're correct and I misremembered. I just retested with specifying via comm...