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/
Home Products Support Community News


RE: [Xen-ia64-devel] MINSTATE_PHYS?

To: "Akio Takebe" <takebe_akio@xxxxxxxxxxxxxx>, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>, "xen-ia64-devel" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] MINSTATE_PHYS?
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Mon, 4 Feb 2008 09:47:07 +0800
Cc: Alex Williamson <alex.williamson@xxxxxx>
Delivery-date: Sun, 03 Feb 2008 17:50:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <BEC866A72A0097takebe_akio@xxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <10EA09EFD8728347A513008B6B0DA77A02B9FDE2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <AFC863E6A5ED9Dtakebe_akio@xxxxxxxxxxxxxx> <42DFA526FC41B1429CE7279EF83C6BDCD323A8@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <BEC866A72A0097takebe_akio@xxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchmqI+MgHEksHpZR0+6wUePNTBtKQAJh3fg
Thread-topic: [Xen-ia64-devel] MINSTATE_PHYS?
Akio Takebe wrote:
> Hi, Xiantao and all
>> Akio Takebe wrote:
>>> Hi, Eddie and Kaz
>>>> I did a quick grep and find MINSTATE_PHYS is never defined in
>>>> xenlinux. Xen mca code did. Anything missed?
>>> The minstate.h is a little old, it seems to be around linux-2.6.9.
>>> Current linux-xen is 2.6.18, so the code may be not nessesary.
>>> Kaz, do you know about it?
>> Hi, Akio & all
>>      Attached the patch did some cleanups. Please review.
> Your patch is right. But I think those defines are left for comparing
> them with native codes. 
> I want to confirm with xen-ia64 comunity.
> These files under arch/ia64/xen is only for xen.
> These are copys of native linux codes and a little old.
> So for the cleaning some files under arch/ia64/xen, we should do:
> - update them and merge the one under arch/ia64/kernel.

One of the purpose to cleanup from my point is to make the
paravirt_ops work simple. Basically we will need to look into
each changes in XenLinux tree and make sure paravirt_ops
side handle it correctly.
I assume with the pv_ops effort going on, the current xenlinux
tree will still exist for quit a long time till everything is settle
and switch to pv_ops. It could be 1 year even, and we can project 
there are other changes in xenlinux tree, and we need to port
them back to pv_ops tree. Less changes especially removing 
dead code helps for that.

> Or
> - remove CONFIG_XEN and cleanup only for xen.
> Do you think which we should do?

I did a whole diff scan for the directory arch/ia64, and
will do those simplification or merge one by one if people like to see
This patch makes Xen/xenministate.h close to kernel/ministate.h
very much. The diff is very minor now. (in pv_ops, it could be in one

[root@vti-build ia64]# diff -urN kernel/minstate.h xen/xenminstate.h
 xenminstate.h |  157
 1 files changed, 139 insertions(+), 18 deletions(-)

Something more will come. Is that what you want?

thx, eddie

Xen-ia64-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>