From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Kashmira. K." <chimnee@yahoo.com>
Cc: winterfi@cisco.com, xen-devel@lists.xensource.com
Subject: Re: Contiguous DMAble memory in Dom0 user space linux process
Date: Fri, 15 Jan 2010 11:59:17 -0500 [thread overview]
Message-ID: <20100115165917.GC11986@phenom.dumpdata.com> (raw)
In-Reply-To: <494534.34716.qm@web50606.mail.re2.yahoo.com>
> Actually I'm not trying to communicate with a driver. The user space application is kind of a driver that lives outside of the kernel and communicates with the device directly.
OK, but isn't the hardware visible via the PCI bus? Does it have any
PCI BARs defined?
> On a linux system (non xen) the bigphysarea patch was used to get large contiguous DMA memory in user space.
> I am trying to do the equivalant on Xen capable linux in Dom0 so the same application will work. Kind of port it from 'linux' to 'Xen capable linux'.
Oh boy. I think you have two options:
1) Play with stubdomains. They are based on Mini-OS and
allow you to create applications + MiniOS (that runs under Xen).
An example of this is the QEMU stubdomain.
You can modify your MiniOS to get you virtual addresses that are
mapped directly to contingous memory areas.
2). Look at fbmem.c and write a device driver that allows the userspace
application to mmap the driver (similar to fb_mem), which in turn sets
up a vmalloc-ed area that is physically contigous (by using the
xen_create_contiguous_region function to exchange PFNs).
next prev parent reply other threads:[~2010-01-15 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 21:03 Contiguous DMAble memory in Dom0 user space linux process Kashmira. K.
2010-01-13 21:31 ` Konrad Rzeszutek Wilk
2010-01-15 2:16 ` Kashmira. K.
2010-01-15 16:59 ` Konrad Rzeszutek Wilk [this message]
2010-01-20 21:10 ` Kashmira. K.
2010-01-20 21:42 ` Konrad Rzeszutek Wilk
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=20100115165917.GC11986@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=chimnee@yahoo.com \
--cc=winterfi@cisco.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).