Since the idea here is to correctly log a user-generated error (user-cpuid
> detected cpuid), the patch is headed in the right direction.
Min's suggestion on using an AND mask sounds good, and can you also make
the warning more informative (print user-cpuid, and the cpuid we're
defaulting to) ?
Ok. I will check if we can use AND mask and provide more information to
user.
On Tue, Nov 3, 2015 at 10:36 AM, Deepthi Nandakumar <
deep...@multicorewareinc.com> wrote:
> Since the idea here is to correctly log a user-generated error (user-cpuid
> > detected cpuid), the patch is headed in the
On 10/28, dnyanesh...@multicorewareinc.com wrote:
> # HG changeset patch
> # User Dnyaneshwar G
> # Date 1446021877 -19800
> # Wed Oct 28 14:14:37 2015 +0530
> # Node ID 975087370d14e90cd63edecb34fb4bf2feda2468
> # Parent
At 2015-10-28 16:45:33,dnyanesh...@multicorewareinc.com wrote:
># HG changeset patch
># User Dnyaneshwar G
># Date 1446021877 -19800
># Wed Oct 28 14:14:37 2015 +0530
># Node ID 975087370d14e90cd63edecb34fb4bf2feda2468
># Parent
# HG changeset patch
# User Dnyaneshwar G
# Date 1446021877 -19800
# Wed Oct 28 14:14:37 2015 +0530
# Node ID 975087370d14e90cd63edecb34fb4bf2feda2468
# Parent 6563218ce342c30bfd4f9bc172a1dab510e6e55b
fix invalid Instruction Set provided in CLI if CPU