Re: memblock_reserve or memblock_remove to reserve a page

On Wed, Sep 14, 2016 at 3:17 PM, Nikhil Utane wrote: > Thank You MH Chen for your response. > > So does that mean with memblock_reserve(), a kernel module can call > phys_to_virt(), create a linear mapping and modify that memory? > Where as with memblock_remove(), a

device_create_file() and device_remove_file()

Hi im looking at the driver: drivers/staging/olpc_dcon/olpc_dcon.c (trying to clean up __ATTR with DEVICE_ATTR_RO/_RW) line 663 creates sysfs files(in a for) : .. rc = device_create_file(_device->dev, _device_files[i]); if (rc) { dev_err(_device->dev, "Cannot create sysfs file\n");

Changing RT task to a different cgroup

When I try to move a RT task to a different cgroup(shown below) I get a EINVAL error. However I can change the cgroup first and then change the sched policy. After looking into kernel source code(*I dont use CONFIG_RT_GROUP_SCHED config*) I was able to extract this piece of logic *chrt -p

Re: memblock_reserve or memblock_remove to reserve a page

Thank You MH Chen for your response. So does that mean with memblock_reserve(), a kernel module can call phys_to_virt(), create a linear mapping and modify that memory? Where as with memblock_remove(), a kernel module can call ioremap() and then modify the memory? What would explain that only in