|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
RE: Hypercall number assignment convension (was Re: [Xen-devel]	Re:[PATC
 
| 
To:  | 
"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> | 
 
| 
Subject:  | 
RE: Hypercall number assignment convension (was Re: [Xen-devel]	Re:[PATCH]: kexec: framework and i386) | 
 
| 
From:  | 
"Tian, Kevin" <kevin.tian@xxxxxxxxx> | 
 
| 
Date:  | 
Wed, 26 Apr 2006 16:07:37 +0800 | 
 
| 
Cc:  | 
xen-devel@xxxxxxxxxxxxxxxxxxx, Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>,	Isaku Yamahata <yamahata@xxxxxxxxxxxxx>,	Magnus Damm <magnus@xxxxxxxxxxxxx>, Horms <horms@xxxxxxxxxxxx>,	Mark Williamson <mark.williamson@xxxxxxxxxxxx> | 
 
| 
Delivery-date:  | 
Wed, 26 Apr 2006 01:08:16 -0700 | 
 
| 
Envelope-to:  | 
www-data@xxxxxxxxxxxxxxxxxx | 
 
| 
List-help:  | 
<mailto:xen-devel-request@lists.xensource.com?subject=help> | 
 
| 
List-id:  | 
Xen developer discussion <xen-devel.lists.xensource.com> | 
 
| 
List-post:  | 
<mailto:xen-devel@lists.xensource.com> | 
 
| 
List-subscribe:  | 
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe> | 
 
| 
List-unsubscribe:  | 
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> | 
 
| 
Sender:  | 
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx | 
 
| 
Thread-index:  | 
AcZpB3F3PbRzHlhYTWaEo8XidkipmQAAPSWw | 
 
| 
Thread-topic:  | 
Hypercall number assignment convension (was Re: [Xen-devel]	Re:[PATCH]: kexec: framework and i386) | 
 
 
 
>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2006年4月26日 15:56
>
>On 26 Apr 2006, at 08:54, Tian, Kevin wrote:
>
>> Then we may need to fill that breathing space with do_ni_hypercall
>> to ensure no leakage from NR_hypercall check. If that's the case,
>> how about define the __HYPERVISOR_arch_* at end of 256 spaces,
>> and fill all unused entries with do_ni_hypercall. By that way, the
>> check
>> to illegal hypercall (<256) is a bit slower, however it shouldn't
>> matter
>> for that rare cases.
>
>Yes, it would need filling with ni_hypercall: we already do that on x86
>anyway (since hypercall table is rounded up to a power of two).
>
>I don't want to put the hypercalls that far up: with one hypercall page
>x86 will currently have a problem implementing more than 128
>hypercalls. I also don't want to put them right at the end of the
>hypercall space because that would make it harder/uglier to add extra
>arch hypercalls later on.
>
>I think 48-55 would be reasonable.
>
>  -- Keir
OK, that makes sense.
Thanks,
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 |   
 
 | 
    | 
  
  
    |   | 
    |