Message ID | CALdTtns8amcyxJbNGwaOB2wAGe8CbWb7-59RQQwJBWpXHUa5+A@mail.gmail.com |
---|---|
State | New |
Headers | show |
On Thu, Jul 20, 2017 at 03:54:46PM -0600, dann frazier wrote: > BugLink: https://bugs.launchpad.net/bugs/1673564 > > There's a pretty nasty errata for ThunderX SoCs in which a guest can > cause interrupts to be disabled on the host kernel. The symptoms vary, > but it's easy to reproduce running a bunch of parallel VM start/stop > loops. > > There was quite a bit of backporting required for the patches in this > series. For such patches, I've described the changes required in a > comment above my S-o-B. They are mostly mechanical transformations to > revert macro cleanups that occurred post-4.11. > > This survived an overnight run of my parallel VM start/stop test on a > CRB1S, whereas an unpatched system would fail in just a few minutes. > > I created this backport as a stepping stone towards 4.10. While I > suspect artful's days of 4.11 are quickly coming to an end, I figured > I might as well submit it since I have it. Note that while this > backport cherry-picks cleanly back to Ubuntu's 4.10, it isn't > compatible - by which I mean, KVM crashes immediately. Diagnosing that > is my next step. > > The following changes since commit bfdccafa8f542c8f9740a64ecb110e4982e336c0: > > platform/x86: thinkpad_acpi: add mapping for new hotkeys (2017-07-20 > 14:50:48 -0500) > > are available in the git repository at: > > git://git.launchpad.net/~dannf/ubuntu/+source/linux/+git/linux > lp1673564-artful > > for you to fetch changes up to 08ecebdce871761059927c93adcb3cb90da2680e: > > KVM: arm64: Log an error if trapping a write-to-read-only GICv3 > access (2017-07-20 15:31:07 -0600) Quick question. When I fetched your tree I noticed a lp1673564-unstable branch as well. Is that one ready to go for unstable? Seth
On Mon, Jul 24, 2017 at 11:06:31AM -0500, Seth Forshee wrote: > On Thu, Jul 20, 2017 at 03:54:46PM -0600, dann frazier wrote: > > BugLink: https://bugs.launchpad.net/bugs/1673564 > > > > There's a pretty nasty errata for ThunderX SoCs in which a guest can > > cause interrupts to be disabled on the host kernel. The symptoms vary, > > but it's easy to reproduce running a bunch of parallel VM start/stop > > loops. > > > > There was quite a bit of backporting required for the patches in this > > series. For such patches, I've described the changes required in a > > comment above my S-o-B. They are mostly mechanical transformations to > > revert macro cleanups that occurred post-4.11. > > > > This survived an overnight run of my parallel VM start/stop test on a > > CRB1S, whereas an unpatched system would fail in just a few minutes. > > > > I created this backport as a stepping stone towards 4.10. While I > > suspect artful's days of 4.11 are quickly coming to an end, I figured > > I might as well submit it since I have it. Note that while this > > backport cherry-picks cleanly back to Ubuntu's 4.10, it isn't > > compatible - by which I mean, KVM crashes immediately. Diagnosing that > > is my next step. > > > > The following changes since commit bfdccafa8f542c8f9740a64ecb110e4982e336c0: > > > > platform/x86: thinkpad_acpi: add mapping for new hotkeys (2017-07-20 > > 14:50:48 -0500) > > > > are available in the git repository at: > > > > git://git.launchpad.net/~dannf/ubuntu/+source/linux/+git/linux > > lp1673564-artful > > > > for you to fetch changes up to 08ecebdce871761059927c93adcb3cb90da2680e: > > > > KVM: arm64: Log an error if trapping a write-to-read-only GICv3 > > access (2017-07-20 15:31:07 -0600) > > Quick question. When I fetched your tree I noticed a lp1673564-unstable > branch as well. Is that one ready to go for unstable? Nevermind, I see that you had already sent that one and I had applied it. I've applied this one to artful/master-next. Thanks! Seth
On Mon, Jul 24, 2017 at 10:06 AM, Seth Forshee <seth.forshee@canonical.com> wrote: > On Thu, Jul 20, 2017 at 03:54:46PM -0600, dann frazier wrote: >> BugLink: https://bugs.launchpad.net/bugs/1673564 >> >> There's a pretty nasty errata for ThunderX SoCs in which a guest can >> cause interrupts to be disabled on the host kernel. The symptoms vary, >> but it's easy to reproduce running a bunch of parallel VM start/stop >> loops. >> >> There was quite a bit of backporting required for the patches in this >> series. For such patches, I've described the changes required in a >> comment above my S-o-B. They are mostly mechanical transformations to >> revert macro cleanups that occurred post-4.11. >> >> This survived an overnight run of my parallel VM start/stop test on a >> CRB1S, whereas an unpatched system would fail in just a few minutes. >> >> I created this backport as a stepping stone towards 4.10. While I >> suspect artful's days of 4.11 are quickly coming to an end, I figured >> I might as well submit it since I have it. Note that while this >> backport cherry-picks cleanly back to Ubuntu's 4.10, it isn't >> compatible - by which I mean, KVM crashes immediately. Diagnosing that >> is my next step. >> >> The following changes since commit bfdccafa8f542c8f9740a64ecb110e4982e336c0: >> >> platform/x86: thinkpad_acpi: add mapping for new hotkeys (2017-07-20 >> 14:50:48 -0500) >> >> are available in the git repository at: >> >> git://git.launchpad.net/~dannf/ubuntu/+source/linux/+git/linux >> lp1673564-artful >> >> for you to fetch changes up to 08ecebdce871761059927c93adcb3cb90da2680e: >> >> KVM: arm64: Log an error if trapping a write-to-read-only GICv3 >> access (2017-07-20 15:31:07 -0600) > > Quick question. When I fetched your tree I noticed a lp1673564-unstable > branch as well. Is that one ready to go for unstable? Yeah - in fact, you already pulled it :) https://lists.ubuntu.com/archives/kernel-team/2017-July/085621.html -dann