[Bug 1788098] Comment bridged from LTC Bugzilla

2019-09-27 Thread bugproxy
--- Comment From p...@au1.ibm.com 2019-09-27 01:51 EDT--- (In reply to comment #73) > Leonardo, can you elaborate on the 'other possible issues'? We're hesitant > to pull 18 patches into a stable kernel under the assumption that they > *might* fix some *potential* issues, without clear

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-09-26 Thread bugproxy
--- Comment From mranw...@us.ibm.com 2019-09-26 15:42 EDT--- Re-opening on our side to test in 19.10. Everything should be there for that, but it would be good to confirm this in time to get any needed fixes to 20.04, too. Just being clear at this point we don't need to target bionic -

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-05-13 Thread bugproxy
--- Comment From mranw...@us.ibm.com 2019-05-13 17:04 EDT--- Adding Paul Mackerras - can you help with the context for the patches - beyond the potential performance impact? We were picking up this series because it fixes the migration problem, which appeared after adding a patch for

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-05-10 Thread bugproxy
--- Comment From leona...@ibm.com 2019-05-10 19:54 EDT--- Hello Juerg, As this complete list was suggested by Paul, I think he may be the best person to show the context of the patch series. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-04-29 Thread bugproxy
--- Comment From leona...@ibm.com 2019-04-29 18:50 EDT--- (In reply to comment #70) > Leonardo, since you seem to have a reliable reproducer now, could you give > this test kernel [1] a try? It just contains commit c066fafc595e ("KVM: PPC: > Book3S HV: Use correct pagesize in

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-04-10 Thread bugproxy
--- Comment From leona...@ibm.com 2019-04-10 12:08 EDT--- (In reply to comment #68) > In comment #22 above, it states that "In a meeting with lagarcia, I was > informed this patch is very important, and that it is already on kernel > 4.18-15 onwards." > > So, I assume that the required

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-04-10 Thread bugproxy
--- Comment From p...@au1.ibm.com 2019-04-10 04:10 EDT--- (In reply to comment #66) > Stefan NACK'ed the series. For some unknown reason that email did make it > into the archive so here is ist content: > > > Since commit fb1522e099f0 ("KVM: update to new mmu_notifier semantic > > v2",

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-04-08 Thread bugproxy
--- Comment From leona...@ibm.com 2019-04-08 10:37 EDT--- This (In reply to comment #64) > Hi Leonardo, > unfortunately there was an issue with the SRU request and Juerg NACK-ed it, > please have a look here: > https://lists.ubuntu.com/archives/kernel-team/2019-March/099128.html > Please

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-03-26 Thread bugproxy
--- Comment From leona...@ibm.com 2019-03-26 13:12 EDT--- Updating: The patchset was acked by Juerg Haefliger on Mar 13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-03-14 Thread bugproxy
--- Comment From leona...@ibm.com 2019-03-14 15:47 EDT--- Patchset SRU [Impact] * VMs have a high chance to hit guest migration issues if more than one guest migration happens at a time, while using THP on ppc64le. * Migrating VMs in parallel will cause at least one guest to crash about

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-03-12 Thread bugproxy
--- Comment From leona...@ibm.com 2019-03-12 14:52 EDT--- (In reply to comment #60) The patches were sent to Ubuntu kernel-team mailing list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-02-26 Thread bugproxy
--- Comment From leona...@ibm.com 2019-02-26 12:58 EDT--- Here are the patches: https://gitlab.com/LeoBras/bionic/compare/master...lp1788098 Also, I attached a tgz with the patches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-02-26 Thread bugproxy
--- Comment From leona...@ibm.com 2019-02-26 12:36 EDT--- (In reply to comment #41) > ...or perhaps I've misunderstood. Are the patches listed in comment #23 the > complete set required to resolve the issue (with no complex backporting > required)? Yes, the patches listed by Paul are the

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-02-25 Thread bugproxy
--- Comment From leona...@ibm.com 2019-02-25 18:35 EDT--- I cherry-picked all patches on top of ubuntu-bionic (Ubuntu-4.15.0-45.48). Then, the next step was trying to find a way to reproduce the bug. I have noted, after several tests, that the previous suggestion of Michael Ranweiler was

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-02-19 Thread bugproxy
--- Comment From p...@au1.ibm.com 2019-02-19 20:52 EDT--- (In reply to comment #34) > In a meeting with lagarcia, I was informed this patch is very important, and > that it is already on kernel 4.18-15 onwards. > > In fact, including this one. there are two important patches on this

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-02-08 Thread bugproxy
--- Comment From leona...@ibm.com 2019-02-08 14:05 EDT--- In a meeting with lagarcia, I was informed this patch is very important, and that it is already on kernel 4.18-15 onwards. In fact, including this one. there are two important patches on this subject:

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-01-24 Thread bugproxy
--- Comment From leona...@ibm.com 2019-01-24 09:34 EDT--- By the test results, the problem doesn't seem to reproduce. Are there any other suggestions to reproduce it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-01-24 Thread bugproxy
--- Comment From leona...@ibm.com 2019-01-24 09:26 EDT--- By suggestion of Michael Ranweiler, I did some concurrent migration tests. In fact, I just repeated the procedure used before, but did it twice at roughly the same time (in parallel). The results are attached. Migration 1:

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-01-04 Thread bugproxy
--- Comment From leona...@ibm.com 2019-01-04 14:29 EDT--- Test: Verify all memory after migration ### Host: ### # uname -a Linux host 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux #cat

[Bug 1788098] Comment bridged from LTC Bugzilla

2019-01-04 Thread bugproxy
--- Comment From leona...@ibm.com 2019-01-04 06:12 EDT--- I have tried the following test in order to reproduce the bug: ## root@localhost:~# uname -a Linux localhost 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@localhost:~# cat

[Bug 1788098] Comment bridged from LTC Bugzilla

2018-12-21 Thread bugproxy
--- Comment From leona...@ibm.com 2018-12-21 12:10 EDT--- Hello, I have been trying to reproduce this bug over this week, but I couldn't do so on Ubuntu. Could anyone verify what I have been doing wrong? # ## QEMU I have built version Qemu 3.1.0 and made sure the patch