* "KVM: s390: reduce number of IO pins to 1" for stable [not found] <20200706171523.12441-1-pbonzini@redhat.com> @ 2020-07-08 11:33 ` Christian Borntraeger 2020-07-08 12:00 ` Greg KH 0 siblings, 1 reply; 4+ messages in thread From: Christian Borntraeger @ 2020-07-08 11:33 UTC (permalink / raw) To: stable; +Cc: kvm list, Janosch Frank stable team, Please consider commit 774911290c58 ("KVM: s390: reduce number of IO pins to 1") for stable. This can avoid OOM killer activity on highly fragmented memory even when swap and memory is available. We decided too late that this is stable material, so sorry for not marking it correctly. Christian ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: "KVM: s390: reduce number of IO pins to 1" for stable 2020-07-08 11:33 ` "KVM: s390: reduce number of IO pins to 1" for stable Christian Borntraeger @ 2020-07-08 12:00 ` Greg KH 2020-07-08 12:36 ` Christian Borntraeger 0 siblings, 1 reply; 4+ messages in thread From: Greg KH @ 2020-07-08 12:00 UTC (permalink / raw) To: Christian Borntraeger; +Cc: stable, kvm list, Janosch Frank On Wed, Jul 08, 2020 at 01:33:49PM +0200, Christian Borntraeger wrote: > stable team, > > > Please consider commit 774911290c58 ("KVM: s390: reduce number of IO pins to 1") > for stable. This can avoid OOM killer activity on highly fragmented memory > even when swap and memory is available. > > We decided too late that this is stable material, so sorry for not marking it > correctly. For what stable tree(s) is it relevant for? thanks, greg k-h ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: "KVM: s390: reduce number of IO pins to 1" for stable 2020-07-08 12:00 ` Greg KH @ 2020-07-08 12:36 ` Christian Borntraeger 2020-07-09 14:26 ` Sasha Levin 0 siblings, 1 reply; 4+ messages in thread From: Christian Borntraeger @ 2020-07-08 12:36 UTC (permalink / raw) To: Greg KH; +Cc: stable, kvm list, Janosch Frank On 08.07.20 14:00, Greg KH wrote: > On Wed, Jul 08, 2020 at 01:33:49PM +0200, Christian Borntraeger wrote: >> stable team, >> >> >> Please consider commit 774911290c58 ("KVM: s390: reduce number of IO pins to 1") >> for stable. This can avoid OOM killer activity on highly fragmented memory >> even when swap and memory is available. >> >> We decided too late that this is stable material, so sorry for not marking it >> correctly. > > For what stable tree(s) is it relevant for? This improves commit 84223598778ba ("KVM: s390: irq routing for adapter interrupts.") so >= 3.15 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: "KVM: s390: reduce number of IO pins to 1" for stable 2020-07-08 12:36 ` Christian Borntraeger @ 2020-07-09 14:26 ` Sasha Levin 0 siblings, 0 replies; 4+ messages in thread From: Sasha Levin @ 2020-07-09 14:26 UTC (permalink / raw) To: Christian Borntraeger; +Cc: Greg KH, stable, kvm list, Janosch Frank On Wed, Jul 08, 2020 at 02:36:07PM +0200, Christian Borntraeger wrote: > > >On 08.07.20 14:00, Greg KH wrote: >> On Wed, Jul 08, 2020 at 01:33:49PM +0200, Christian Borntraeger wrote: >>> stable team, >>> >>> >>> Please consider commit 774911290c58 ("KVM: s390: reduce number of IO pins to 1") >>> for stable. This can avoid OOM killer activity on highly fragmented memory >>> even when swap and memory is available. >>> >>> We decided too late that this is stable material, so sorry for not marking it >>> correctly. >> >> For what stable tree(s) is it relevant for? > >This improves commit 84223598778ba ("KVM: s390: irq routing for adapter interrupts.") >so >= 3.15 I've queued it for all stable branches, thank you! -- Thanks, Sasha ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-07-09 14:26 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20200706171523.12441-1-pbonzini@redhat.com>
2020-07-08 11:33 ` "KVM: s390: reduce number of IO pins to 1" for stable Christian Borntraeger
2020-07-08 12:00 ` Greg KH
2020-07-08 12:36 ` Christian Borntraeger
2020-07-09 14:26 ` Sasha Levin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox