|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: [PATCH V2 2/2] mm: Extend memory hotplug API to allow me
To: |
Dave Hansen <dave@xxxxxxxxxxxxxxxxxx> |
Subject: |
[Xen-devel] Re: [PATCH V2 2/2] mm: Extend memory hotplug API to allow memory hotplug in virtual machines |
From: |
Daniel Kiper <dkiper@xxxxxxxxxxxx> |
Date: |
Tue, 3 May 2011 22:13:34 +0200 |
Cc: |
jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, ian.campbell@xxxxxxxxxx, haicheng.li@xxxxxxxxxxxxxxx, konrad.wilk@xxxxxxxxxx, dan.magenheimer@xxxxxxxxxx, v.tolstov@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, rientjes@xxxxxxxxxx, andi.kleen@xxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, fengguang.wu@xxxxxxxxx, Daniel Kiper <dkiper@xxxxxxxxxxxx>, wdauchy@xxxxxxxxx |
Delivery-date: |
Tue, 03 May 2011 13:15:26 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<1304439952.30823.68.camel@nimitz> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<20110502214921.GH4623@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1304439952.30823.68.camel@nimitz> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.3.28i |
On Tue, May 03, 2011 at 09:25:52AM -0700, Dave Hansen wrote:
> On Mon, 2011-05-02 at 23:49 +0200, Daniel Kiper wrote:
> > +int register_online_page_callback(online_page_callback_t callback)
> > +{
> > + int rc = -EPERM;
> > +
> > + lock_memory_hotplug();
> > +
> > + if (online_page_callback == generic_online_page) {
> > + online_page_callback = callback;
> > + rc = 0;
> > + }
> > +
> > + unlock_memory_hotplug();
> > +
> > + return rc;
> > +}
> > +EXPORT_SYMBOL_GPL(register_online_page_callback);
>
> -EPERM is a bit uninformative here. How about -EEXIST, plus a printk?
EEXIST means File exists (POSIX.1). It could be misleading. That is why
I decided to use EPERM. I could not find any better choice. I think another
choice is EINVAL (not the best one in my opinion). Additionally, I am not
sure it should have printk. I think it is role of caller to notify (or not)
about possible errors.
> I also don't seen the real use behind having a "register" that can only
> take a single callback. At worst, it should be
> "set_online_page_callback()" so it's more apparent that there can only
> be one of these.
OK.
> > +int unregister_online_page_callback(online_page_callback_t callback)
> > +{
> > + int rc = -EPERM;
> > +
> > + lock_memory_hotplug();
> > +
> > + if (online_page_callback == callback) {
> > + online_page_callback = generic_online_page;
> > + rc = 0;
> > + }
> > +
> > + unlock_memory_hotplug();
> > +
> > + return rc;
> > +}
> > +EXPORT_SYMBOL_GPL(unregister_online_page_callback);
>
> Again, -EPERM is a bad code here. -EEXIST, perhaps? It also deserves a
> WARN_ON() or a printk on failure here.
Please look above.
> Your changelog doesn't mention, but what ever happened to doing
> something dirt-simple like this? I have a short memory.
Andrew Morton complained about (ab)use of notifiers. He suggested
to use callback machanism (I could not find any better solution
in Linux Kernel). He convinced me.
Daniel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|