[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080306180559.GA14934@suse.de>
Date: Thu, 6 Mar 2008 10:05:59 -0800
From: Greg KH <gregkh@...e.de>
To: Balaji Rao <balajirrao@...il.com>
Cc: kvm-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Mark kobjects as unitialized
On Thu, Mar 06, 2008 at 11:20:50PM +0530, Balaji Rao wrote:
> On Thursday 06 March 2008 10:35:14 pm Greg KH wrote:
> <snip>
> > Where exactly in the code does that happen? kobjects should not be
> > "reused" as that implies that they are static, and not dynamically
> > allocated, right?
> >
> > Which kobject is this?
> Yes, its static. Here's the code from virt/kvm_main.c:1269
>
> static struct sys_device kvm_sysdev = {
> .id = 0,
> .cls = &kvm_sysdev_class,
> };
>
> this sys_device is being registered/unregistered when kvm-intel is
> loaded/unloaded.
Ah, ok. I'll add this patch then.
> > Ugh, is this the sys_device stuff? I hate that code...
> >
> Yes it is! But, why do you hate it ?
For reasons like this :)
kobjects should not be static. the sysdevice stuff was a hack when it
was originally created and never touched since the mid 2.5 days. It
needs to be fixed up a lot, and is on my TODO list, slowly getting
closer to the top...
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists