All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Martin <furryfuttock@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Consuming PCI device in PV kernel
Date: Fri, 25 Jul 2014 13:56:38 +0100	[thread overview]
Message-ID: <357303711.20140725135638@gmail.com> (raw)
In-Reply-To: <1405940004.25022.10.camel@kazak.uk.xensource.com>

Hello Ian,

> IIRC from the guest PoV you just need to read the BAR values from the
> CFG space and then use them without worrying about where they point,
> i.e. by creating virtual address mappings of whatever MMIO address the
> BAR gives you.

I  thought that I was mapping the BAR memory correctly, however when I
fixed  a  bug in my software I started getting errors and I eventually
tracked it down to mapping the MMIO memory.

I     have     tried     calling    HYPERCALL_update_va_mapping    and
HYPERCALL_mmu_update  and  they both fail. HYPERCALL_update_va_mapping
gives me the following in xl dmesg:

(XEN) mm.c:1700:d292v0 Bad L1 flags 400000

Looking at the code I can't see where bit 22 is being set!

Reading  the qemu PCI mapping code, it seems to call xc_domctl. I have
traced   down   through  this  into  the xen source and it seems to do
many  things that I don't have access to via straight hypercalls.

Google doesn't seem to help much on this one either.

Any idea on how to proceed with this?

-- 
Best regards,
 Simon                            mailto:furryfuttock@gmail.com

  reply	other threads:[~2014-07-25 12:56 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
2014-07-21 10:53             ` Ian Campbell
2014-07-25 12:56               ` Simon Martin [this message]
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=357303711.20140725135638@gmail.com \
    --to=furryfuttock@gmail.com \
    --cc=Ian.Campbell@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.