qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Pierre Morel <pmorel@linux.vnet.ibm.com>,
	Halil Pasic <pasic@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: Fri, 22 Sep 2017 15:49:20 +0200	[thread overview]
Message-ID: <20170922154920.10fd08ee.cohuck@redhat.com> (raw)
In-Reply-To: <ccb6e3eb-320e-b5dd-f728-09d8cab440c4@de.ibm.com>

On Fri, 22 Sep 2017 14:40:31 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> On 09/22/2017 02:13 PM, Pierre Morel wrote:
> > On 22/09/2017 10:38, Christian Borntraeger wrote:  
> >> Instead of unconditionally enabling the KVM AIS capability
> >> in the kvm arch init function, do this in the flic realize function
> >> when we know if migration is available. This requires to initialize
> >> flic before the CPUs.  
> > 
> > I am not sure to agree.
> > 
> > AIS facility is used for PCI (currently only PCI)
> > We want to support PCI emulation and PCI VFIO
> > 
> > 
> > Not having AIS support in the host kernel or not supporting AISM in the host kernel does not affect the emulation.
> > Neither virtio-pci nor TCG.
> > The only devices, (currently), which can not work without AIS and is not migratable without AISM are PCI VFIO devices.  
> 
> This patch enable the conditional enablement facility for the KVM host mask. The cpu model enablement is done
> differently for KVM and TCG anyway.
> Right now AIS is only enabled for KVM. For TCG AIS is not implemented at all and disabled. So for whenever this
> is fixed in TCG it can be handled then. 

Yes, that will probably still need quite a bit of work before we are
there.

> 
> And for emulated devices under KVM you still need the kernel support - otherwise migration is really broken for
> the nimm/dimm values.

Agreed, you need this for any pci device.

I have not yet reviewed this (or tested under tcg). I'd like to hear
David's opinion, though.

  reply	other threads:[~2017-09-22 13:49 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 [this message]
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
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=20170922154920.10fd08ee.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).