search for: cmd_line

...p so far. I have few more questions to ask: > > How do I modify the driver to pick tools from where the driver itself > resides, rather than from the PATH? > Do I need to write some C++ code to customize such behaviors? Yes, this is what hooks are for. You're supposed to change the cmd_line property to something like this: (cmd_line "$CALL(PrependCustomizedPath, 'toolname') --tool --options") The PrependCustomizedPath function above is implemented in C++ (just drop a .cpp file into the plugin directory). > And how to make sure that we have same behavior on Wind...

Hi Mikhail, Thanks for your wonderful help so far. I have few more questions to ask: How do I modify the driver to pick tools from where the driver itself resides, rather than from the PATH? And how to make sure that we have same behavior on Windows as far as paths (/ Vs \) and picking up tools from the driver directory is concerned? Do I need to write some C++ code to customize such

This patch set should make it easier to maintain PV-GRUB2 installations. The general idea is based on discussions I had with Xen developers (mainly Ian Jackson) at the Ubuntu Developer Summit in May 2011; though I never did manage to get the core port done and Vladimir beat me to that, I think the configuration approach we discussed there is still valid and useful. The idea here is that people

...(...) ...' and 'if (...) ... else if (...) ... else ...' forms. That's what the EmitElseIf argument controls. BTW, the example in the documentation generates the 'if (...) ... else if (...) ... else ...' form since the 'case' there is assumed to be inside the 'cmd_line' property. Can you provide a small TableGen code example of what you're trying to do which is not working? -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

...ay be you can help. > [...] > > Is this possible in driver? or should I hack llvm-ld? On second thought, I think I'll add a workaround for this even if llvm-ld's behaviour will be fixed (for example, by adding a second '-o' option). You will be able to say the following: (cmd_line "llc $(CALL AddBcSuffix, $INFILE)") Will this modification solve your problem?

Hi Mikhail, I have one more problem related to driver/llvm-ld at my hand for which i could not think of any solution. May be you can help. We use llvm-ld as a linker to link .bc alongwith other .bc libs. example $ llvm-ld foo.bc -l std -o tmp.bc Now this command generates two files 1. tmp.bc (lli executable script) 2. tmp.bc.bc (the linked output .bc) Now i am interested only in

...config from /home/xen_images/vtpmmgr-stubdom.cfg Daemon running with PID 5048 Xen Minimal OS! start_info: 0xa2000(VA) nr_pages: 0x1000 shared_inf: 0x44e09000(MA) pt_base: 0xa5000(VA) nr_pt_frames: 0x5 mfn_list: 0x9a000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: stack: 0x597e0-0x797e0 MM: Init _text: 0x0(VA) _etext: 0x39357(VA) _erodata: 0x45000(VA) _edata: 0x47c40(VA) stack start: 0x597e0(VA) _end: 0x99e00(VA) start_pfn: ad max_pfn: 1000 Mapping memory range 0x400000 - 0x1000000 setting 0x0-0x45000 readonly skipped...

...>> >> How do I modify the driver to pick tools from where the driver itself >> resides, rather than from the PATH? >> Do I need to write some C++ code to customize such behaviors? >> > > Yes, this is what hooks are for. You're supposed to change the > cmd_line property to something like this: > > (cmd_line "$CALL(PrependCustomizedPath, 'toolname') --tool --options") > > The PrependCustomizedPath function above is implemented in C++ (just > drop a .cpp file into the plugin directory). > > Hi Mikhail, I want to re...

...and then use that variable when constructing the command > line. This is not possible without hooks, but hooks are limited in > what they can do (they can only do simple string substitution). Would it help if it was allowed to pass arguments to hooks? So that you could write, for example: (cmd_line "$CALL(MyHook, $INFILE, $OUTFILE)") > Basically, my concern with TableGen is that a lot of work has gone > into creating a small domain-specific scripting language in > TableGen, when maybe a real scripting language would be easier to > use. As Anton said, that was intention...

...adflags; +#define LOADED_HIGH (1<<0) +#define KEEP_SEGMENTS (1<<6) +#define CAN_USE_HEAP (1<<7) + uint16_t setup_move_size; + uint32_t code32_start; + uint32_t ramdisk_image; + uint32_t ramdisk_size; + uint32_t bootsect_kludge; + uint16_t heap_end_ptr; + uint16_t _pad1; + uint32_t cmd_line_ptr; + uint32_t initrd_addr_max; + uint32_t kernel_alignment; + uint8_t relocatable_kernel; + uint8_t _pad2[3]; + uint32_t cmdline_size; + uint32_t hardware_subarch; + uint64_t hardware_subarch_data; +} __attribute__((packed)); + +/* The so-called "zeropage" */ +struct boot_params { + u...

...adflags; +#define LOADED_HIGH (1<<0) +#define KEEP_SEGMENTS (1<<6) +#define CAN_USE_HEAP (1<<7) + uint16_t setup_move_size; + uint32_t code32_start; + uint32_t ramdisk_image; + uint32_t ramdisk_size; + uint32_t bootsect_kludge; + uint16_t heap_end_ptr; + uint16_t _pad1; + uint32_t cmd_line_ptr; + uint32_t initrd_addr_max; + uint32_t kernel_alignment; + uint8_t relocatable_kernel; + uint8_t _pad2[3]; + uint32_t cmdline_size; + uint32_t hardware_subarch; + uint64_t hardware_subarch_data; +} __attribute__((packed)); + +/* The so-called "zeropage" */ +struct boot_params { + u...

...adflags; +#define LOADED_HIGH (1<<0) +#define KEEP_SEGMENTS (1<<6) +#define CAN_USE_HEAP (1<<7) + uint16_t setup_move_size; + uint32_t code32_start; + uint32_t ramdisk_image; + uint32_t ramdisk_size; + uint32_t bootsect_kludge; + uint16_t heap_end_ptr; + uint16_t _pad1; + uint32_t cmd_line_ptr; + uint32_t initrd_addr_max; + uint32_t kernel_alignment; + uint8_t relocatable_kernel; + uint8_t _pad2[3]; + uint32_t cmdline_size; + uint32_t hardware_subarch; + uint64_t hardware_subarch_data; +} __attribute__((packed)); + +/* The so-called "zeropage" */ +struct boot_params { + u...

...tart_info->domain_controller_evtchn = control_evtchn; + start_info->store_page = vstartinfo_start + PAGE_SIZE; + start_info->store_evtchn = store_evtchn; if ( initrd_len != 0 ) { start_info->mod_start = vinitrd_start; @@ -270,6 +276,9 @@ start_info->cmd_line[MAX_CMDLINE-1] = ''\0''; munmap(start_info, PAGE_SIZE); + /* Tell our caller where we told domain store page was. */ + *store_mfn = page_array[((vstartinfo_start-dsi.v_start)>>PAGE_SHIFT) + 1]; + /* shared_info page starts its life empty. */ shared_info...

...h below: ======= Parsing config from vtpmmgr.cfg Daemon running with PID 2406 Xen Minimal OS! start_info: 0xa2000(VA) nr_pages: 0x1000 shared_inf: 0xcd7b0000(MA) pt_base: 0xa5000(VA) nr_pt_frames: 0x5 mfn_list: 0x9a000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: stack: 0x597e0-0x797e0 MM: Init _text: 0x0(VA) _etext: 0x39357(VA) _erodata: 0x45000(VA) _edata: 0x47c40(VA) stack start: 0x597e0(VA) _end: 0x99e00(VA) start_pfn: ad max_pfn: 1000 Mapping memory range 0x400000 - 0x1000000 setting 0x0-0x45000 readonly skipped...

...h below: ======= Parsing config from vtpmmgr.cfg Daemon running with PID 2406 Xen Minimal OS! start_info: 0xa2000(VA) nr_pages: 0x1000 shared_inf: 0xcd7b0000(MA) pt_base: 0xa5000(VA) nr_pt_frames: 0x5 mfn_list: 0x9a000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: stack: 0x597e0-0x797e0 MM: Init _text: 0x0(VA) _etext: 0x39357(VA) _erodata: 0x45000(VA) _edata: 0x47c40(VA) stack start: 0x597e0(VA) _end: 0x99e00(VA) start_pfn: ad max_pfn: 1000 Mapping memory range 0x400000 - 0x1000000 setting 0x0-0x45000 readonly skipped...

Thanks for the reply! > The plan now is to make this functionality easier to use, so you'll be able to > just say: > > llvmc2 --load MyPlugin.td MyFile.cpp > > and have llvmc2 build and load MyPlugin.td behind the scenes. That sounds like a good idea. Part of the reason I suggested making the system less dependent on TableGen is that in the process of developing a

Hi there, I am starting a new thread to try and solve a problem I am having will slow network throughput to the XEN host (not to a domU). I have confirmed my problem occurs with PVOPS ''xen/master'' kernel as well using http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.6-pvops-dom0-xen-master-x86_64 as the .config. It also occurs with a forward ported xenified kernel

Hi there, I am starting a new thread to try and solve a problem I am having will slow network throughput to the XEN host (not to a domU). I have confirmed my problem occurs with PVOPS ''xen/master'' kernel as well using http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.6-pvops-dom0-xen-master-x86_64 as the .config. It also occurs with a forward ported xenified kernel

Hi Mikhail, What is mentioned in the reference manual is this: // Evaluates to "cmdline1" if the option "-A" is provided on the // command line; to "cmdline2" if "-B" is provided; // otherwise to "cmdline3". (case (switch_on "A"), "cmdline1", (switch_on "B"), "cmdline2",

Sanjiv Gupta wrote: > Hi Mikhail, > > What is mentioned in the reference manual is this: > > // Evaluates to "cmdline1" if the option "-A" is provided on the > // command line; to "cmdline2" if "-B" is provided; > // otherwise to "cmdline3". > > (case > (switch_on "A"),