From mboxrd@z Thu Jan  1 00:00:00 1970
From: Juan Quintela <quintela@redhat.com>
Subject: KVM call minutes for 2014-05-27
Date: Tue, 27 May 2014 16:21:00 +0200
Message-ID: <87r43f5mlv.fsf@troll.troll>
Reply-To: quintela@redhat.com
Mime-Version: 1.0
Content-Type: text/plain
To: KVM devel mailing list <kvm@vger.kernel.org>,
	Developers qemu-devel <qemu-devel@nongnu.org>
Return-path: <qemu-devel-bounces+gceq-qemu-devel=gmane.org@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>
Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
List-Id: kvm.vger.kernel.org


CPU models on s390
------------------

(If you look at call for agenda, you can see that there was a pdf for
helping understand the problem)


- new features only appears on new processors (manchine models).  Old
  models gets exactly the same facilities independently of the Host
  that they are running on.

- if a facility is emulated in the Host, the guest don't know if it is
  there or emulated.

- Lots of discussion about how to implement it.

Participants can do a better conclusion here?


Later, Juan.