[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-ia64-devel] Enabling hypercalls from VT-i domain
- To: "DOI Tsunehisa" <Doi.Tsunehisa@xxxxxxxxxxxxxx>, "xen-ia64-devel" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
- From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
- Date: Wed, 2 Aug 2006 21:03:23 +0800
- Delivery-date: Wed, 02 Aug 2006 06:04:15 -0700
- List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
- Thread-index: Aca2H7+M13de22UhRGypf49iOgYjGQAFC3Yw
- Thread-topic: [Xen-ia64-devel] Enabling hypercalls from VT-i domain
> My name is Tsunehisa Doi.
Welcome,
--Anthony
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of DOI
>Tsunehisa
>Sent: 2006年8月2日 18:34
>To: xen-ia64-devel
>Subject: [Xen-ia64-devel] Enabling hypercalls from VT-i domain
>
>Hi all,
>
> My name is Tsunehisa Doi.
>
> We are porting Steven Smith's para drivers for full-VM to IPF.
>In the xen-unstable.hg (cs: 10883-10885), it's enabling the hypercall
>from HVM domain. Thus, I will post the enabling patch for IPF. This
>patch includes:
>
> + cleanup the hypercall handling code for VT-i domain
> - delete the dead code in vmx_hypercall.c and vmx_ivt.S
> - the code is not used now, I think.
> * It's called with `break 0x1100' instruction. (current 0x1000)
> * The hypercall table for VT-i domain doesn't match the
> hypercall number.
> * The register used for hypercall are different with current
> version. (r16-r20 vs. r2,r4-r18)
> + enabling hypercalls from VT-i domain
> - modify the checker to permit hypercalls from VT-i domain.
>
>Thanks,
>- Tsunehisa Doi
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel