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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-devel] Shared memory and event channel

from [Ian Campbell] [Permanent Link][Original]
To: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Subject: Re: [Xen-devel] Shared memory and event channel
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Wed, 24 Feb 2010 09:38:33 +0000
Cc: Daniel, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "djmagee@xxxxxxxxxxxx" <djmagee@xxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Stodden <Daniel.Stodden@xxxxxxxxxx>
Delivery-date: Wed, 24 Feb 2010 01:41:07 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <29b32d341002231126h703334b2u5af6ab9b2bbf00fc@xxxxxxxxxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <29b32d341002211058l7e283336pa4fdfd0dc0b7124b@xxxxxxxxxxxxxx> <1266825344.4996.183.camel@xxxxxxxxxxxxxxxxxxx> <29b32d341002220936q2f6f3cdaif3cbb766d1e644d1@xxxxxxxxxxxxxx> <1266874463.27288.57.camel@xxxxxxxxxxxxxxxxxxxxxxx> <29b32d341002221416t4e00b899q18e07a69ad24b07f@xxxxxxxxxxxxxx> <1266917906.11737.5928.camel@xxxxxxxxxxxxxxxxxxxxxx> <20100223144738.GC25741@xxxxxxxxxxxxxxxxxxx> <1266939735.11737.6397.camel@xxxxxxxxxxxxxxxxxxxxxx> <29b32d341002230753r2a1a028dpf276f68b0cca48a@xxxxxxxxxxxxxx> <EECC125FCE18E740AF561189E126028502AA24@xxxxxxxxxxxxxxxxxxxxxxx> <29b32d341002231126h703334b2u5af6ab9b2bbf00fc@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
On Tue, 2010-02-23 at 19:26 +0000, Ritu kaur wrote:

> Need a clarification, using pci passthrough I believe it remove access
> to device from dom0 and attaches the device to a domU and from then on
> can only be accessed via that domU or is it possible to have dom0 and
> a single domU gain access to device using pci passthrough? I guess
> not, thought of checking.

You are correct, a given hardware device is only directly accessible to
a single domain at a time, be that dom0 or a domU via PCI passthrough.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-devel] live migration fails (assert in shadow_hash_delete), Ashish Bijlani
Next by Date:  [Xen-devel] [PATCH] xen I/O ring interface: provide a variant of __RING_SIZE() that is an integer constant expression, Jan Beulich
Previous by Thread:  Re: [Xen-devel] Shared memory and event channel, Ritu kaur
Next by Thread:  [Xen-devel] [PATCH] Fix blktap2 test in xen-hotplug-cleanup, Jim Fehlig
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy