From: Tim Deegan <tim@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "olaf@aepfle.de" <olaf@aepfle.de>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"andres@gridcentric.ca" <andres@gridcentric.ca>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"keir.xen@gmail.com" <keir.xen@gmail.com>,
"andres@lagarcavilla.org" <andres@lagarcavilla.org>,
"adin@gridcentric.ca" <adin@gridcentric.ca>
Subject: Re: [PATCH 3 of 7] Use a reserved pfn in the guest address space to store mem event rings
Date: Thu, 1 Mar 2012 15:17:33 +0000 [thread overview]
Message-ID: <20120301151733.GA48103@ocelot.phlegethon.org> (raw)
In-Reply-To: <1330588073.10008.113.camel@dagon.hellion.org.uk>
At 07:47 +0000 on 01 Mar (1330588073), Ian Campbell wrote:
> > > Is there no scope for making these pages owned by the domain but not
> > > actually part of the P2M? We can cope with that for other types of magic
> > > page, can't we?
It would need a new operation to map the ring into the tool that uses
it; normal map-foreign-page ops need a GFN.
But that sounds like a good idea all the same.
Tim.
next prev parent reply other threads:[~2012-03-01 15:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 6:05 [PATCH 0 of 7] Mem event ring setup interface update Andres Lagar-Cavilla
2012-02-23 6:05 ` [PATCH 1 of 7] Tools: Sanitize mem_event/access/paging interfaces Andres Lagar-Cavilla
2012-02-23 14:29 ` Olaf Hering
2012-02-28 12:56 ` Ian Campbell
2012-02-28 15:14 ` Andres Lagar-Cavilla
2012-02-23 6:05 ` [PATCH 2 of 7] x86/hvm: refactor calls to prepare and tear down a helper ring Andres Lagar-Cavilla
2012-02-23 6:05 ` [PATCH 3 of 7] Use a reserved pfn in the guest address space to store mem event rings Andres Lagar-Cavilla
2012-02-28 13:01 ` Ian Campbell
2012-02-28 15:19 ` Andres Lagar-Cavilla
2012-03-01 7:47 ` Ian Campbell
2012-03-01 15:17 ` Tim Deegan [this message]
2012-03-01 16:26 ` Andres Lagar-Cavilla
2012-03-01 16:30 ` Andres Lagar-Cavilla
2012-03-01 17:32 ` Tim Deegan
2012-03-01 17:44 ` Andres Lagar-Cavilla
2012-03-01 17:52 ` [PATCH 3 of 7] Use a reserved pfn in the guest address space to store mem event ringsg Tim Deegan
2012-03-06 19:27 ` Andres Lagar-Cavilla
2012-03-01 2:29 ` [PATCH 3 of 7] Use a reserved pfn in the guest address space to store mem event rings Andres Lagar-Cavilla
2012-02-23 6:05 ` [PATCH 4 of 7] x86/mm: wire up sharing ring Andres Lagar-Cavilla
2012-02-23 6:05 ` [PATCH 5 of 7] Tools: libxc side for setting up the mem " Andres Lagar-Cavilla
2012-02-28 13:02 ` Ian Campbell
2012-02-23 6:05 ` [PATCH 6 of 7] x86/mm: Clean up mem event structures on domain destruction Andres Lagar-Cavilla
2012-02-23 14:32 ` Olaf Hering
2012-02-23 6:05 ` [PATCH 7 of 7] x86/mm: Fix mem event error message typos Andres Lagar-Cavilla
2012-02-23 16:07 ` [PATCH 0 of 7] Mem event ring setup interface update Tim Deegan
2012-02-27 22:43 ` Andres Lagar-Cavilla
-- strict thread matches above, loose matches on Subject: below --
2012-03-01 2:43 [PATCH 0 of 7] Mem event ring interface setup update, V2 Andres Lagar-Cavilla
2012-03-01 2:43 ` [PATCH 3 of 7] Use a reserved pfn in the guest address space to store mem event rings Andres Lagar-Cavilla
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=20120301151733.GA48103@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=adin@gridcentric.ca \
--cc=andres@gridcentric.ca \
--cc=andres@lagarcavilla.org \
--cc=keir.xen@gmail.com \
--cc=olaf@aepfle.de \
--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).