search for: purley

https://access.redhat.com/support/policy/intel shows mainly Xeon CPUs. What about Intel Core i7-6700 Quad-Core Skylake has the current EL6 variant support for it? Any experience? Feedback would be greatly appreciated. Thanks, LF

...> > 796 if ((boot_cpu_data.x86_vendor == X86_VENDOR_INTEL) && > 797 ((boot_cpu_data.x86 == 6))) { > 798 switch (boot_cpu_data.x86_model) { > 799 case 94: /* Skylake-S */ > 800 case 86: /* Broadwell-DE SoC */ > 801 case 85: /* Purley */ > 802 case 79: /* Broadwell-EP and EX */ > 803 case 78: /* Skylake-Y */ > 804 case 77: /* Atom Avoton */ > 805 case 71: /* Broadwell-H */ > 806 case 70: /* Crystal Well */ > 807 break; > 808 default: > 809...

....el6/arch/x86/kernel/setup.c 796 if ((boot_cpu_data.x86_vendor == X86_VENDOR_INTEL) && 797 ((boot_cpu_data.x86 == 6))) { 798 switch (boot_cpu_data.x86_model) { 799 case 94: /* Skylake-S */ 800 case 86: /* Broadwell-DE SoC */ 801 case 85: /* Purley */ 802 case 79: /* Broadwell-EP and EX */ 803 case 78: /* Skylake-Y */ 804 case 77: /* Atom Avoton */ 805 case 71: /* Broadwell-H */ 806 case 70: /* Crystal Well */ 807 break; 808 default: 809 if (boot_cpu_data.x86_mode...

Hi anyone, Sorri to bring a purley Model Security question on this list but I can''t find anywhere to bring this up on the Model Security project page. I''ve found a bug (I think) in the Model Security generator but I''m not sure... I''m pretty noob and I could just be missing something. I''...

Hi, Has anyone had any experience with Intel Vroc[1]? I'm possibly having to deal with a new server with such technology and can't find much (real world) information about it. Looking at the specs it's basically a glorified fake raid which usually turns on my alarm bells. Has anyone done any testing, how does it compare with "real" raid or software raid? Cheers, Lucian [1]

Hello Matthew, On Thu, 27 Jul 2017 15:59:35 -0400 Matthew Miller <mattdm at mattdm.org> wrote: > On Thu, Jul 27, 2017 at 08:38:14PM +0200, wwp wrote: > > Say, instead of stable, something not rawhide. But I'll examine all > > options that do work, so let's forget about "stable". > > In that case ? and I freely admit I have some bias here ? I

...f ((boot_cpu_data.x86_vendor == X86_VENDOR_INTEL) && >> 797 ((boot_cpu_data.x86 == 6))) { >> 798 switch (boot_cpu_data.x86_model) { >> 799 case 94: /* Skylake-S */ >> 800 case 86: /* Broadwell-DE SoC */ >> 801 case 85: /* Purley */ >> 802 case 79: /* Broadwell-EP and EX */ >> 803 case 78: /* Skylake-Y */ >> 804 case 77: /* Atom Avoton */ >> 805 case 71: /* Broadwell-H */ >> 806 case 70: /* Crystal Well */ >> 807 break; >> 808...

...est evaluation of their experience. I must admit I don't understand a mailing list as you must get so many replications of the same. I think a forum is often a better platform. Again this is no dictate just saying how my experience is and giving you some feed back Please meddle away, it was purley an opinion. The documentation is a bit sketchy and when you do a google because of the tremendous fast development its a bit of a mare because of the tremendous fast development There are a lot of versions and sometimes its very easy to get confused. Also because its so fast and a moving roadmap...

...6_vendor == X86_VENDOR_INTEL) && >>> 797 ((boot_cpu_data.x86 == 6))) { >>> 798 switch (boot_cpu_data.x86_model) { >>> 799 case 94: /* Skylake-S */ >>> 800 case 86: /* Broadwell-DE SoC */ >>> 801 case 85: /* Purley */ >>> 802 case 79: /* Broadwell-EP and EX */ >>> 803 case 78: /* Skylake-Y */ >>> 804 case 77: /* Atom Avoton */ >>> 805 case 71: /* Broadwell-H */ >>> 806 case 70: /* Crystal Well */ >>> 807...