All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sting Zax <zstingx@gmail.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: frontend and backend devices and different types of hw - pci for example
Date: Mon, 29 Aug 2005 02:57:07 -0400	[thread overview]
Message-ID: <3a0f1c62050828235727cd55fa@mail.gmail.com> (raw)
In-Reply-To: <200508281625.09980.mark.williamson@cl.cam.ac.uk>

Hello, 

 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 ?


>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 ? 


Regards,
Sting

On 8/28/05, Mark Williamson <mark.williamson@cl.cam.ac.uk> 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
>

  reply	other threads:[~2005-08-29  6:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-28  7:28 frontend and backend devices and different types of hw - pci for example Sting Zax
2005-08-28 15:25 ` Mark Williamson
2005-08-29  6:57   ` Sting Zax [this message]
2005-08-29  8:59     ` Keir Fraser
2005-08-29 10:45     ` Mark Williamson
2005-08-29 19:48       ` Stefan Berger
2005-09-03 17:46         ` Mark Williamson
2005-09-03 18:42           ` Stefan Berger
2005-09-04  3:23             ` Mark Williamson
2005-09-04 13:35               ` David Hopwood
2005-09-06 21:59               ` Stefan Berger

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=3a0f1c62050828235727cd55fa@mail.gmail.com \
    --to=zstingx@gmail.com \
    --cc=mark.williamson@cl.cam.ac.uk \
    --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.