On 15/09/14 15:02, David Herrmann wrote:
> Hi
>
> On Mon, Sep 15, 2014 at 3:19 PM, John Haxby wrote:
>> On 12/09/14 16:03, Kay Sievers wrote:
>>> On Fri, Sep 12, 2014 at 3:04 PM, John Haxby wrote:
>>>> When I think of changing the
>>>> behaviour
On 12/09/14 16:03, Kay Sievers wrote:
> On Fri, Sep 12, 2014 at 3:04 PM, John Haxby wrote:
>> On 02/09/14 16:42, Kay Sievers wrote:
>>>>> Either the kernel has to provide a mechanism for the userspace to
>>>>> control onlining, or do it itself and provide
On 02/09/14 16:42, Kay Sievers wrote:
>> > Either the kernel has to provide a mechanism for the userspace to
>> > control onlining, or do it itself and provide a mechanism to prevent
>> > automatic onlining. I think that the first option is actually
>> > cleaner. So yeah, let's add the original rul
On 02/09/14 16:40, Kay Sievers wrote:
>>> >> But just in case someone thinks of any per-CPU onlining policy
>>> >> machinery now: We will not ship anything in that area in systemd/udev
>>> >> upstream. This stuff just belongs into the kernel, like it works for
>>> >> any other device.
>> >
>> > Do
On 02/09/14 16:23, Kay Sievers wrote:
> On Tue, Sep 2, 2014 at 5:11 PM, Colin Guthrie wrote:
>>
>> John Haxby wrote on 02/09/14 10:31:
>>> Col, forgive my ignorance, but cpuadd@$name.service seems to imply that
>>> you'd have one file or symlink per CPU. Th
On 02/09/14 09:42, Colin Guthrie wrote:
> Kay Sievers wrote on 02/09/14 09:27:
>> On Tue, Sep 2, 2014 at 10:01 AM, John Haxby wrote:
>>>
>>> On 2 Sep 2014, at 06:55, Kay Sievers wrote:
>>>
>>>> On Tue, Sep 2, 2014 at 5:22 AM, Zhenzhong Duan
>&
On 2 Sep 2014, at 06:55, Kay Sievers wrote:
> On Tue, Sep 2, 2014 at 5:22 AM, Zhenzhong Duan
> wrote:
>> Cpu doesn't get online automaticly after hotplug when we test guest cpu
>> add/remove in xen env.
>>
>> I don't have an baremetal env to test this, but I think it's same.
>>
>> The rule is
