However, regarding the logic, I have a few doubts -
1. for each cpu in drv-cpumask, if there is already a driver
registered, its calling __cpuidle_unset_driver which loops over for
each cpu in drv-cpumask again. Isn't it unnecessary to do this nested
calls?
It is to rollback the previous
Hi,
i am new to kernelnewbie. I would like to work on the VFS/Filesystem sub
system. Any guidance towards the same is much appreciated.
RegardsManoj ___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
On Fri, 22 Aug 2014 21:39:42 +0530, manoj kumar said:
i am new to kernelnewbie. I would like to work on the VFS/Filesystem sub
system. Any guidance towards the same is much appreciated.
Step 0: Figure out *why* you want to work on filesystems, pick a *specific*
goal, and pick up a basic
On 8/20/2014 2:33 AM, Rohan Puri wrote:
On Tue, Aug 19, 2014 at 10:04 PM, Loris Degioanni lo...@draios.com wrote:
Sure, here's some more context.
I'm one of the developers of sysdig (www.sysdig.org), a tool that
captures system calls and uses them to offer advanced system monitoring.
One of
HI
here is the problem:
I am trying to compile mesa in a x86 system. After installing all the
required packages and ussing the following configure command line:
./configure --with-dri-drivers=i915 --with-gallium-drivers=
make
show this error:
loader.c:495:24: fatal error: radeon_drm.h: No
On Sat, Aug 23, 2014 at 12:33 AM, Loris Degioanni lo...@draios.com wrote:
On 8/20/2014 2:33 AM, Rohan Puri wrote:
On Tue, Aug 19, 2014 at 10:04 PM, Loris Degioanni lo...@draios.com
wrote:
Sure, here's some more context.
I'm one of the developers of sysdig (www.sysdig.org), a tool that
