From: Wei Liu <wei.liu2@citrix.com>
To: Hongyang Yang <yanghy@cn.fujitsu.com>
Cc: Shriram Rajagopalan <rshriram@cs.ubc.ca>,
wei.liu2@citrix.com, Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: remus suspend event channel in pvops kernel
Date: Thu, 21 Aug 2014 12:23:40 +0100 [thread overview]
Message-ID: <20140821112340.GC10356@zion.uk.xensource.com> (raw)
In-Reply-To: <53F5A8A7.40404@cn.fujitsu.com>
On Thu, Aug 21, 2014 at 04:07:03PM +0800, Hongyang Yang wrote:
> Hi Ian,
>
> I remember Shriram has implemented it few years ago. It's
> already in upstream Xen.
>
> refer to:
> http://wiki.xen.org/wiki/Remus_PV_domU_requirements
>
FYI Ian was talking about upstream Linux kernel, not upstream Xen.
And I think that wiki page concurs with what Ian said -- it's not yet in
upstream Linux kernel.
Wei.
next prev parent reply other threads:[~2014-08-21 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 16:29 remus suspend event channel in pvops kernel Ian Campbell
2014-08-21 8:07 ` Hongyang Yang
2014-08-21 11:23 ` Wei Liu [this message]
2014-08-21 17:20 ` Ian Campbell
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=20140821112340.GC10356@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=rshriram@cs.ubc.ca \
--cc=xen-devel@lists.xen.org \
--cc=yanghy@cn.fujitsu.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).