From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39629)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rkrcmar@redhat.com>) id 1bosxC-0001Df-5i
	for qemu-devel@nongnu.org; Tue, 27 Sep 2016 10:01:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rkrcmar@redhat.com>) id 1bosx5-0003mA-CH
	for qemu-devel@nongnu.org; Tue, 27 Sep 2016 10:01:49 -0400
Received: from mx1.redhat.com ([209.132.183.28]:37764)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rkrcmar@redhat.com>) id 1bosx5-0003m0-5F
	for qemu-devel@nongnu.org; Tue, 27 Sep 2016 10:01:43 -0400
Date: Tue, 27 Sep 2016 16:01:39 +0200
From: Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>
Message-ID: <20160927140138.GD26148@potion>
References: <20160922210432.18680-1-rkrcmar@redhat.com>
	<20160922210432.18680-6-rkrcmar@redhat.com>
	<eab44f91-4d9f-1425-2e77-927dd3a5c144@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <eab44f91-4d9f-1425-2e77-927dd3a5c144@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 5/5] intel_iommu: do not allow EIM without
 KVM support
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>, Igor Mammedov <imammedo@redhat.com>, Richard Henderson <rth@twiddle.net>, Eduardo Habkost <ehabkost@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>

2016-09-23 11:27+0200, Paolo Bonzini:
> Since the whole IOMMU feature is new and somewhat experimental, I think
> it's okay to just make EIM the default for >=2.8 machine types if KVM is
> on (using DEFINE_PROP_ON_OFF_AUTO; auto means true if KVM is on and

Sounds good.

> false otherwise, and pc-2.7 would set eim=off).

What about eim=on in pc-2.7, to avoid breaking migration?