From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Halil Pasic <pasic@linux.vnet.ibm.com>,
Pierre Morel <pmorel@linux.vnet.ibm.com>,
Yi Min Zhao <zyimin@linux.vnet.ibm.com>,
David Hildenbrand <david@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>,
"Jason J . Herne" <jjherne@linux.vnet.ibm.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH/RFC 2/3] s390x/ais: enable ais when migration is available
Date: Mon, 25 Sep 2017 13:45:32 +0200 [thread overview]
Message-ID: <20170925134532.08e9e273.cohuck@redhat.com> (raw)
In-Reply-To: <20da1950-3aa5-c29f-3d54-4f82289f34f1@de.ibm.com>
On Mon, 25 Sep 2017 12:12:49 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 09/25/2017 12:07 PM, Cornelia Huck wrote:
> > On Fri, 22 Sep 2017 16:27:00 +0200
> > Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
> >
> >> One thing I would find very helpful is what do we expect to work and not
> >> work for which version. Kind of a matrix. For instance should vfio pci
> >> work for versions prior 2.11. I think in the not so distant past we
> >> changed how SIC works (so it complains when we don't have ais).
> >
> > A matrix sounds like a good idea.
>
> I think we do not even need a matrix, a minimum level will suffice because...
> >
> > I don't think we really ever had a setup that worked out of the box
>
> exactly: ...it never worked until 2.10 and we do not have libvirt support yet.
> Now with the fix 2.10 will also not work, so I think its fair to say
>
> PCI passthrough via VFIO will be supported for
> - KVM: host kernel >= 4.13
> - TCG: TBD
> - QEMU >= 2.11
> - libvirt TBD
Make that zpci-per-se, no?
with KVM: host kernel >= 4.13 && QEMU >= 2.11
with TCG: tbd, I don't think anybody has time to wire this up for 2.11
Apropos libvirt: How will it determine whether zpci should be
supported? There are some old QEMU + KVM combinations out there that
will have a phb (but not be usable by stock Linux guests as the feature
bits are missing). Version fence? Check for cpu feature support?
next prev parent reply other threads:[~2017-09-25 11:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 8:38 [Qemu-devel] [PATCH/RFC 0/3] ais fixups for 2.11 Christian Borntraeger
2017-09-22 8:38 ` [Qemu-devel] [PATCH/RFC 1/3] s390x/ais: disable ais facility as it is broken Christian Borntraeger
2017-09-26 12:01 ` David Hildenbrand
2017-09-22 8:38 ` [Qemu-devel] [PATCH/RFC 2/3] s390x/ais: enable ais when migration is available Christian Borntraeger
2017-09-22 12:13 ` Pierre Morel
2017-09-22 12:40 ` Christian Borntraeger
2017-09-22 13:49 ` Cornelia Huck
2017-09-22 14:02 ` Pierre Morel
2017-09-22 14:07 ` Christian Borntraeger
2017-09-22 14:27 ` Halil Pasic
2017-09-25 10:07 ` Cornelia Huck
2017-09-25 10:12 ` Christian Borntraeger
2017-09-25 11:45 ` Cornelia Huck [this message]
2017-09-25 11:47 ` Christian Borntraeger
2017-09-26 9:14 ` Yi Min Zhao
2017-09-26 13:04 ` Boris Fiuczynski
2017-09-22 14:38 ` Pierre Morel
2017-09-26 12:23 ` David Hildenbrand
2017-09-26 12:29 ` Christian Borntraeger
2017-09-26 12:33 ` David Hildenbrand
2017-09-26 12:33 ` Christian Borntraeger
2017-09-22 8:38 ` [Qemu-devel] [PATCH/RFC 3/3] s390x/ais: disable ais for compat machines Christian Borntraeger
2017-09-26 12:26 ` David Hildenbrand
2017-09-26 12:45 ` Christian Borntraeger
2017-09-26 13:00 ` David Hildenbrand
2017-09-26 13:32 ` Christian Borntraeger
2017-09-26 13:43 ` Cornelia Huck
2017-09-26 13:45 ` Christian Borntraeger
2017-09-22 11:27 ` [Qemu-devel] [PATCH/RFC 0/3] ais fixups for 2.11 Christian Borntraeger
2017-09-22 13:08 ` Christian Borntraeger
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=20170925134532.08e9e273.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=zyimin@linux.vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).