WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] HVM hypercalls

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] HVM hypercalls
From: Ruslan Nikolaev <nruslan_devel@xxxxxxxxx>
Date: Sun, 1 Aug 2010 17:32:17 -0700 (PDT)
Delivery-date: Sun, 01 Aug 2010 17:33:01 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1280709137; bh=DizI8HuE+DzkIs8k+90W0G/M66fTJwSPwsO16Ky+9+w=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ShsdrLGLD/8YN7/vh57wYKz/9VMFprW0KfSJMWdimVaCDomeYnCVsKFbJFrcLV1c7+z9qO9oNsBEt5plULXM/ZC3XKXmL2gBjI8Uf/VlCbQNKQ9Vxb7oL0JaWOO0VA18TKt11/VkeWnUxyTo2PKBBIZDoUcfgFfHy1bJfRiZe8U=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=eGIgZy1g9VqzuxnVfnrHQyLX/zhbxuV8HwPF8KDPMkfXGwhti6WzUnqR+Oh9KTE749XU2SBy88H6unQEUTepIT9GPV79fUlsxbm/+3KVrzj9EbeTRFdofZR3rXoURMBpsbOIJiXpcV/YAD3htD6BY/hc00FpyhftpaZpTeeRF2o=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanks!


> --- On Sat, 7/31/10, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
> wrote:
> 
> > From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
> > Subject: Re: [Xen-devel] HVM hypercalls
> > To: "Ruslan Nikolaev" <nruslan_devel@xxxxxxxxx>
> > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> > Date: Saturday, July 31, 2010, 4:07 AM
> >   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@xxxxxxxx> 
> > wrote:
> > >
> > >> From: Jeremy Fitzhardinge<jeremy@xxxxxxxx>
> > >> Subject: Re: [Xen-devel] HVM hypercalls
> > >> To: "Ruslan Nikolaev"<nruslan_devel@xxxxxxxxx>
> > >> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> > >> 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@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
> > >
> > 
> > 
> 
> 
> 
> 




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>