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/
Home Products Support Community News


RE: [Xen-devel] VCPU Structure

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: RE: [Xen-devel] VCPU Structure
From: "Nimgaonkar, Satyajeet" <SatyajeetNimgaonkar@xxxxxxxxxx>
Date: Wed, 10 Nov 2010 18:24:29 +0000
Accept-language: en-US
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 10 Nov 2010 10:58:23 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19673.37162.523893.709556@xxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <12871952FC0E29439F861FA745BCDD8503EC90AA@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <3d762ccd-644e-4a38-9620-7209e972e7bd@default> <12871952FC0E29439F861FA745BCDD8503EC98CB@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <<fa86f3a6-2433-4595-b249-a10711cb44da@default> <12871952FC0E29439F861FA745BCDD8503EC99C4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <42a3804d-5b4c-4920-a52f-2f5394ef585b@default> <12871952FC0E29439F861FA745BCDD8503EC9D52@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <6665015d-037b-485a-9b5f-8e5f64a921c1@default>, <19673.37162.523893.709556@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-topic: [Xen-devel] VCPU Structure
    I accept that I may have been unclear and not specific with my requests, 
but I am currently working on a complex research project and so it makes it 
difficult to understand all its aspects in entirety. I apologize for it and 
also appreciate your patience and assistance.
    Now I precisely know what exactly I want to achieve and I would appreciate 
if I get some help on it.
I have implemented a custom hypercall in xen. Now i need to get hold off the 
memory that is being assigned to the process (i.e. the function that is calling 
the hypercall). I intend to do this from the hypercall handler. Once I have 
this memory info, I will compute the hash of it and store it in the VCPU 
structure. Any sample code or examples on this would help a lot.
    I hope this makes sense. Thanks a lot for the constant help.

From: Ian Jackson [Ian.Jackson@xxxxxxxxxxxxx]
Sent: Tuesday, November 09, 2010 12:21 PM
To: Dan Magenheimer
Cc: Nimgaonkar, Satyajeet; Xen Devel
Subject: RE: [Xen-devel] VCPU Structure

Dan Magenheimer writes ("RE: [Xen-devel] VCPU Structure"):
> I'm still not quite sure I understand, though your description is
> getting better.

Are you sure that your patience with this enquirer is really a virtue
in this context ?

xen-devel is not a list that should be used for people who need help
with their homework.


Xen-devel mailing list

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