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

[Xen-devel] Device driver domains

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Device driver domains
From: "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
Date: Tue, 13 Dec 2005 14:37:32 -0800
Delivery-date: Tue, 13 Dec 2005 22:39:11 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcYANc5ousFgGvzuQwOYGgDQcighjQ==
Thread-topic: Device driver domains
  Hi,

  I am interested in running device drivers on dedicated drivers domains
(non dom0).

  My understanding is that this was possible in 2.0 but it is still not
available in 3.0
 
  I tried running Xen 2.0.7 to see if I could create a driver domain,
but that was not successful. If I set CONFIG_XEN_PHYSDEV_ACCESS for
domU, the domain dies very early in the boot process. Nothing gets
printed in the domU console after the " ** REMOTE CONSOLE: CTRL-] TO
QUIT **" message. And Xen prints the following messages:

(XEN) (file=extable.c, line=71) Pre-exception: fc52d69d -> fc52d724
(XEN) (file=traps.c, line=464) Page fault: fc52d739 -> fc505a60

I was wondering if  anyone used driver domains successfully in 2.0.7?
Could device access in domU be broken in 2.0.7 ?
What was the latest version of Xen for which someone have reported
device drivers were used successfully?

In fact, I am interested in having this functionality in Xen 3.0. Can
someone explain why the code that existed in 2.0 is not available in
3.0? I would like to understand what are the issues and how hard would
be to have this functionality available in Xen 3.0. I would appreciate
any comment or explanation

Thanks

Renato 

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Device driver domains, Santos, Jose Renato G <=