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] Sched_op hypercall small questions

To: Jan Beulich <JBeulich@xxxxxxxx>
Subject: Re: [Xen-devel] Sched_op hypercall small questions
From: Daniel Castro <evil.dani@xxxxxxxxx>
Date: Tue, 20 Sep 2011 21:35:22 +0900
Cc: keir.xen@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Sep 2011 05:40:56 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=d3XSMhM2CxHKFcjH56w90PlMXdas47+/UeoXK/bENrw=; b=HX3E73w2gG2+l4xIBGaKfckGgH+hcxzR3R9yK+8FBakHeJ/5j+iQFR0NB4Q6uhftFR mLWDPKzSX+W3wv2WqUFtYcE+67UEjug/P2brTtxC+d+ChLwkGYJ1SQZLOJ4vOvC4ZXzI qBNZm6ma+Hi3nwaYEX+RzxsAtedeThsddI86Q=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E789BB40200007800056C5A@xxxxxxxxxxxxxxxxxxxx>
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: <4E784FD502000078000769C5@xxxxxxxxxxxxxxxxxxxx> <CAP2B85_YdLJDaNoaimuDOJhQJ_1ogtDWYhUbg-Ycxd0R0dmd8A@xxxxxxxxxxxxxx> <4E7874180200007800056BF2@xxxxxxxxxxxxxxxxxxxx> <CAP2B85-ZUYdbkyEQHkM65gwKO4g-xV=k3O30FByw9DhA7vwmWg@xxxxxxxxxxxxxx> <4E789BB40200007800056C5A@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Sep 20, 2011 at 8:57 PM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>> On 20.09.11 at 12:55, Daniel Castro <evil.dani@xxxxxxxxx> wrote:
>> What I am trying is writing to the xenstore ring, issue the send
>> hypercall, then wait (poll hypercall) for event, then read answer from
>> ring.
>
> That reads as if you do all this from the same thread in the same domain.
> Which might be your problem, particularly if additionally you use the
> same event channel for signaling production and consumption.

Yes you are correct, I have all in the same thread. But I have no
other choice, since this is run inside hvmloader when the BIOS is
being deployed.

>> The waiting is not working, but If I wait enough time, the ring will
>> contain the answer, but apparently I have a problem with my event
>> channel port. So to test this theory I am using event channel status
>> hypercall, and I get:
>> Status 2 (meaning interdomain connected)
>> VCPU 0
>> The Union reports dom 32752 and port 2.
>
> 32752 == DOMID_SELF. And I can't see where the hypercall
> implementation would return DOMID_SELF here.
Sorry I had a coding error, but it is corrected (I did not call the
union correctly, so I ended up calling dom in the main struct).
Anyway here is the output corrected:
Xenbus rings @0xfeffc000, event channel 2
Event Chn 2 Status 2 VCPU 0.
Event is interdomain (2) union dom 983040 union port 42

Thanks,

Daniel

>
>> Right now, there are two things that jump to my mind, first when I
>> issue the poll hypercall the system continues execution, instead of
>> yielding CPU unitl event arrives. If it were never to arrive it should
>> yield infinitely, right?
>
> Without a timeout, yes.
>
>> Second, the bit is never set. Or it is being undone before I can check it.
>
> That would need to be you to undo it.
>
> Jan
>
>



-- 
+-=====---------------------------+
| +---------------------------------+ | This space intentionally blank
for notetaking.
| |   | Daniel Castro,                |
| |   | Consultant/Programmer.|
| |   | U Andes                         |
+-------------------------------------+

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