From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40956) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a7R0I-0008Ue-SY for qemu-devel@nongnu.org; Fri, 11 Dec 2015 11:57:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a7R0H-0003e6-W0 for qemu-devel@nongnu.org; Fri, 11 Dec 2015 11:57:10 -0500 Received: from smtp02.citrix.com ([66.165.176.63]:9358) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a7R0H-0003e2-Rd for qemu-devel@nongnu.org; Fri, 11 Dec 2015 11:57:09 -0500 Message-ID: <1449852961.30975.71.camel@citrix.com> From: Ian Campbell Date: Fri, 11 Dec 2015 16:56:01 +0000 In-Reply-To: References: <56548BD202000078000B881F@prv-mh.provo.novell.com> <56548D8402000078000B8840@prv-mh.provo.novell.com> <5665921202000078000BCA2A@prv-mh.provo.novell.com> <5665B56E02000078000BCB52@prv-mh.provo.novell.com> <566AF76502000078000BEB76@prv-mh.provo.novell.com> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [Xen-devel] [PATCH RFC v2 4/4] xen/MSI: re-expose masking capability List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefano Stabellini , Jan Beulich Cc: xen-devel , qemu-devel@nongnu.org On Fri, 2015-12-11 at 16:44 +0000, Stefano Stabellini wrote: > =C2=A0 > It is not possible to do this at runtime. I think we should do this at > compile time because in any case it is not supported to run a QEMU built > for a given Xen version on a different Xen version. I am currently working pretty hard to make this possible in the future, it would be a shame to add another reason it wasn't possible at this stage. I proposed (in <1445442435.9563.184.camel@citrix.com>) that as well as the various stable libraries extracted from libxenctrl we will probably also want to have a libxendevicemodel.so at some point, to provide a stable way to interface with all the stuff which being a DM involves. Maybe that library could contain a way to get this information? (In which case it could be hardcoded at compile time now and I'll see what I can do when I get to producing the library). For the original issue here, could the flag be exposed as a XEN_SYSCTL_PHYSCAP_???? Ian.