[Mckernel-users 3] Re: Questions about McKernel

[yin at ertl.jp]

Dear Balazs,

This is Yin from Nagoya University.
I sincerely apologize for my slow response.

Thank you so much for the prompt answer.
After I disabled the SSE initialization code and compile again, linking
errors:

mckernel/kernel/syscall.c:4986: undefined reference to `ihk_mc_get_boot_time'
mckernel/kernel/syscall.c:5001: undefined reference to
`ihk_mc_get_ns_per_tsc'
mckernel/kernel/syscall.c:3500:undefined reference to `ihk_mc_get_ns_per_tsc'

are appeared.
Unfortunately I cannot find any other implementation of these two
functions in the source code since there are declared 'extern'.
So these errors are impossible to solve from using this source code version.

Looking forward to your kind response.

Best,
Yin

> Hello Yin,
>
> thanks for your interest in McKernel!
> Please see my answers inline.
>
> On Thu, May 26, 2016 at 3:50 AM, <yin at ertl.jp> wrote:
>
>> Q1: attached-mic mode is designed for running McKernel natively on
>> MIC(if I
>> didn’t misunderstand). Why the target architecture(ARCH) is x86_64 but not
>> k1om, and the compiler designated in the configure file is gcc but not
>> x86_6
>> 4-k1om-linux-gcc?
>>
>
> I believe that for the kernel code you can go with x86_64 as well, but to
> be honest
> we haven't used the KNC configuration for quite a while now.
> We've been mainly focusing on the upcoming KNL version of the Xeon Phi,
> which will be primarily standalone and for which the standard Xeon
> configuration
> is currently the most similar.
>
> Q2: During compiling using attached-mic mode, there is an error appeared:
>> error: 'xgetbv' is not supported on 'k1om'.
>> After searching in the source code, 'xgetbv' instruction is used in
>> implemen
>> ting SSE, but Xeon Phi doesn’t support SSE as I know. So I wonder whether M
>> cKernel-1.0.0 is the formal version which can be used on Intel Xeon Phi.
>
> URL at which I downloaded McKernel-1.0.0:
>> http://www.pccluster.org/ja/mckernel/download.html
>
>
> The version you are using is mainly for partitioning a Xeon chip.
> I am currently away and I am not sure how soon I can investigate this, but
> we could
> try doing it together.
>
> Have you tried to disable the SSE initialization code and compile/boot
> that
> way?
>
> Best regards,
> Balazs
>
>
>>
>> I'm looking forward to your kind response.
>>
>> Thank you,
>> Yin
>>
>>
>>
>>
>> _______________________________________________
>> Mckernel-users mailing list
>> Mckernel-users at new1.pccluster.org
>> http://new1.pccluster.org/mailman/listinfo/mckernel-users
>>
>