From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joanna Rutkowska Subject: Re: Re: [PATCH][VTD] force boot to fail if interrupt remapping cannot be enabled when iommu=force Date: Thu, 28 Apr 2011 20:26:43 +0200 Message-ID: <4DB9B163.4040908@invisiblethingslab.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0892319786==" Return-path: 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: Keir Fraser Cc: "Cihula, Joseph" , "xen-devel@lists.xensource.com" , "Kay, Allen M" , Rafal Wojtczuk , Jan Beulich List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0892319786== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA5AD1A7AA4E5C32372F15FB8" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA5AD1A7AA4E5C32372F15FB8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 04/28/11 19:05, Keir Fraser wrote: > On 28/04/2011 00:42, "Kay, Allen M" wrote: >=20 >> Force Xen boot to fail if interrupt remapping fails to enable and the >> following are true: iommu=3Dforce is set as xen boot parameter, VT-d e= ngine HW >> is interrupt remapping capable, DMAR_INTR_REMAP bit is set in DMAR fla= gs. >> This forces iommu=3Dforce boot instances has interrupt remapping enabl= ed if HW >> and BIOS supports it. >=20 > If HW and BIOS support it, why would it fail to be enabled? This doesn'= t > look like a particularly useful panic() path. If interrupt remapping is= so > important, perhaps iommu=3Dforce should unconditionally require it, and= panic > in its absence regardless of platform features? Indeed, seems to me like a desired behavior. j. > As it is, this looks like a > panic that is never realistically going to trigger. >=20 > -- Keir >=20 >> Signed-off-by: Allen Kay >=20 >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel --------------enigA5AD1A7AA4E5C32372F15FB8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNubFjAAoJEDaIqHeRBUM05bEH/Rvzfvri0f8hSp8BQpevVReN lKGacgPwMsw/lpUj7TVEawLRXbY5oslrZLLkA17g2fX7RNJuLo764oKl/XISrbB4 tZKS5OwosqGtJl9Jm+BlMB1/AJ+/rbRwzN3ktySu/ab9jAiefFoG3FpOhbL1QdBo +w7aB2sT8y29Dfi6fCMvoCpdfwPyBLdHo6L4OR+yduKdb/4UHheAgUeIjmqEu6Cg A+4n3oWY1+HJSe/IzRlHZecyjYIdMoXVdsjDMTntyrXwbPP1GHKOylZnYwM6f5ay z5/V9WJmUx98USxfpKMSAl6xNn/Lcd3WBebMCZSRViFbvxbBSG3HYnIat7avy7I= =B4aW -----END PGP SIGNATURE----- --------------enigA5AD1A7AA4E5C32372F15FB8-- --===============0892319786== 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.xensource.com http://lists.xensource.com/xen-devel --===============0892319786==--