[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
Interesting.
I had started by reverting the commit entirely, but settled on only reverting the part causing the scheduling issues. I'm not sure if I was as thorough in my testing this fix, across a lot of laptop generations.
I'll test reverting the full commit in the new year, and report back.
I think that, at a minimum - the commit should get some scrutiny by people who might understand the subtleties, and/or unintended side effects better than I.
-Ben On Sat, Dec 22, 2012 at 9:49 PM, Marek Marczykowski <marmarek@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Ok, I can confirm that on xen-4.1-testing tip with above commit reverted
completely problem has gone away, even without sched_ratelimit_us=0. With
Ben's patch (partially revert) no reboot observed, but still sometimes only
pCPU0 is used after resume.
--
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
- References:
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
- Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
|