[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] passing hypercall parameters by pointer
>>>>> "IP" == Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> writes: IP> Post 3.0 we can completely redo the dom0 op interface, but the rest of IP> the hypercall interface will have to remain backward compatible, at IP> least for x86_*. Just to clarify, "the rest" refers to hypercalls made from the kernel, correct? Any hypercall using VAs made from user space are at issue here. IP> Since passing by VA is so convenient on the architectures that IP> support it we may not want to do anything different on these IP> anyhow. I agree, why create a new mapping when a usable one exists. At least for common kernel code, we will need to wrap such VAs in a macro so that the "psuedo-physical" is passed in for PPC. I assume this is reasonable? -JX -- "I got an idea, an idea so smart my head would explode if I even began to know what I was talking about." -- Peter Griffin (Family Guy) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |