>>> On 22.08.16 at 13:22, wrote:
>> > >> First of all - please don't top post.
>> > >>
>> > >>> What about remove the dependency between AVX2 and AVX512F
>> > ( AVX2:
>> > >> [AVX512F], ) ?
>> > >>
>> > >> Yes, that's
> >>> On 10.08.16 at 14:10, wrote:
> > On 10/08/16 11:29, Jan Beulich wrote:
> > On 10.08.16 at 11:58, wrote:
> >>> On 03.08.16 at 03:32, wrote:
> >> On 25/07/16 07:09, Kang, Luwei wrote:
> >> First of
On 10/08/16 11:29, Jan Beulich wrote:
On 10.08.16 at 11:58, wrote:
>> On 03.08.16 at 03:32, wrote:
> On 25/07/16 07:09, Kang, Luwei wrote:
> First of all - please don't top post.
>
>> What about remove the
>>> On 10.08.16 at 11:58, wrote:
>> >>> On 03.08.16 at 03:32, wrote:
>> >> On 25/07/16 07:09, Kang, Luwei wrote:
>> >> First of all - please don't top post.
>> >>
>> >> > What about remove the dependency between AVX2 and AVX512F
>> >> >>
> >>> On 03.08.16 at 03:32, wrote:
> >> On 25/07/16 07:09, Kang, Luwei wrote:
> >> First of all - please don't top post.
> >>
> >> > What about remove the dependency between AVX2 and AVX512F
> >> >> ( AVX2:
> >> [AVX512F], ) ?
> >>
> >> Yes,
>>> On 03.08.16 at 03:32, wrote:
>> On 25/07/16 07:09, Kang, Luwei wrote:
>> First of all - please don't top post.
>>
>> > What about remove the dependency between AVX2 and AVX512F
>> >> ( AVX2:
>> [AVX512F], ) ?
>>
>> Yes, that's what I think
> On 25/07/16 07:09, Kang, Luwei wrote:
> First of all - please don't top post.
>
> > What about remove the dependency between AVX2 and AVX512F
> >> ( AVX2:
> [AVX512F], ) ?
>
> Yes, that's what I think we want, but we need Andrew's agreement here.
>
> >>> Hi
On 25/07/16 07:09, Kang, Luwei wrote:
First of all - please don't top post.
> What about remove the dependency between AVX2 and AVX512F
>> ( AVX2:
[AVX512F], ) ?
Yes, that's what I think we want, but we need Andrew's agreement here.
>>> Hi Andrew, what is your
> >> First of all - please don't top post.
> >>
> >>> What about remove the dependency between AVX2 and AVX512F
> ( AVX2:
> >> [AVX512F], ) ?
> >>
> >> Yes, that's what I think we want, but we need Andrew's agreement here.
> >>
> > Hi Andrew, what is your opinion ?
>
> You are in a better
On 07/07/16 03:42, Kang, Luwei wrote:
>
>> -Original Message-
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Tuesday, July 5, 2016 3:03 PM
>> To: Kang, Luwei
>> Cc: andrew.coop...@citrix.com; chao.p.p...@linux.intel.com; xen-
>> de...@lists.xen.org
>>
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Tuesday, July 5, 2016 3:03 PM
> To: Kang, Luwei
> Cc: andrew.coop...@citrix.com; chao.p.p...@linux.intel.com; xen-
> de...@lists.xen.org
> Subject: RE: [PATCH v4] x86/cpuid: AVX-512 Feature
>>> On 05.07.16 at 04:31, wrote:
First of all - please don't top post.
> What about remove the dependency between AVX2 and AVX512F ( AVX2: [AVX512F],
> ) ?
Yes, that's what I think we want, but we need Andrew's agreement
here.
> From: Jan Beulich
What about remove the dependency between AVX2 and AVX512F ( AVX2: [AVX512F], ) ?
-Original Message-
From: Jan Beulich [mailto:jbeul...@suse.com]
Sent: Friday, July 1, 2016 3:56 PM
To: andrew.coop...@citrix.com; Kang, Luwei
Cc: chao.p.p...@linux.intel.com;
>>> On 30.06.16 at 07:50, wrote:
> --- a/xen/tools/gen-cpuid.py
> +++ b/xen/tools/gen-cpuid.py
> @@ -243,6 +243,17 @@ def crunch_numbers(state):
> # AMD K6-2+ and K6-III processors shipped with 3DNow+, beyond the
> # standard 3DNow in the earlier K6
AVX-512 is an extention of AVX2. Its spec can be found at:
https://software.intel.com/sites/default/files/managed/b4/3a/319433-024.pdf
This patch detects AVX-512 features by CPUID.
Signed-off-by: Luwei Kang
---
[V4]:
Update the description about features dependency.
[V3]:
15 matches
Mail list logo