From: Arun Sharma <arun.sharma@intel.com>
To: Mike Wray <mike.wray@hp.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: VMX device models not getting created anymore?
Date: Thu, 16 Jun 2005 10:35:41 -0700 [thread overview]
Message-ID: <42B1B86D.6090503@intel.com> (raw)
In-Reply-To: <42B13EC8.3090008@hp.com>
Mike Wray wrote:
>> I sent a patch: vmx-device-models-py.patch to the list to do just
>> this, but the event channel numbers seem to be off by one for some
>> reason (please see comments inside the patch).
>
>
> OK, I see the patch. What makes you think the event channel port
> numbers are off? Is it possible that it should be using port2 instead
> of port1?
If I print self.device_channel.port1 and compare it to the output of
# xm list --long
It's off by one and device models don't get any events from the VMX domain.
When I add the -1, things work ok i.e. device models do receive events
from the VMX domain.
port1 = dom0 end of the event channel. That's what the device models
listen to. port2 = hypervisor/vmx domain end of the event channel.
-Arun
next prev parent reply other threads:[~2005-06-16 17:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 21:48 VMX device models not getting created anymore? Ian Pratt
2005-06-15 14:30 ` Mike Wray
2005-06-15 17:09 ` Arun Sharma
2005-06-16 8:56 ` Mike Wray
2005-06-16 17:35 ` Arun Sharma [this message]
2005-06-17 13:07 ` Mike Wray
2005-06-17 19:28 ` Arun Sharma
2005-06-17 20:17 ` Arun Sharma
2005-06-17 21:54 ` cannot concatenate 'str' and 'Nonetype' object with creating domain Jurgen Stroo
2005-06-17 22:16 ` Jurgen Stroo
2005-06-20 11:13 ` VMX device models not getting created anymore? Mike Wray
2005-06-21 21:01 ` Arun Sharma
2005-06-22 8:34 ` Mike Wray
2005-06-20 10:52 ` Mike Wray
-- strict thread matches above, loose matches on Subject: below --
2005-06-15 17:12 Ian Pratt
2005-06-15 18:02 ` Arun Sharma
2005-06-10 21:22 Arun Sharma
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=42B1B86D.6090503@intel.com \
--to=arun.sharma@intel.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=mike.wray@hp.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.