From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH 3 of 6] evtchn delivery on HVM Date: Fri, 23 Apr 2010 11:33:48 -0400 Message-ID: <20100423153348.GA16823@phenom.dumpdata.com> References: <20100422205836.GJ31220@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org > > * How should CPU0 event-channel notifications be delivered? > > + * val[63:56] == 0: val[55:0] is a delivery GSI (Global System > > Interrupt). > > + * val[63:56] == 1: val[55:0] is a delivery PCI INTx line, as follows: > > + * Domain = val[47:32], Bus = val[31:16], > > + * DevFn = val[15: 8], IntX = val[ 1: 0] > > + * If val == 0 then CPU0 event-channel notifications are not delivered. > > > > I don't see val[63:56] == 2 ? > > > > the comment on the other patch needs to be update as well Yup, and it looks that this also needs a patch to xen-unstable.hg as that header file is missing this data too.