From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gorm Hansen Subject: Re: To use xcs or not? Date: Sun, 20 Feb 2005 22:42:09 -0800 Message-ID: <421982C1.7000403@diku.dk> References: <42184ECD.1080904@diku.dk> <4218C302.2070900@codemonkey.ws> <421951AE.2030805@diku.dk> <42196BC8.7000008@codemonkey.ws> <42197E79.6030504@diku.dk> <42198034.7020008@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <42198034.7020008@codemonkey.ws> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Anthony Liguori Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Anthony Liguori wrote: > Jacob Gorm Hansen wrote: > >> Hmm from looking at the code in drivers/xen/evtchn/evtchn.c, it seems >> if I write to this device, I can unmask local event channels, but >> there is no notion of a target domain. > > > Port's come in pairs. 117 is the remote port number. Typically, in > dom0 you would allocate the port pair (0, 117). The 0 tells xc to > allocate an unused local port that's connected to the remote port. > > Local ports are always unique so there's no need to be domain specific. I see. But that means there is no way to _send_ notifications from /dev/xen/evtchn? All I can do there is read incoming events? Jacob ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click