[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] How did Xen handle PCI config space access for VT-d device?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
From: "Neo Jia" <neojia@xxxxxxxxx>
Date: Mon, 23 Jun 2008 00:53:55 -0700
Delivery-date: Mon, 23 Jun 2008 00:54:19 -0700
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=XK5IGf/9pizwYhlCH4nNk5d9xp/UtI/wdXmtxOTkq1FW36r9wSJSSjnIrXlspoX1p2 3oSLEOYVIwEqC6KN8H/UjETei+MoZyzaSLhYXfIu/dda9zWvYMHPCt8eSU7K9UrYAZyT LNdRLEP2Nhtj7JJHgepB8gtP77Amvuo1XGF5g=
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

hi,

I am curious about how Xen handle PCI config space access of VT-d
device. Could you point me to the code?

Thanks,
Neo

-- 
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!

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

Follow-Ups:
- RE: [Xen-devel] How did Xen handle PCI config space access for VT-ddevice?
  - From: Han, Weidong

Prev by Date: [Xen-devel] VMX status report. Xen: #17884 & Xen0: #577 -- no new issue
Next by Date: [Xen-devel] Xen and AMD: VMExit on int 0x80 and 64bit case.
Previous by thread: [Xen-devel] VMX status report. Xen: #17884 & Xen0: #577 -- no new issue
Next by thread: RE: [Xen-devel] How did Xen handle PCI config space access for VT-ddevice?
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.