From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: Hypercall invoking Date: Tue, 10 May 2016 09:32:31 +0200 Message-ID: <1462865551.4858.9.camel@citrix.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6267609515789718504==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: tutu sky , "Xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org --===============6267609515789718504== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="=-SVRiOes+PYeabYjzp+Hq" --=-SVRiOes+PYeabYjzp+Hq Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2016-05-10 at 06:49 +0000, tutu sky wrote: > Hi, > I added a new hypercall to xen successfully, but when i try to invoke > it in dom0 using privcmd, i am unable to invoke (using XC), I must cd > to /xen.x.y.z/tools/xcutils and then try to invoke hypercall by XC > interface which i created for it. > DO functions of hypercall is written in /xen/common/kernel.c. >=20 > can you give me a clue? > That depends on what you are trying to achieve, and on what you have implemented and how you have implemented it. Actually, this is not the first time we tell you this: without you being specific, we can't possibly help. In this case, "being specific" would have meant specifying: =C2=A0- what is your final end goal =C2=A0- what is your plan to reach it =C2=A0- what you have implemented already of such plan Showing the code of what you have already implemented is, in theory, not strictly necessary, but it would help a lot (and may become necessary, at some point, for being able to help you effectively). Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-SVRiOes+PYeabYjzp+Hq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJXMY6PAAoJEBZCeImluHPuXnAP/iZv9qjMBoISQvdsEuO9i2GJ TulV23Kq0QWKCfhkR/rtGkwRoPNfiG8zLbL61kFCL/UuIrNWvXXCaBQ6zaltuMwH p6VqbWVP3hcBry8UwVTrf8Xre2hSDrpABTKkFfSG/RNbxClj53TC8WmR6+6JGDj5 mjisALpwDDiGXyiCC1FEMCQQzuh8erfJeDsfzH25PYNNIJOMICYTiX4OAg8NlbFg 1CXVjXNLPyPKXgMZI1ttVti+qpxxeWpm+R9O9KhbtmwHTFY2x6/89v42oE+eeX3M Vz02j13G2lJ6uF3DsLi2MZSi9zHCZ2Wdzqfk6aRZSU8mVkALeLCmbBIX/Bq4b9mF esT08/aunegMzebd0mhcr1WC2H737kFo7PaaWDTT20UKF5lVssCJe3xVrymbnTF4 rCgTBK7J+jX6O0IBrAbL/zwGBBiZ0NPqoh6zCNhf+qVy1IclxpDot2O1Ckg7absQ w0WvSigW0b9XxBmZ160z78yxjbGtwGjvYMF3E2PMshlT34/zsM7F4SJlhKRCuq8W ZkZCu/fdtAWJGxZpWgg5k1uTYNUQ92Hh5tomuvQqK7GaHtmpKzbZrjatpir+PZzt pQsAhAMX4VGXfnngijiMT/rSzK0hug49+Bemy8usL0c0a69DUU+LA5SRU55l7fIG 4eIWMdb7zGdPKG4z7AB9 =AcNV -----END PGP SIGNATURE----- --=-SVRiOes+PYeabYjzp+Hq-- --===============6267609515789718504== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy94ZW4tZGV2ZWwK --===============6267609515789718504==--