From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wei Liu <liuw@liuw.name>
Subject: Re: FIFO-based event channel ABI design (draft B)
Date: Mon, 18 Feb 2013 20:50:20 +0000
Message-ID: <CAOsiSVW4jA9JQkX5vXPA5rBSX7WUTL4seLF4J9hDnFFUFfD_nw@mail.gmail.com>
References: <511E46FD.3010605@citrix.com>
	<1361200766.1051.5.camel@zakaz.uk.xensource.com>
	<51228C27.7050000@citrix.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7486848675757517416=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <51228C27.7050000@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: David Vrabel <david.vrabel@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Wei Liu <wei.liu2@citrix.com>, Ian Campbell <Ian.Campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

--===============7486848675757517416==
Content-Type: multipart/alternative; boundary=089e01493ee4597d1204d605e12a

--089e01493ee4597d1204d605e12a
Content-Type: text/plain; charset=UTF-8

On Mon, Feb 18, 2013 at 8:16 PM, David Vrabel <david.vrabel@citrix.com>wrote:

> On 18/02/13 15:19, Ian Campbell wrote:
> > On Fri, 2013-02-15 at 14:32 +0000, David Vrabel wrote:
> >> Except for a lack of information of the required memory barriers (to be
> >> included in draft C), this should now be completely enough to start on a
> >> prototype (any volunteers? ;).
> >
> > I think the real question is whether you as creator of the design are
> > going to be working on the implementation. That would the usual
> > progression of things.
>
> Yes, but I can't work on it full-time.
>
>
I would really like to help, but I'm mainly occupied by Xen network
improvement
at the moment. I will be happy to join the discussion on the new design and
share my humble two cents.

One thing I do think about is the registration interface. The naming for now
mainly focuses on N-level event channel, but there might be other models in
the
future, so I will rename it to EVTCHNOP_register_extended_event_channel and
make registering each model a subcommand of that interface. Modifications to
toolstack will also need adjustment. AFAICT the FIFO-design will be enabled
for
all guests while the 3-level design only aims for Dom0 and driver domains.
Anyway, let's discuss this later, after I post my new series.


Wei.


 David
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

--089e01493ee4597d1204d605e12a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Feb 18, 2013 at 8:16 PM, David Vrabel <span dir=3D=
"ltr">&lt;<a href=3D"mailto:david.vrabel@citrix.com" target=3D"_blank">davi=
d.vrabel@citrix.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><di=
v class=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"im">On 18/02/13 15:19, Ian Campbell wrote:<b=
r>


&gt; On Fri, 2013-02-15 at 14:32 +0000, David Vrabel wrote:<br>
&gt;&gt; Except for a lack of information of the required memory barriers (=
to be<br>
&gt;&gt; included in draft C), this should now be completely enough to star=
t on a<br>
&gt;&gt; prototype (any volunteers? ;).<br>
&gt;<br>
&gt; I think the real question is whether you as creator of the design are<=
br>
&gt; going to be working on the implementation. That would the usual<br>
&gt; progression of things.<br>
<br>
</div>Yes, but I can&#39;t work on it full-time.<br>
<span class=3D""><font color=3D"#888888"><br></font></span></blockquote><di=
v><br></div><div style></div><div class=3D"gmail_quote"><div class=3D"gmail=
_quote">I would really like to help, but I&#39;m mainly occupied by Xen net=
work improvement</div>

<div class=3D"gmail_quote">at the moment. I will be happy to join the discu=
ssion on the new design and</div><div class=3D"gmail_quote">share my humble=
 two cents.</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_q=
uote">

One thing I do think about is the registration interface. The naming for no=
w</div><div class=3D"gmail_quote">mainly focuses on N-level event channel, =
but there might be other models in the</div><div class=3D"gmail_quote">futu=
re, so I will rename it to EVTCHNOP_register_extended_event_channel and</di=
v>

<div class=3D"gmail_quote">make registering each model a subcommand of that=
 interface. Modifications to</div><div class=3D"gmail_quote">toolstack will=
 also need adjustment. AFAICT the FIFO-design will be enabled for</div><div=
 class=3D"gmail_quote">

all guests while the 3-level design only aims for Dom0 and driver domains.<=
/div><div class=3D"gmail_quote">Anyway, let&#39;s discuss this later, after=
 I post my new series.</div><div class=3D"gmail_quote"><br></div><div class=
=3D"gmail_quote">

<br></div><div class=3D"gmail_quote">Wei.</div><div><br></div></div><br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padd=
ing-left:1ex">

<span class=3D""><font color=3D"#888888">
David<br>
</font></span><div class=3D""><div class=3D"h5"><br>
_______________________________________________<br>
Xen-devel mailing list<br>
<a href=3D"mailto:Xen-devel@lists.xen.org">Xen-devel@lists.xen.org</a><br>
<a href=3D"http://lists.xen.org/xen-devel" target=3D"_blank">http://lists.x=
en.org/xen-devel</a><br>
</div></div></blockquote></div><br></div></div>

--089e01493ee4597d1204d605e12a--


--===============7486848675757517416==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============7486848675757517416==--