From: Tim Deegan <tim@xen.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Olaf Hering <olaf@aepfle.de>, xen-devel@lists.xensource.com
Subject: Re: [PATCH 0 of 2] v2: memshare/xenpaging/xen-access fixes for xen-unstable
Date: Fri, 16 Sep 2011 12:20:47 +0100 [thread overview]
Message-ID: <20110916112047.GA95880@ocelot.phlegethon.org> (raw)
In-Reply-To: <20081.53649.196648.92906@mariner.uk.xensource.com>
At 11:21 +0100 on 15 Sep (1316085665), Ian Jackson wrote:
> Tim Deegan writes ("Re: [Xen-devel] [PATCH 0 of 2] v2: memshare/xenpaging/xen-access fixes for xen-unstable"):
> > At 11:57 +0200 on 08 Sep (1315483028), Olaf Hering wrote:
> > > The following two patches allow the parallel use of memsharing,
> > > xenpaging and xen-access by using an independent ring buffer for
> > > each feature.
> > >
> > > Please review.
> >
> > As I said, the Xen side looks fine but I'd like the opinion of the tools
> > maintainers about the API changes before I apply anything. Maybe this
> > is something that can happen at the hackathon.
>
> >From the tools point of view:
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
>
> Tim, I wasn't sure if your message was an ack from the hypervisor
> point of view, so I haven't actually applied these patches.
OK, I've applied them now.
Cheers,
Tim.
prev parent reply other threads:[~2011-09-16 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 9:57 [PATCH 0 of 2] v2: memshare/xenpaging/xen-access fixes for xen-unstable Olaf Hering
2011-09-08 9:57 ` [PATCH 1 of 2] mem_event: pass mem_event_domain pointer to mem_event functions Olaf Hering
2011-09-08 9:57 ` [PATCH 2 of 2] mem_event: use different ringbuffers for share, paging and access Olaf Hering
2011-09-12 13:57 ` [PATCH 0 of 2] v2: memshare/xenpaging/xen-access fixes for xen-unstable Tim Deegan
2011-09-15 10:21 ` Ian Jackson
2011-09-16 11:20 ` Tim Deegan [this message]
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=20110916112047.GA95880@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Ian.Jackson@eu.citrix.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).