From: Simon Martin <furryfuttock@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Consuming PCI device in PV kernel
Date: Mon, 21 Jul 2014 11:13:30 +0100 [thread overview]
Message-ID: <538610044.20140721111330@gmail.com> (raw)
In-Reply-To: <20140718190942.GG15947@laptop.dumpdata.com>
Hello Konrad,
Friday, July 18, 2014, 8:09:42 PM, you wrote:
>> I now have a working implementation of my own pcifront based on the
>> mini-os implementation, however I can't seem to find any examples or
>> documentation anywhere on how to discover and map the PCI device into
>> my PV memory map.
> Not sure what 'PV memory map' means? You mean the BAR values and such?
That's exactly what I mean. I assume that BAR entries must be written
pointing to an absolute memory area in dom0 which will then be mapped
into the PV as this provides the greatest flexibility. Is this
correct? Or do I just enable a memory area in the PV and map the BAR
to the buffers physical address?
Regards.
--
Best regards,
Simon mailto:furryfuttock@gmail.com
next prev parent reply other threads:[~2014-07-21 10:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 11:13 Consuming PCI device in PV kernel Simon Martin
2014-07-03 18:09 ` Konrad Rzeszutek Wilk
2014-07-07 8:21 ` Simon Martin
2014-07-07 11:22 ` Simon Martin
2014-07-07 12:21 ` Realtime access to PCI NIC Simon Martin
2014-07-08 14:46 ` Ian Campbell
2014-07-10 7:47 ` Simon Martin
2014-07-08 15:01 ` Consuming PCI device in PV kernel Konrad Rzeszutek Wilk
2014-07-10 7:54 ` Simon Martin
2014-07-11 16:47 ` Dario Faggioli
2014-07-15 8:37 ` Simon Martin
2014-07-15 14:56 ` Konrad Rzeszutek Wilk
2014-07-18 14:37 ` Simon Martin
2014-07-18 19:09 ` Konrad Rzeszutek Wilk
2014-07-21 10:13 ` Simon Martin [this message]
2014-07-21 10:53 ` Ian Campbell
2014-07-25 12:56 ` Simon Martin
2014-07-25 13:10 ` Ian Campbell
2014-07-25 13:21 ` Simon Martin
2014-07-25 13:37 ` Ian Campbell
2014-07-25 13:50 ` Andrew Cooper
2014-07-25 14:20 ` Simon Martin
2014-07-25 14:25 ` Andrew Cooper
2014-07-25 14:30 ` Simon Martin
2014-07-25 14:33 ` Ian Campbell
2014-07-25 14:36 ` Simon Martin
2014-07-25 14:28 ` Simon Martin
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=538610044.20140721111330@gmail.com \
--to=furryfuttock@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
/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).