[Xen-ia64-devel] [PATCH] xencomm: tmem support.

2009-06-19 Thread Isaku Yamahata
[IA64] xencomm: tmem support. add tmem support to xencomm. Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp diff --git a/arch/ia64/xen/xcom_hcall.c b/arch/ia64/xen/xcom_hcall.c --- a/arch/ia64/xen/xcom_hcall.c +++ b/arch/ia64/xen/xcom_hcall.c @@ -40,6 +40,7 @@ #include

[Xen-ia64-devel] [PATCH] xencomm support for multi call with physdev_op and event_channel_op.

2008-12-02 Thread Isaku Yamahata
IA64: xencomm support for multi call with physdev_op and event_channel_op. Recently the c/s of d545a95fca73 makes use of multi call with __HYPERVISOR_event_channel_op and __HYPERVISOR_physdev_op. This patch adds support of those hypercall. Signed-off-by: Isaku Yamahata [EMAIL PROTECTED] diff

[Xen-ia64-devel] [PATCH] xencomm: support XENMEM_add_to_physmap and XENMEM_remove_from_phsymap

2008-09-09 Thread Isaku Yamahata
Note: this patch depends on the c/s of 653:8566781df55e which updates include/xen/interface/memory.h. [IA64] xencomm: support XENMEM_add_to_physmap and XENMEM_remove_from_phsymap support XENMEM_add_to_physmap and XENMEM_remove_from_phsymap. Signed-off-by: Isaku Yamahata [EMAIL PROTECTED] diff

[Xen-ia64-devel] [PATCH] xencomm: support PHYSDEVOP_manage_pci_add/remove.

2008-07-24 Thread Isaku Yamahata
[IA64] xencomm: support PHYSDEVOP_manage_pci_add/remove. add support PHYSDEVOP_manage_pci_add/remove which were newly added. Signed-off-by: Isaku Yamahata [EMAIL PROTECTED] diff -r 65290c01dca0 arch/ia64/xen/xcom_hcall.c --- a/arch/ia64/xen/xcom_hcall.cThu Jul 24 14:31:47 2008 +0900 +++

[Xen-ia64-devel] [PATCH] xencomm: fix dirty page leak

2008-04-09 Thread Kouya Shimura
This patch fixes a dirty page leak for live migration. The common part of this fix is already applied to upstream. http://xenbits.xensource.com/xen-unstable.hg?rev/146f214a0e63 Thanks, Kouya Signed-off-by: Kouya Shimura [EMAIL PROTECTED] diff -r feee6422144f xen/arch/ia64/xen/mm.c ---

[Xen-ia64-devel] [PATCH] [xencomm, xen] use common xencomm.c and remove ia64 xencomm.c

2007-08-07 Thread Isaku Yamahata
# HG changeset patch # User [EMAIL PROTECTED] # Date 1186475123 -32400 # Node ID 8b6af0333d531d1fd63b1ce02c2df51b0d4f45f5 # Parent 6f18f5bdeea3473766929f9caa10cc163a411aa3 use common xencomm.c and remove ia64 xencomm.c PATCHNAME: use_common_xencomm_c_and_remove_ia64_xencomm_c Signed-off-by:

[Xen-ia64-devel] [PATCH] xencomm update for acm interface change

2007-06-12 Thread Isaku Yamahata
xencomm update for acm interface change by c/s 15189:96915ca8d5f2 of xen-unstable.h -- yamahata # HG changeset patch # User [EMAIL PROTECTED] # Date 1181649851 -32400 # Node ID 287794cccd22e7de3ea3f96beff87a4c114bbf30 # Parent 245902ee7ce0c1499c172b3a9240b8e2ede45a5f xencomm update for acm

Re: [Xen-ia64-devel] [PATCH] xencomm update for acm interface change

2007-06-12 Thread Alex Williamson
On Tue, 2007-06-12 at 21:14 +0900, Isaku Yamahata wrote: xencomm update for acm interface change by c/s 15189:96915ca8d5f2 of xen-unstable.h Applied. Thanks, Alex -- Alex Williamson HP Open Source Linux Org.

[Xen-ia64-devel] [PATCH] xencomm, xenmem and hypercall continuation

2006-11-09 Thread Isaku Yamahata
fix xenmem hypercall for non-trivial xencomm arch(i.e. ia64, and powerpc) On ia64 and powerpc, guest_handle_add_offset() effect persists over hypercall continuation because its consumed offset is recorced in guest domains memory space. On the other hand, x86 guest_handle_add_offset() effect is

[Xen-ia64-devel] PATCH: xencomm fixes for HVM PV drivers and driver domain

2006-10-06 Thread Tristan Gingold
Hi, Two fixes for xencomm glitches. Tested by booting driver domU. Tristan. # HG changeset patch # User [EMAIL PROTECTED] # Node ID 0b2f6318af669fa3f1092f1d1e9cb5a048792d99 # Parent 1a0b58e7b5de8c666b19d3063658d9a3c25e9bea Xencomm fixes for HVM PV-drivers and driver domain. Create xcom_mini.c

Re: [Xen-ia64-devel] PATCH: xencomm [2]

2006-10-02 Thread Akio Takebe
Hi, Aron However on ia64 this isn't sufficient. We need either for the modules to load *earlier* (such as in the initramfs) or we need to use dom0_mem=1G (for example) I have some questions, though: 1. On x86, all of the memory is assigned to dom0, then it balloons to give memory to

Re: [Xen-ia64-devel] PATCH: xencomm [2]

2006-10-02 Thread Akio Takebe
Hi, Aron I checked the fragmentation on xen/ia64 with on xen/x86. The following data is /proc/budddyinfo after starting each daemons. 1. buddyinfo of ia64 at the boottime. (dom0_mem=512MB) Mon Oct 2 20:42:24 JST 2006 --iptables--- Node 0, zone DMA 1 2 1

Re: [Xen-ia64-devel] PATCH: xencomm [2]

2006-10-02 Thread Aron Griffis
Akio Takebe wrote: [Mon Oct 02 2006, 08:45:22AM EDT] The following data is /proc/budddyinfo after starting each daemons. 1. buddyinfo of ia64 at the boottime. (dom0_mem=512MB) Mon Oct 2 20:42:24 JST 2006 ---iptables---Node 0, zone DMA 1 2 1 1 1 1 0 0 0 1 9 ---portmap---

Re: [Xen-ia64-devel] PATCH: xencomm [2]

2006-09-29 Thread Tristan Gingold
Le Vendredi 29 Septembre 2006 16:14, Aron Griffis a écrit : Hi Tristan, Tristan Gingold wrote: [Thu Sep 28 2006, 07:33:28AM EDT] My tests were booting dom0+2*dom_U (using netbk, blkbk and netloop as modules), and doing ping+wget from domU_1. I tested these patches on the Fedora rawhide

Re: [Xen-ia64-devel] PATCH: xencomm [2]

2006-09-29 Thread Akio Takebe
Hi, Aron I think this issue do not relate xencomm and copy_from/to_user. This issue is caused by page_alloc of net/blkbk module. order:8 is too big. After forked and terminated some process, alloc_page() of oder:8 almost fail. So builtin module don't have this issue because none of process is

Re: [Xen-ia64-devel] PATCH: xencomm [2]

2006-09-29 Thread Tristan Gingold
Le Vendredi 29 Septembre 2006 16:35, Akio Takebe a écrit : Hi, Aron I think this issue do not relate xencomm and copy_from/to_user. This issue is caused by page_alloc of net/blkbk module. order:8 is too big. After forked and terminated some process, alloc_page() of oder:8 almost fail. So

Re: [Xen-ia64-devel] PATCH: xencomm [2]

2006-09-29 Thread Aron Griffis
Tristan Gingold wrote: [Fri Sep 29 2006, 10:44:48AM EDT] Does this bug occur on x86 ? No. Aron ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel

Re: [Xen-ia64-devel] PATCH: xencomm [2]

2006-09-29 Thread Akio Takebe
Hi, Aron Tristan Gingold wrote: [Fri Sep 29 2006, 10:44:48AM EDT] Does this bug occur on x86 ? No. Aron Hmmm... But this issue was happened on x86-PAE. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201796 Actually with dom0_mem=512M on FC6-ia64, we can success installing blkbk on rare

Re: [Xen-ia64-devel] PATCH: xencomm [2]

2006-09-29 Thread Aron Griffis
Akio Takebe wrote: [Fri Sep 29 2006, 11:41:57AM EDT] Hmmm... But this issue was happened on x86-PAE. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201796 Actually with dom0_mem=512M on FC6-ia64, we can success installing blkbk on rare occasions. On PAE the problem was fixed by

Re: [Xen-ia64-devel] PATCH: xencomm [2]

2006-09-28 Thread Akio Takebe
Hi, Tristan I tried to test your patches. And I don't meet the network issue. good work!!! I'll try to test my network load test. I had some unaligned access message. For your infomation, I show the log. PING 10.124.36.60 (10.124.36.60) 56(84) bytes of data. kernel unaligned access to

Re: [Xen-ia64-devel] PATCH: xencomm

2006-09-27 Thread Akio Takebe
Hi, Tristan I tested your patch. But after I enabled network on domU and pinged another machine, the following message is shown, then domU hang up. I try to check your patches. [EMAIL PROTECTED] ~]# BUG: soft lockup detected on CPU#0! Modules linked in: netloop xennet xenblk

[Xen-ia64-devel] PATCH: xencomm - kernel side

2006-08-23 Thread Tristan Gingold
Hi, taking into account Hollis comments I now submit this patch. IA64 specific stuff will be posted to xen-ia64-unstable after merge. Tristan. # HG changeset patch # User [EMAIL PROTECTED] # Node ID ba96f5f81464dc3db80af0454fb05c73de620637 # Parent cc7a78171c811b9caa5587a0141d8c8477d10ce8