[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] PCI MMIO?
- To: xen-users@xxxxxxxxxxxxxxxxxxx
- From: "Stephen Donnelly" <sfdonnelly@xxxxxxxxx>
- Date: Mon, 19 Mar 2007 11:04:44 +1300
- Delivery-date: Sun, 18 Mar 2007 15:03:46 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=JZNUEA30/KJS52URoqdHiplO1a6//E1shru98DuXmJiAKxSQtPh32eSmH1uqqcUt5umm1Vkdmjj+Uto7F1R1hCj1Dl0uymJ17t/mFxVT8IHH5CZpkS4DhiN3356voPhXHrLDCWYWqoeClmn3LKwik/KvsY8HJQ7WwTTnK4/7Z2w=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
On 3/16/07, Petersson, Mats <Mats.Petersson@xxxxxxx> wrote:
> I have a PCI device that has a 64kB mmio range at PCI_BAR_0. > This space contains the registers for the device. The Linux > driver provides a char device that allows read/write/seek, > and mmap for this space. In Linux you can use either
> read/write/seek to access the space, or memory map it via > mmap and access it directly. When using the driver in dom0 > under Xen 3.0.4, the read/write/seek method works fine but > the mmap does not. None of the related functions return
> errors, but the mmap does not appear to access the correct > memory. Is there anything I am missing?
It realy shouldn't make any difference. It's probably a question for Xen Devel tho'.
If you can access the device from kernel mode (have you tried that?) then you should be able to access it from user-mode, I would have thought.
The linux kernel is actually responsible for mapping the memory itself,
and aside from checking some permissions, there is no difference to the hypervisor whether a domain is DomU or Dom0.
Thanks for the advice Mats, I may try posting to the devel list.
Yes
access from the kernel does work, hence my confusion. It seems to be
only the memory mapping to user space that is not working, yet this
code works fine on non-xen kernels.
Stephen.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|