From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH 3/5] xen: virq, remove VIRQ_XC_RESERVED Date: Mon, 6 Aug 2012 15:49:31 +0100 Message-ID: <501FD97B.4030906@citrix.com> References: <1344023454-31425-1-git-send-email-jean.guyader@citrix.com> <1344023454-31425-4-git-send-email-jean.guyader@citrix.com> <501F97F90200007800092CAC@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jean Guyader Cc: "Jean Guyader (3P)" , "xen-devel@lists.xen.org" , Ross Philipson , Jan Beulich , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 06/08/12 15:46, Jean Guyader wrote: > On 6 August 2012 09:10, Jan Beulich wrote: >>>>> On 03.08.12 at 21:50, Jean Guyader 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