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-ia64-devel

Re: [Xen-ia64-devel] [RFC][PATCH 0/3] xen&domain gdb debugger

Hi Yamahata-san,

Thank you for your each comment. 

Yes, I thought a new hypercall. Actually in early stage,
I implemented a peek/poke hypercall. 
I don't care the performance of debugging but no modification of dom0.
If a new hypercall is added, dom0 must be modified to utilize
xencomm. So I dare to use xc_map_foreign_range(). I don't just like
to re-compile RHEL5.x kernel for debugging.

I'd like to support x86 also in the future. So a new hypercall would
be worth considering.

Thanks,
Kouya

Isaku Yamahata writes:
> Great. This must be usefull!
> 
> Your approach to peek/poke xen pages is to map them into dom0
> which is ia64 specific.
> How about adding a new hypercall peek/poke pages?
> Although such a hypercall won't be suitable to read/write many data,
> they would be arch generic so that it would be applicable to x86 too.
> Looking into the patch to gdb, it maps, read/write page and unmaps
> each time to access xen memory. So just calling peek/poke hypercall
> overhead seems acceptable. (At least at this moment.)
> -- 
> yamahata

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

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