From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Simon Martin <furryfuttock@gmail.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Consuming PCI device in PV kernel
Date: Fri, 25 Jul 2014 15:25:35 +0100 [thread overview]
Message-ID: <53D268DF.6010906@citrix.com> (raw)
In-Reply-To: <13170235.20140725152048@gmail.com>
On 25/07/14 15:20, Simon Martin wrote:
> Hello Andrew,
>
>>>>>> Looking at the code I can't see where bit 22 is being set!
>>>>> Without seeing you code I've no idea about this (even if I could see it,
>>>>> I dunno...)
>>>> Bit 22 is being set in Xen code.
>>> Hopefully someone who knows the x86 PV stuff can chime in then, I looked
>>> but can't see what this represents.
>> I suspect this would be:
>> /* Bit 22 of a 24-bit flag mask. This corresponds to bit 62 of a pte.*/
>> #define _PAGE_GNTTAB (1U<<22)
>> from include/asm-x86/x86_64/page.h
>> So you are attempting to update a pte which already has a granted page
>> in it.
> That's weird as I have only one domU running, so nothing else could
> have claimed the PCI memory area. The PCI has been passed through as I
> see the mapping in xenstore.
>
> Should I be using a different hypercall to gain access to this memory
> area?
>
>
Once you grant map a page from another domain, your domain no longer
owns the PTE. You should either avoid that PTE, or grant unmap the
foreign frame first.
This indicates that you have memory management issues/corruption in
whichever domain is receiving the update_va errors.
~Andrew
next prev parent reply other threads:[~2014-07-25 14:25 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
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 [this message]
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=53D268DF.6010906@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=furryfuttock@gmail.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).