Displaying 6 results from an estimated 6 matches for "e5630".
Did you mean:
e5430
2011 Mar 21
1
Cant find out MCE reason (CPU 35 BANK 8)
Hello community.
We are running, Centos 4.8 on SuperMicro SYS-6026T-3RF with 2xIntel Xeon
E5630 and 8xKingston KVR1333D3D4R9S/4G
For some time we have lots of MCE in mcelog and we cant find out the reason.
"Ordinary" mce message looks like:
CPU 51 BANK 8 TSC 8511e3ca77dc
MISC 274d587f00006141 ADDR 807044840
STATUS cc0055000001009f MCGSTATUS 0
decode with mcelog --ascii --cpu p4(c...
2010 Nov 03
2
CPU enumeration
Hello,
Is it possible to alter how XCP enumerates multi-core cpu’s such that a Vcpu represents a “socket”, rather than a “core”? A server with dual quad core processors, no HT, presents each of the 8 cores as a Vcpu to the guest. Windows Server 2008 R2 see’s each Vcpu as a unique “socket” and we are therefore coming up against licensing issues with Windows and more importantly SQL Server 2008
2013 Nov 10
0
[LLVMdev] loop vectorizer erroneously finds 256 bit vectors
...r the previously sent IR the vector width of
256 bit is found mistakenly (and reproducibly) on this hardware:
model name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
For the same IR the loop vectorizer finds the correct vector width (128
bit) on:
model name : Intel(R) Xeon(R) CPU E5630 @ 2.53GHz
model name : Intel(R) Core(TM) i7 CPU M 640 @ 2.80GHz
Thus, the behavior depends on which hardware I run on.
I am using the JIT execution engine (original interface).
Frank
On 09/11/13 23:50, Frank Winter wrote:
> The loop vectorizer is doing an amazing job so far. Most...
2013 Nov 10
2
[LLVMdev] loop vectorizer erroneously finds 256 bit vectors
...width of
> 256 bit is found mistakenly (and reproducibly) on this hardware:
>
> model name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
>
> For the same IR the loop vectorizer finds the correct vector width (128
> bit) on:
>
> model name : Intel(R) Xeon(R) CPU E5630 @ 2.53GHz
> model name : Intel(R) Core(TM) i7 CPU M 640 @ 2.80GHz
>
> Thus, the behavior depends on which hardware I run on.
>
> I am using the JIT execution engine (original interface).
>
> Frank
>
>
>
> On 09/11/13 23:50, Frank Winter wrote:
>
>&g...
2013 Nov 10
0
[LLVMdev] loop vectorizer erroneously finds 256 bit vectors
...found mistakenly (and reproducibly) on this
> hardware:
>
> model name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
>
> For the same IR the loop vectorizer finds the correct vector width
> (128 bit) on:
>
> model name : Intel(R) Xeon(R) CPU E5630 @ 2.53GHz
> model name : Intel(R) Core(TM) i7 CPU M 640 @ 2.80GHz
>
> Thus, the behavior depends on which hardware I run on.
>
> I am using the JIT execution engine (original interface).
>
> Frank
>
>
>
> On 09/11/13 23:50, Frank Winte...
2013 Nov 10
3
[LLVMdev] loop vectorizer erroneously finds 256 bit vectors
The loop vectorizer is doing an amazing job so far. Most of the time.
I just came across one function which led to unexpected behavior:
On this function the loop vectorizer finds a 256 bit vector as the
wides vector type for the x86-64 architecture. (!)
This is strange, as it was always finding the correct size of 128 bit
as the widest type. I isolated the IR of the function to check if this
is