WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] RE: [PATCH 0/6] Add memory add support to Xen

To: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: [PATCH 0/6] Add memory add support to Xen
From: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date: Sun, 28 Jun 2009 20:50:44 -0700
Accept-language: en-US
Acceptlanguage: en-US
Cc:
Delivery-date: Sun, 28 Jun 2009 20:51:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E2263E4A5B2284449EEBD0AAB751098402CCF824CD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <E2263E4A5B2284449EEBD0AAB751098402CCF824CD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acn30pHKvEHffnKqTQqSzyN8vmXgFQAkyzSQ
Thread-topic: [PATCH 0/6] Add memory add support to Xen
Jiang, Yunhong wrote on Sun, 28 Jun 2009 at 02:26:51:

> 
> There are several option to support it.
> a) Move the ACPI event to Xen HV, that is sure to be a big changes.
> b) Add some hook in Dom0, so that instead of add the new memory to dom0,
> it will use hypercall to notify Xen HV.
> c) Change current dom0 implementation. When dom0 get the ACPI event and
> get the memory device's resource, it will not directly add the memry to
> system, instead, it will notify user space with uevent. The uevent
> script will ask kernel to add the new memory to system. In Xen
> environment, the uevent script will notify Xen HV. We are still
> investigating on this option.
> 
> We are in early stage . any suggestion or new idea will be helpful to
> us and welcome.
> 

I think the option b is the practical choice because the kernel typically has a 
well-defined routine for that, and the maintenance cost of the diff for dom0 
should be very low. The option c may not work for other OS like Solaris...

Jun
___
Intel Open Source Technology Center




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel