[Xen-ia64-devel] RE: [Patch] Add uaccess utility for VTI

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

Will do.  

But don't you need to use some kind of lock?
E.g. what happens if the machine address changes
(due to migration or ballooning or ...) between the
call to __domain_va_to_ma and the use of the ma?

Also, why is Xen/ia64-VTI different?  Linux/x86,
Linux/ia64, Xen/x86(non-VTx), Xen/ia64(non-VTi),
and (I think) Xen/x86-VTx all just do the access
and manage misses as an exception.  Your approach
is better if the mapping is missing more often
than it is present, but how often will this be
true?

Thanks,
Dan 

> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx] 
> Sent: Tuesday, June 21, 2005 12:04 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Patch] Add uaccess utility for VTI
> 
> Hi, Dan,
>       Attached patch adds necessary put/get_user, 
> copy_from/to_user, etc stuff for VTI. Please apply.
> 
> Signed-off-by Kevin Tian <Kevin.tian@xxxxxxxxx>
>  
>  include/asm-ia64/vmx_uaccess.h       |  156 [New]
>  arch/ia64/vmmu.c                     |   52 +++++++++++++
>  include/asm-ia64/uaccess.h           |    5 +
> +++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 213 insertions(+)
> 
> Thanks,
> Kevin
> 

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