From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jean Guyader <jean.guyader@gmail.com>
Cc: "Jean Guyader (3P)" <jean.guyader@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Ross Philipson <Ross.Philipson@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH 3/5] xen: virq, remove VIRQ_XC_RESERVED
Date: Mon, 6 Aug 2012 15:49:31 +0100 [thread overview]
Message-ID: <501FD97B.4030906@citrix.com> (raw)
In-Reply-To: <CAEBdQ920zPHQuLng=ncPonFHoSnvgFb3rz4wo+MZP5y88GAAxA@mail.gmail.com>
On 06/08/12 15:46, Jean Guyader wrote:
> On 6 August 2012 09:10, Jan Beulich <JBeulich@suse.com> wrote:
>>>>> On 03.08.12 at 21:50, Jean Guyader <jean.guyader@citrix.com> wrote:
>>> VIRQ_XC_RESERVED was reserved for V4V but we have switched
>>> to event channels so this place holder is no longer required.
>> I'm fine with this change, but is a future re-use of the value indeed
>> not going to cause problems on XenServer (or wherever else this
>> is patch set coming from)?
>>
> That may need to be confirmed but I don't think XenServer is using v4v
> yet, their plan
> is to pick it up from upstream. So removing this VIRQ should be fine.
>
> Jean
Yes - we don't use it, but are interested when XenClient can
successfully upstream it.
~Andrew
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next prev parent reply other threads:[~2012-08-06 14:49 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 19:50 [PATCH 0/5] RFC: V4V (v3) Jean Guyader
2012-08-03 19:50 ` [PATCH 1/5] xen: add ssize_t Jean Guyader
2012-08-06 8:08 ` Jan Beulich
2012-08-06 14:47 ` Jean Guyader
2012-08-09 9:51 ` Tim Deegan
2012-08-09 10:19 ` Jean Guyader
2012-08-09 10:39 ` Jan Beulich
2012-08-09 10:48 ` Jean Guyader
2012-08-09 13:02 ` Jan Beulich
2012-08-09 10:59 ` Tim Deegan
2012-08-09 11:08 ` Jean Guyader
2012-08-03 19:50 ` [PATCH 2/5] xen: Introduce guest_handle_for_field Jean Guyader
2012-08-03 19:50 ` [PATCH 3/5] xen: virq, remove VIRQ_XC_RESERVED Jean Guyader
2012-08-06 8:10 ` Jan Beulich
2012-08-06 14:46 ` Jean Guyader
2012-08-06 14:49 ` Andrew Cooper [this message]
2012-08-06 14:56 ` Ian Campbell
2012-08-06 15:01 ` Jean Guyader
2012-08-06 15:13 ` Ian Campbell
2012-08-06 15:46 ` Jan Beulich
2012-08-03 19:50 ` [PATCH 4/5] xen: events, exposes evtchn_alloc_unbound_domain Jean Guyader
2012-08-06 8:19 ` Jan Beulich
2012-08-09 10:06 ` Tim Deegan
2012-08-09 10:23 ` Ian Campbell
2012-08-09 10:35 ` Tim Deegan
2012-08-09 10:40 ` Jean Guyader
2012-08-09 23:25 ` Jean Guyader
2012-08-10 7:35 ` Jan Beulich
2012-08-10 7:51 ` Jean Guyader
2012-08-10 7:57 ` Jan Beulich
2012-08-23 12:03 ` Jean Guyader
2012-08-03 19:50 ` [PATCH 5/5] xen: Add V4V implementation Jean Guyader
2012-08-06 8:45 ` Jan Beulich
2012-08-23 11:57 ` Jean Guyader
2012-08-24 20:06 ` Jan Beulich
2012-09-01 20:58 ` Jean Guyader
2012-09-01 20:56 ` Jean Guyader
2013-06-11 17:10 ` [PATCH 5/5] xen: Add V4V implementation - padding question Ross Philipson
2013-06-11 17:25 ` Tim Deegan
2013-06-11 17:40 ` Ross Philipson
2013-06-11 17:54 ` Ross Philipson
2013-06-11 18:04 ` Tim Deegan
2013-06-12 7:45 ` Jan Beulich
2013-06-13 17:21 ` Stefano Stabellini
2012-08-09 10:38 ` [PATCH 5/5] xen: Add V4V implementation Tim Deegan
2012-08-10 16:51 ` Jean Guyader
2012-08-13 9:38 ` Tim Deegan
2012-08-13 12:43 ` Jean Guyader
2012-08-16 12:32 ` Tim Deegan
2012-08-04 13:24 ` [PATCH 0/5] RFC: V4V (v3) Jean Guyader
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=501FD97B.4030906@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=Ross.Philipson@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=jean.guyader@citrix.com \
--cc=jean.guyader@gmail.com \
--cc=xen-devel@lists.xen.org \
/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).