[Xen-ia64-devel] Re: [Xen-devel] [Patch] [RFC] avoid debugger_trap when we don't expect

2008-01-30 Thread Keir Fraser
This doesn't need to be fixed on x86 -- the int3 handler will return silently if the debugger is not configured. It would be nice if the ia64 handler would do the same. If that is not possible then change only ia64 code and if you need to be able to probe gdbstub configuration then add a public

[Xen-ia64-devel] flush cache after patch kernel

2008-01-30 Thread Duan, Ronghui
Need flushing cache here, if not, i/d cache may be not synchronous. Signed-off-by: Duan Ronghui [EMAIL PROTECTED] diff -r 32ec5dbe2978 xen/arch/ia64/xen/xenpatch.c --- a/xen/arch/ia64/xen/xenpatch.c Fri Nov 30 08:54:33 2007 -0700 +++ b/xen/arch/ia64/xen/xenpatch.c Wed Jan 30 14:47:46

[Xen-ia64-devel] Re: [Xen-devel] [Patch] [RFC] avoid debugger_trap when we don't expect

2008-01-30 Thread Akio Takebe
Hi, Keir This doesn't need to be fixed on x86 -- the int3 handler will return silently if the debugger is not configured. It would be nice if the ia64 handler would do the same. If that is not possible then change only ia64 code and if you need to be able to probe gdbstub configuration then add a

[Xen-ia64-devel] Re: [Xen-devel] [Patch] [RFC] avoid debugger_trap when we don't expect

2008-01-30 Thread Keir Fraser
On 30/1/08 08:48, Akio Takebe [EMAIL PROTECTED] wrote: This doesn't need to be fixed on x86 -- the int3 handler will return silently if the debugger is not configured. It would be nice if the ia64 handler would do the same. If that is not possible then change only ia64 code and if you need to

[Xen-ia64-devel] Paravirt_ops/hybrid directions and next steps

2008-01-30 Thread Alex Williamson
Hi all, A few of us from the various companies working on Xen/ia64 and Red Hat had a phone conference to discuss requirements and directions for getting the XenLinux parts of Xen/ia64 into upstream and future Red Hat releases. This was partially spurred by my questions on the mailing list

[Xen-ia64-devel] Re: [Xen-devel] [Patch] [RFC] avoid debugger_trap when we don't expect

2008-01-30 Thread Akio Takebe
Hi, Keir On 30/1/08 08:48, Akio Takebe [EMAIL PROTECTED] wrote: This doesn't need to be fixed on x86 -- the int3 handler will return silently if the debugger is not configured. It would be nice if the ia64 handler would do the same. If that is not possible then change only ia64 code and if

Re: [Xen-ia64-devel] paravirt_ops and its alternatives

2008-01-30 Thread Isaku Yamahata
On Thu, Jan 31, 2008 at 08:21:51AM +0800, Dong, Eddie wrote: Alex All: Hi Eddie. At first I'd like to make it clear. The goal is to merge xenLinux/ia64 modification into upstream kenrel. Hence reduce maintenane cost etc... And you want to dicuss how to do it. Is this correct? Now I'm forward

Re: [Xen-ia64-devel] paravirt_ops and its alternatives

2008-01-30 Thread Alex Williamson
Hi Isaku Eddie, On Thu, 2008-01-31 at 10:44 +0900, Isaku Yamahata wrote: On Thu, Jan 31, 2008 at 08:21:51AM +0800, Dong, Eddie wrote: Alex All: Hi Eddie. At first I'd like to make it clear. The goal is to merge xenLinux/ia64 modification into upstream kenrel. Hence reduce maintenane

RE: [Xen-ia64-devel] paravirt_ops and its alternatives

2008-01-30 Thread Dong, Eddie
Isaku Yamahata wrote: On Thu, Jan 31, 2008 at 08:21:51AM +0800, Dong, Eddie wrote: Alex All: Hi Eddie. At first I'd like to make it clear. The goal is to merge xenLinux/ia64 modification into upstream kenrel. Hence reduce maintenane cost etc... And you want to dicuss how to do it. Is

Re: [Xen-ia64-devel] paravirt_ops and its alternatives

2008-01-30 Thread Isaku Yamahata
On Wed, Jan 30, 2008 at 08:23:54PM -0700, Alex Williamson wrote: We discussed this a little on the phone conference today. It's going to be a bit of a learning curve (at least for me), but it should probably be in git. This will allow us to better coordinate with the other upstream linux

Re: [Xen-ia64-devel] paravirt_ops and its alternatives

2008-01-30 Thread Isaku Yamahata
On Thu, Jan 31, 2008 at 11:44:57AM +0800, Dong, Eddie wrote: Actually paravirt_ops version of X86 Linux doesn;t detect this. In stead, it put a special initial code in ELF Linux image and let the dom builder find it and start from that point to make sure it is on top of Xen hypervisor. For

[Xen-ia64-devel] [PATCH] Fix the domain refernece counting

2008-01-30 Thread Isaku Yamahata
Fix the domain refernece counting caused by allocated pages from domheap for shared page and hyperregister page. Calling share_xen_page_with_guest() with domain heap page is wrong so that it increments domian-xenpages which is never decremented. Thus the domian refcount doesn't decrease to 0 so

RE: [Xen-ia64-devel] [Q] About xc.domain_destroy_hook

2008-01-30 Thread Zhang, Xing Z
Hi Kan: When I implemented NVRAM, I found there were many difference shutdown ways for HVM domain. So I added hook on each flow. Maybe Xend code merged some shutdown paths. You can try to remove it to see if NVRAM still works. If fine, I think it is removable. Thx. Good good

[Xen-ia64-devel] MINSTATE_PHYS?

2008-01-30 Thread Dong, Eddie
I did a quick grep and find MINSTATE_PHYS is never defined in xenlinux. Xen mca code did. Anything missed? diff -r 71a415f9179b arch/ia64/xen/xenminstate.h --- a/arch/ia64/xen/xenminstate.h Fri Jan 18 14:20:59 2008 -0700 +++ b/arch/ia64/xen/xenminstate.h Thu Jan 31 15:08:42 2008

RE: [Xen-ia64-devel] [Q] About xc.domain_destroy_hook

2008-01-30 Thread Masaki Kanno
Hi Wing, Thanks for your reply. I removed the line from XendDomainInfo.py, then I tested the following commands. I didn't see the error message with the following commands. - xm shutdown - xm reboot - xm destroy - shutdown on guest OS - reboot on guest OS I will send a patch to solve