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] frontend and backend devices and different types of hw -

To: Sting Zax <zstingx@xxxxxxxxx>
Subject: Re: [Xen-devel] frontend and backend devices and different types of hw - pci for example
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Mon, 29 Aug 2005 11:45:51 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 29 Aug 2005 10:46:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <3a0f1c62050828235727cd55fa@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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <3a0f1c6205082800287beb089@xxxxxxxxxxxxxx> <200508281625.09980.mark.williamson@xxxxxxxxxxxx> <3a0f1c62050828235727cd55fa@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
>  I had looked at the code of 2.0.*  under xen/arch/x86 saw
> pci-irq.c and pci-pc.c and pci-x86.c which as I understand handle pci
> devices other than net/usb.
> However, I did not saw such modules in the unstable version.
> May I ask : is this PCI support for non net/usb PCI devices  removed
> (or temporarily removed) from the unstable version? or maybe I simply
> missed it ?

Dom0 now basically owns anything to do with PCI whereas previously Xen 
controlled core PCI stuff and dom0 just accessed devices.  Support for giving 
device access to other domains will need to be implemented in dom0 (this 
hasn't been done yet but it's hoped the feature will be back in time for the 
release).

> >Note that giving direct physical access to a PCI device has security
> >implications since the guest can potentially use the cards' DMA
> > capabilities to access all of physical memory.
>
> Will IOMMU support help solving this security problems ?

Yes but only if it enforces access permissions fully i.e. I don't think the 
IOEMU in AMD64 machines is sufficient.  From the looks of Pacifica it might 
have sufficient support to control the DMA problem, I'm sure Intel have a 
similar solution (although I don't think it's implemented in Vanderpool - 
they'll probably need chipset support).

Cheers,
Mark

>
> Regards,
> Sting
>
> On 8/28/05, Mark Williamson <mark.williamson@xxxxxxxxxxxx> wrote:
> > > What about other devices ? let's say a PCI sound card (or any other PCI
> > > device). Where is the software that should handle it ? I remember I saw
> > > somewhere some discussion about PCI configuration space, but I don't
> > > remember where.
> >
> > That code is in Xen itself in Xen 2.0.  Xen controls access to the PCI
> > configuration spaces so that guests can only see the devices they have
> > access to.  It also controls the IO memory / ports that domains are
> > allowed to access in order to control PCI devices.
> >
> > Note that giving direct physical access to a PCI device has security
> > implications since the guest can potentially use the cards' DMA
> > capabilities to access all of physical memory.  The front/back-style
> > devices do not have this limitation.
> >
> > Btw, I've laid some groundwork for a virtual sound device but haven't had
> > much time to hack on it yet.
> >
> > Cheers,
> > Mark

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