linux-kernel - Re: control on cpu/core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMOw1v4aHTOr_a9FBFuQXfLGq1SVNWiWnYn-xn-mG+gQWEeiNQ@mail.gmail.com>
Date:	Fri, 5 Apr 2013 14:54:16 -0300
From:	Lucas De Marchi <lucas.demarchi@...fusion.mobi>
To:	christophe malvasio <arsdmthe@...il.com>
Cc:	linux-modules <linux-modules@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: control on cpu/core

On Fri, Apr 5, 2013 at 1:30 PM, christophe malvasio <arsdmthe@...il.com> wrote:
> hi all
> i want to give the control of one core to a module
> that is the kernel have to not schedule/interrupt execution on this
> core and also my module have to be the only thing to send execution on
> this core
> i'm not sure if i can make it only from my module or if i must hack
> the kernel too ?
> fake core unplug or more coding ?
> give me your opinion ;)

You can isolate a core during boot so no process is scheduled to that
core. See "isolcpus=" in Documentation/kernel-parameters.txt.

I don't know what your module is doing so it might not be possible in
all scenarios. The only way I see is if your module created a kernel
thread. Then it can be moved to the isolated core by setting the cpu
mask. See for example how kworker, watchdog, migration do.

I'm CCing LKML to broaden your audience. linux-modules@...r.kernel.org
is really low traffic and mostly intended for the module
loading/removal process, not really about writing modules.

Lucas De Marchi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/