Re: [Xen-ia64-devel] Question about evtchn_vector

2006-05-10 Thread Tristan Gingold 
Le Mercredi 10 Mai 2006 09:23, Tian, Kevin a écrit :
 From: Tristan Gingold [mailto:[EMAIL PROTECTED]

 Sent: 2006年5月10日 15:05
 
 Le Mercredi 10 Mai 2006 04:57, Tian, Kevin a écrit :
  From:Tristan Gingold
 
  Sent: 2006年5月9日 23:22
  
  Hi,
  
  currently evtchn_vector is a field of vcpu_info.  I think it should be
   a field of shared_info, because it is shared by every processor.
   Comment ?
  
  Tristan.
 
  Yes, that vector is domain-wise. However do you really need put it
  into shared_info? Guest doesn't access this field directly, and how
  about moving it into arch_domain?
 
 Guest access it, to initialize it!
 
 Tristan.

 If only for initialization, you can pass that vector number in
 vcpu_guest_context which is used to setup initial guest context. Then
 save passed vector into arch_domain.evtchn_vector.
No, it is dom linux which setsit.  See evtchn_ia64.c

Tristan.

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

RE: [Xen-ia64-devel] Question about evtchn_vector

2006-05-10 Thread Tian, Kevin 
From: Tristan Gingold [mailto:[EMAIL PROTECTED]
Sent: 2006年5月10日 15:31
 
  Yes, that vector is domain-wise. However do you really need put it
  into shared_info? Guest doesn't access this field directly, and how
  about moving it into arch_domain?
 
 Guest access it, to initialize it!
 
 Tristan.

 If only for initialization, you can pass that vector number in
 vcpu_guest_context which is used to setup initial guest context. Then
 save passed vector into arch_domain.evtchn_vector.
No, it is dom linux which setsit.  See evtchn_ia64.c

Tristan.

OK, domain 0 is always special. 

Thanks,
Kevin

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