search for: bank2

Hi, Some operations on AMDGPU require operands which must be in a register bank that is impossible to copy from another. The operation needs to be rewritten in a complex way to avoid the illegal copy. Currently if I correctly report the required register banks in the operand mapping, RegBankSelect happily inserts the illegal copies, somehow concluding they are cheap (I would at least hope

...then checks these registers and creates the new vregs and rewrites as necessary. Is this the way this is intended to work? > > I am not sure I understand the work around. > Let me try to illustrate this with an example. > Let say we have: > = inst a(bank1) > And inst only accepts bank2. > Are you saying that you lie by saying that bank1 is legal in that case? > If so, why applyMapping would do any rewriting since this is legal. Yes. It’s what happens here: https://reviews.llvm.org/D58511 <https://reviews.llvm.org/D58511> For extract_vector_elt, the indirect register...

...not read Master Boot Record\n"); goto error; } /* Get 1st partition info */ bank1_part_info = PARTITION_ENTRY(mbr, bank1); if (bank1_part_info->ostype != PART_TYPE_FAT16) { error("Warning: Bank 1 is of wrong type"); } /* Get 2nd partition info */ bank2_part_info = PARTITION_ENTRY(mbr, bank2); if (bank2_part_info->ostype != PART_TYPE_FAT16) { error("Warning: Bank 2 is of wrong type"); } rFd.disk_info = &disk_info; rFd.partition = bank1_part_info; fat_fs = libfat_open(fat_disk_read_handle, (intptr_t) &rFd...

Hi, I'm wondering if there's a method for doing any of these 1. Check what's the physical memory available. free -m shows ~768 mem but I was sure that I had 1G of memory in there. 2. I check the kernel and it seems like the 4G split is in effect so it should map / correctly recognise there's 1G of Mem there. Is there any way to check besides opening up the machine to look at it

...Sockets ================================ Type Status Set Device Locator Bank Locator ----------- ------ --- ------------------- ---------------- unknown empty 0 DIMM1 BANK0 unknown empty 0 DIMM2 BANK1 unknown empty 0 DIMM3 BANK2 SDRAM in use 0 DIMM4 BANK3 ==== On-Board Devices ===================================== To Be Filled By O.E.M. ==== Upgradeable Slots ==================================== ID Status Type Description --- --------- ---------------- ----------------------------...

...Sockets ================================ Type Status Set Device Locator Bank Locator ----------- ------ --- ------------------- ---------------- Unknown in use 0 P1_DIMM1B BANK0 Unknown in use 0 P1_DIMM1A BANK1 Unknown in use 0 P1_DIMM2B BANK2 Unknown in use 0 P1_DIMM2A BANK3 Unknown in use 0 P1_DIMM3B BANK4 Unknown in use 0 P1_DIMM3A BANK5 Unknown in use 0 P1_DIMM4B BANK6 Unknown in use 0 P1_DIMM4A BANK7 unknown empty 0 P2_DIMM1B BANK8 unkno...

...= Memory Device Sockets ================================ Type Status Set Device Locator Bank Locator ------- ------ --- ------------------- -------------------- SDRAM in use 0 DIMM0 BANK0 SDRAM in use 0 DIMM1 BANK1 SDRAM in use 0 DIMM2 BANK2 SDRAM in use 0 DIMM3 BANK3 SDRAM in use 0 DIMM4 BANK4 SDRAM in use 0 DIMM5 BANK5 SDRAM in use 0 DIMM6 BANK6 SDRAM in use 0 DIMM7 BANK7 ==== On-Board Devices ===================================== To Be Fill...

...Serial Number: None Asset Tag: None Part Number: None Handle 0x001F, DMI type 17, 27 bytes Memory Device Array Handle: 0x001D Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: A2 Bank Locator: Bank2/3 Type: Unknown Type Detail: None Speed: Unknown Manufacturer: None Serial Number: None Asset Tag: None Part Number: None Handle 0x0020, DMI type 17, 27 bytes Memory Device Array Handle: 0x001D Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 1024 M...

This is my first post here, and i hope it is ok that i posted in this thread. I have been doing a bit of reading on the solaris platforms, and seem to be inclined to try out the open solaris os or solaris 10. My only worry is that my lack of knowledge with the command line may make this difficult regarding trouble shooting. It seems fairly straighforward creating zpools etc, but maybe nexenta is

Is there a method to view the status of the rams ecc single or double bit errors? I would like to confirm that ecc on my xeon e5520 and ecc ram are performing their role since memtest is ambiguous. I am running memory test on a p6t6 ws, e5520 xeon, 2gb samsung ecc modules and this is what is on the screen: Chipset: Core IMC (ECC : Detect / Correct) However, further down "ECC" is

...andle 0x0023, DMI type 126, 19 bytes Inactive Handle 0x0024, DMI type 17, 27 bytes Memory Device Array Handle: 0x001E Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: PROC 1 DIMM 1G Bank Locator: BANK2 Type: <OUT OF SPEC> Type Detail: Synchronous Speed: Unknown Manufacturer: Manufacturer02 Serial Number: 00000000 Asset Tag: AssetTagNum2 Part Number: Handle 0x0025, DMI type 126, 19 bytes Inactive Handle 0x0026, DMI type 17, 27 bytes Memory Device Array Handle: 0x...