From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
Developers qemu-devel <qemu-devel@nongnu.org>
Subject: KVM call minutes for 2014-05-27
Date: Tue, 27 May 2014 16:21:00 +0200 [thread overview]
Message-ID: <87r43f5mlv.fsf@troll.troll> (raw)
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.
reply other threads:[~2014-05-27 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r43f5mlv.fsf@troll.troll \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.