From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ruslan Nikolaev <nruslan_devel@yahoo.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: HVM hypercalls
Date: Fri, 30 Jul 2010 17:07:59 -0700 [thread overview]
Message-ID: <4C53695F.9040004@goop.org> (raw)
In-Reply-To: <583475.55555.qm@web113602.mail.gq1.yahoo.com>
On 07/30/2010 09:06 AM, Ruslan Nikolaev wrote:
> I have 2 kernels:
>
> 1. From Xen repositary pvops-git (2.6.31.13).
You want 2.6.32.16 from xen.git - the branch is xen/stable-2.6.32.x
J
> 2. From kernel.org: 2.6.32.16
>
> Thank you!
> Ruslan.
>
>
> --- On Thu, 7/29/10, Jeremy Fitzhardinge<jeremy@goop.org> wrote:
>
>> From: Jeremy Fitzhardinge<jeremy@goop.org>
>> Subject: Re: [Xen-devel] HVM hypercalls
>> To: "Ruslan Nikolaev"<nruslan_devel@yahoo.com>
>> Cc: xen-devel@lists.xensource.com
>> Date: Thursday, July 29, 2010, 11:47 PM
>> On 07/29/2010 11:55 AM, Ruslan
>> Nikolaev wrote:
>>> Thank you very much! I'll try this. BTW is it required
>> to do this for every module with HVM hypercalls or there is
>> some shared initialization code in HVM guest (Linux) similar
>> to one used in paravirtualized guests?
>>> If it's supposed to be in a module, is there any good
>> example I can look at?
>>> AFAIK hypercall_page is being initialized on Xen side
>> with appropriate vmcall/vmmcall code. Is this CPUID
>> mechanism a standard way to obtain hypercall_page reference
>> on HVM domain?
>>
>> What kernel are you working with? There's already
>> code to implement pv-on-hvm support for various recent pvops
>> kernels, so you can just base your work on those.
>>
>> J
>>
>>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-07-31 0:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 19:22 HVM hypercalls Ruslan Nikolaev
2010-07-29 1:05 ` Dan Magenheimer
2010-07-29 7:30 ` Juergen Gross
2010-07-29 18:55 ` Ruslan Nikolaev
2010-07-29 19:47 ` Jeremy Fitzhardinge
2010-07-30 16:06 ` Ruslan Nikolaev
2010-07-31 0:07 ` Jeremy Fitzhardinge [this message]
2010-08-03 19:48 ` Ruslan Nikolaev
2010-08-03 21:40 ` Jeremy Fitzhardinge
2010-08-04 17:41 ` Ruslan Nikolaev
2010-08-05 7:25 ` Christoph Egger
2010-08-05 10:31 ` Stefano Stabellini
2011-05-23 7:48 ` veeruyours
2011-05-23 8:22 ` Ian Campbell
2011-05-23 13:52 ` veerasena reddy
2011-05-24 12:06 ` Ian Campbell
2011-05-24 13:58 ` veeruyours
2011-05-24 14:09 ` Ian Campbell
2011-05-25 7:38 ` veeruyours
2011-05-25 8:13 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2010-08-06 21:58 Ruslan Nikolaev
2010-08-09 9:41 ` Stefano Stabellini
2010-08-03 20:30 Ruslan Nikolaev
2010-08-02 0:32 Ruslan Nikolaev
2008-08-19 14:38 HVM Hypercalls Kumar, Venkat
2008-08-19 14:53 ` Keir Fraser
2008-08-20 11:48 ` Kumar, Venkat
2008-08-20 12:11 ` Keir Fraser
2006-12-15 18:46 HVM hypercalls Ky Srinivasan
2006-12-15 19:54 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C53695F.9040004@goop.org \
--to=jeremy@goop.org \
--cc=nruslan_devel@yahoo.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.