From: Keir Fraser <keir.xen@gmail.com>
To: Olaf Hering <olaf@aepfle.de>,
Andres Lagar-Cavilla <andres@lagarcavilla.org>
Cc: andres@gridcentric.ca, xen-devel@lists.xensource.com,
Tim Deegan <tim@xen.org>,
ian.campbell@citrix.com, adin@gridcentric.ca
Subject: Re: [PATCH 0 of 3] Update paging/sharing/access interfaces v2
Date: Fri, 10 Feb 2012 12:04:23 -0800 [thread overview]
Message-ID: <CB5AB847.2AF41%keir.xen@gmail.com> (raw)
In-Reply-To: <20120210194517.GA23684@aepfle.de>
On 10/02/2012 11:45, "Olaf Hering" <olaf@aepfle.de> wrote:
>> Actually, this hiatus allows me to float a perhaps cleaner way to map the
>> ring: the known problem is that the pager may die abruptly, and Xen is
>> still posting events to a page now belonging to some other dom0 process.
>> This is dealt with in the qemu-dm case by stuffing the ring in an unused
>> pfn (presumably somewhere in the mmio hole?)
>>
>> Would that work? Is there a policy for parceling out these "magic pfn's"?
>
> I was just thinking about this issue. The bug is that the ring lives in
> dom0, the page should belong to domU and should be destroyed along with
> it. And ring users in dom0 should request (and maybe initially allocate
> and setup) a certain gfn belonging to domU.
Yes indeed. The gpfn could be allocated by the domain builder, or by
hvmloader (which might be too late!).
-- Keir
next prev parent reply other threads:[~2012-02-10 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 6:08 [PATCH 0 of 3] Update paging/sharing/access interfaces v2 Andres Lagar-Cavilla
2012-02-09 6:08 ` [PATCH 1 of 3] Use memops for mem paging, sharing, and access, instead of domctls Andres Lagar-Cavilla
2012-02-09 17:21 ` Ian Jackson
2012-02-09 20:33 ` Andres Lagar-Cavilla
2012-02-09 6:08 ` [PATCH 2 of 3] x86/mm: New sharing audit memop Andres Lagar-Cavilla
2012-02-09 17:04 ` Ian Jackson
2012-02-09 6:08 ` [PATCH 3 of 3] Tools: Sanitize mem_event/access/paging interfaces Andres Lagar-Cavilla
2012-02-10 16:13 ` [PATCH 0 of 3] Update paging/sharing/access interfaces v2 Tim Deegan
2012-02-10 18:13 ` Andres Lagar-Cavilla
2012-02-10 19:45 ` Olaf Hering
2012-02-10 20:04 ` Keir Fraser [this message]
2012-02-10 20:11 ` Andres Lagar-Cavilla
2012-02-10 20:29 ` Keir Fraser
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=CB5AB847.2AF41%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=adin@gridcentric.ca \
--cc=andres@gridcentric.ca \
--cc=andres@lagarcavilla.org \
--cc=ian.campbell@citrix.com \
--cc=olaf@aepfle.de \
--cc=tim@xen.org \
--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).