| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
RE: [Xen-ia64-devel] [PV-on-HVM] Hypercall optimizations
Hi Kasai,
For PV-on-HVM, it needs to implement hypercall stub itself.
This stub needs to be implemented by a function call.
> It is necessary to export functio of __ hypercall() in
> unmodified_drivers. However, function of __hypercall() is defined by
> assembler code.
>
I don't quite understand this question.
Even __hypercall() is definded by assembler code.
It can be exported by using EXPORT_SYMBOL(__hypercall) in some C file.
- Anthony
Kasai Takanori write on 2007年1月23日 20:23:
> Hi All,
>
> We tested pv-on-hvm.
> But pv-on-hvm doesn't work by Hypercall optimizations.
> ・xen-ia64-unstable.hg : 13367
> [IA64] Hypercall optimizations
>
> If we load xen-platform-pci.ko, the following errors occur.
>
> # insmod xen-platform-pci.ko
> xen_platform_pci: Unknown symbol __hypercall
> insmod: error inserting 'xen-platform-pci.ko': -1 Unknown symbol in
> module
>
> It is necessary to export functio of __ hypercall() in
> unmodified_drivers. However, function of __hypercall() is defined by
> assembler code.
>
> How should we define function of __hypercall() in unmodified_drivers?
> Then, how should export symbol of __hypercall()?
>
> Best Regards,
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
| |
|
Home