lkml.org 
[lkml]   [2017]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: A udev rule to serve the change event of ACPI container?
    On Mon 26-06-17 10:59:07, Michal Hocko wrote:
    > On Mon 26-06-17 14:26:57, Joey Lee wrote:
    > > Hi all,
    > >
    > > If ACPI received ejection request for a ACPI container, kernel
    > > emits KOBJ_CHANGE uevent when it found online children devices
    > > below the acpi container.
    > >
    > > Base on the description of caa73ea15 kernel patch, user space
    > > is expected to offline all devices below the container and the
    > > container itself. Then, user space can finalize the removal of
    > > the container with the help of its ACPI device object's eject
    > > attribute in sysfs.
    > >
    > > That means that kernel relies on users space to peform the offline
    > > and ejection jobs to acpi container and children devices. The
    > > discussion is here:
    > > https://lkml.org/lkml/2013/11/28/520
    > >
    > > The mail loop didn't explain why the userspace is responsible for
    > > the whole container offlining. Is it possible to do that transparently
    > > from the kernel? What's the difference between offlining memory and
    > > processors which happends without any cleanup and container which
    > > does essentially the same except it happens at once?
    > >
    > > - After a couple of years, can we let the container hot-remove
    > > process transparently?
    > > - Except udev rule, does there have any other mechanism to trigger
    > > auto offline/ejection?
    >
    > I would be also interested whether the kernel can simply send an udev event
    > to all devices in the container.

    Any opinion on this?
    --
    Michal Hocko
    SUSE Labs

    \
     
     \ /
      Last update: 2017-07-11 10:25    [W:4.502 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site