Skip to contentSkip to conversation

oprofile broken by sysfs updates

DISCUSSION Pavel Machek 3 participants 3 messages Jun 11, 2003

lore
Share & tools
lore
#0 lore raw

Hi!

I only tried reading the diffs, but:

arch/i386/oprofile/nmi_int.c must be suspended before arch/i386/kernel/apic.c is.

How is that guaranteed with new code?

-static struct device device_nmi = {

-       .name   = "oprofile",
-       .bus_id = "oprofile",
-       .driver = &nmi_driver,
-       .parent = &device_lapic.dev,
+static struct sys_device device_oprofile = {
+       .id     = 0,
+       .cls    = &oprofile_sysclass,

};

Pavel

Signature · 2 lines
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
#1 lore raw
Quoted 2 lines

I only tried reading the diffs, but:

Then maybe you should

a) Read the entire initial thread (which you participated in), esp this message:

http://marc.theaimsgroup.com/?l=linux-kernel&m=105518049424749&w=2

b) Read the comments in the code (from drivers/base/sys.c):

/**
* sysdev_shutdown - Shut down all system devices.
*

 *      Loop over each class of system devices, and the devices in each
 *      of those classes. For each device, we call the shutdown method for
 *      each driver registered for the device - the globals, the auxillaries,
 *      and the class driver. 
 *
 *      Note: The list is iterated in reverse order, so that we shut down
 *      child devices before we shut down thier parents. The list ordering
 *      is guaranteed by virtue of the fact that child devices are registered
 *      after their parents. 

*/

c) Try using the code and stop being a troll.

Thanks,

-pat