All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: stable@vger.kernel.org, frankja@linux.ibm.com, imbrenda@linux.ibm.com
Subject: Re: [PATCH 5.4.y] KVM: s390: disable migration mode when dirty tracking is disabled
Date: Mon, 6 Mar 2023 18:26:04 +0100	[thread overview]
Message-ID: <ZAYiLCkl+nuabM4h@kroah.com> (raw)
In-Reply-To: <20230306151331.4531-1-nrb@linux.ibm.com>

On Mon, Mar 06, 2023 at 04:13:31PM +0100, Nico Boehr wrote:
> Migration mode is a VM attribute which enables tracking of changes in
> storage attributes (PGSTE). It assumes dirty tracking is enabled on all
> memslots to keep a dirty bitmap of pages with changed storage attributes.
> 
> When enabling migration mode, we currently check that dirty tracking is
> enabled for all memslots. However, userspace can disable dirty tracking
> without disabling migration mode.
> 
> Since migration mode is pointless with dirty tracking disabled, disable
> migration mode whenever userspace disables dirty tracking on any slot.
> 
> Also update the documentation to clarify that dirty tracking must be
> enabled when enabling migration mode, which is already enforced by the
> code in kvm_s390_vm_start_migration().
> 
> Also highlight in the documentation for KVM_S390_GET_CMMA_BITS that it
> can now fail with -EINVAL when dirty tracking is disabled while
> migration mode is on. Move all the error codes to a table so this stays
> readable.
> 
> To disable migration mode, slots_lock should be held, which is taken
> in kvm_set_memory_region() and thus held in
> kvm_arch_prepare_memory_region().
> 
> Restructure the prepare code a bit so all the sanity checking is done
> before disabling migration mode. This ensures migration mode isn't
> disabled when some sanity check fails.
> 
> Cc: stable@vger.kernel.org
> Fixes: 190df4a212a7 ("KVM: s390: CMMA tracking, ESSA emulation, migration mode")
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
> Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Link: https://lore.kernel.org/r/20230127140532.230651-2-nrb@linux.ibm.com
> Message-Id: <20230127140532.230651-2-nrb@linux.ibm.com>
> [frankja@linux.ibm.com: fixed commit message typo, moved api.rst error table upwards]
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> (cherry picked from commit f2d3155e2a6bac44d16f04415a321e8707d895c6)
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>

Thanks, all backports now queued up.

greg k-h

      reply	other threads:[~2023-03-06 17:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 10:53 FAILED: patch "[PATCH] KVM: s390: disable migration mode when dirty tracking is" failed to apply to 5.4-stable tree gregkh
2023-03-06 15:13 ` [PATCH 5.4.y] KVM: s390: disable migration mode when dirty tracking is disabled Nico Boehr
2023-03-06 17:26   ` Greg KH [this message]

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=ZAYiLCkl+nuabM4h@kroah.com \
    --to=greg@kroah.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=nrb@linux.ibm.com \
    --cc=stable@vger.kernel.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.