search for: block0

Lets say you had 4 servers and you wanted to setup replicate and distribute. What methoid would be better: server sdb1 xen0 brick0 xen1 mirror0 xen2 brick1 xen3 mirror1 replicate block0 - brick0 mirror0 replicate block1 - brick1 mirror1 distribute unify - block0 block1 or server sdb1 sdb2 xen0 brick0 mirror3 xen1 brick1 mirror0 xen2 brick2 mirror1 xen3 brick3 mirror2 replicate block0 - brick0 mirror0 replicate block1 - brick1 mirror1 replicate block2 - brick2 mirror2 replicate...

Hi, Ady wrote: > so, why the original isohybrid image from Debian and many other > isohybrid images have mostly (but not all) "00s" in place of the "90s"? That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. * Fedora has it with EFI FAT filesystem in one partition and a HFS filesystem in another partition. * Debian and Ubuntu have it only for the EFI FAT partition. * Arch...

> Hi, > > Ady wrote: > > so, why the original isohybrid image from Debian and many other > > isohybrid images have mostly (but not all) "00s" in place of the "90s"? > > That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. > Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. > > * Fedora has it with EFI FAT filesystem in one partition and a HFS filesystem > in another partition. > * Debian and Ubuntu have it only for the...

Hi, Gene Cumm wrote: > it seems the stack format got > set, changed, then mostly reverted back, with this code being the last > piece missing from 2009. The commit to isohdpfx.S of 2009-05-31 looks incomplete. The sequence of the stack pointers was swapped, but the sequence of stack pushes was not.

I have 6 boxes with a client config (see below) across 6 boxes. I am using distribute across 3 replicate pairs. Since I am running xen I need to disable-direct-io and that slows things down quite a bit. My thought was to move the replicate / distribute to the backend server config so that self heal can happen on faster backend rather then frontend client with disable-direct-io. Does this

I am working on a target which has some structural hazards. To detect these hazards, I implemented a sub-class of PostRAHazardRecognizer. PostRAHazardRecognizer resets the hazard state on a basic block basis. So, how to detect hazards that may occur between the end of a basic block and the beginning of another basic block ? Thanks ! -------------- next part -------------- An HTML

Hi, i have implemented in xorriso the equivalents of isohybrid.c options --mac and --uefi. There remains the question how to ensure that the submitted MBR is prepared for the 32 byte mock-up of an APM Block0. I see in git of may 2012 that all mbr/isohdp[fp]x*.bin begin by 33 ed 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 Can i safely refuse on MBR templates which do not bear that signature without inflicting injustice o...

...m::createInstructionCombiningPass() llvm::createReassociatePass() llvm::createGVNPass() llvm::createCFGSimplificationPass() The optimized IR seems to contain what look like dead stores on %8 and %9 in basic blocks 7 and haveData. How can I get rid of them? Thanks, Vinayak define internal void @block0() { entry: %0 = call i8* @RNI_File_new() %1 = call i64 @RNI_File_open(i8* %0, i8* getelementptr inbounds ([69 x i8]* @.str, i64 0, i64 0), i8 0) %2 = icmp eq i64 %1, 0 br i1 %2, label %openSuccessBB, label %errorExit0 errorExit0: ; preds = %entry,...

...(OK, this is not good C style ;) ) { ... goto label0; ... goto label1; ... label0: { // some C code for basic block starting at label0 ... } label1: { // some C code for basic block starting at label1 ... } } In the previous example, the last instruction of basic block0 (starting at label0) is not a jump. There might be a structural hazard between this instruction and the first instruction of basic block1 (starting at label1). Did you have to deal with this kind of hazards ? Thanks. On Thu, Feb 10, 2011 at 10:30 AM, Damien Vincent <damien.llvm at gmail.com&l...

...ructions when BIOS starts the MBR. As long as no old Mac is around, one should not take that risk. To my knowledge the APM in the Debian and Ubuntu ISOs is useless. The APM of Fedora and some Gentoo ISOs points to a HFS+ filesystem and thus might be of interest for the Macs. In any case the APM Block0 is a dummy with always the same content, regardless of the size of the ISO or the position of the HFS+ partition. Its presence without further APM blocks would not harm BIOS booting but could mislead the old Macs for which APM matters. > With the variety of potential combinations, is there rea...

mainly question for the intel folks, any chance to rerun the ltp testsuites to see how we are doing these days with all the changes ? thanks :) Wim

Hi, When we meet UEFI or EFI firmware, lots of linux os release use GRUB bootloader. But I wanna use isolinux to boot the installation environment and also the linux os installed. Some question puzzled me. Now, I look for your help: 1. I didn't found information about how to use syslinux(isolinux,etc.) in uefi. I wanna know that are there some differences of the isolinux configuration

...S,HTT,TM,<b31>> real memory = 536805376 (511 MB) avail memory = 516386816 (492 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: <math processor> on motherboard npx0: INT 16 interface acpi0: <IntelR AWRDACPI> on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Using $PIR table, 10 entries at 0xc00fdeb0 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_cpu0: <CPU> on acpi0...

...T,TM,<b31>> real memory = 1342152704 (1279 MB) avail memory = 1298341888 (1238 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: <math processor> on motherboard npx0: INT 16 interface acpi0: <COMPAQ D14 > on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O rang...