From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: stable@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
KVM <kvm@vger.kernel.org>, "Cornelia Huck" <cohuck@redhat.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
"David Hildenbrand" <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
"Thomas Huth" <thuth@redhat.com>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Nitesh Narayan Lal" <nitesh@redhat.com>,
"Halil Pasic" <pasic@linux.ibm.com>
Subject: Re: [PATCH 0/1] KVM: s390: backport for stable of "KVM: s390: index
Date: Mon, 20 Sep 2021 17:24:39 +0200 [thread overview]
Message-ID: <YUint4b1ETglbj8z@kroah.com> (raw)
In-Reply-To: <20210920150616.15668-1-borntraeger@de.ibm.com>
On Mon, Sep 20, 2021 at 05:06:15PM +0200, Christian Borntraeger wrote:
> Stable team,
>
> here is a backport for 4.19 of
> commit a3e03bc1368 ("KVM: s390: index kvm->arch.idle_mask by vcpu_idx")
> This basically removes the kick_mask parts that were introduced with
> kernel 5.0 and fixes up the location of the idle_mask to the older
> place.
Now queued up, thanks.
> FWIW, it might be a good idea to also backport
> 8750e72a79dd ("KVM: remember position in kvm->vcpus array") to avoid
> a performance regression for large guests (many vCPUs) when this patch
> is applied.
> @Paolo Bonzini, would you be ok with 8750e72a79dd in older stable releases?
That would also have to go into 5.4.y, right?
thanks,
greg k-h
next prev parent reply other threads:[~2021-09-20 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 15:06 [PATCH 0/1] KVM: s390: backport for stable of "KVM: s390: index Christian Borntraeger
2021-09-20 15:06 ` [PATCH 1/1] KVM: s390: index kvm->arch.idle_mask by vcpu_idx Christian Borntraeger
2021-09-21 2:43 ` Halil Pasic
2021-09-20 15:24 ` Greg KH [this message]
2021-09-20 15:30 ` [PATCH 0/1] KVM: s390: backport for stable of "KVM: s390: index Christian Borntraeger
2021-09-20 18:05 ` Paolo Bonzini
2021-09-21 8:46 ` Christian Borntraeger
2021-09-21 13:04 ` Paolo Bonzini
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=YUint4b1ETglbj8z@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nitesh@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.org \
--cc=thuth@redhat.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