[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140226102620.GA4686@redhat.com>
Date: Wed, 26 Feb 2014 11:26:21 +0100
From: Stanislaw Gruszka <sgruszka@...hat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: David Rientjes <rientjes@...gle.com>, boris.ostrovsky@...cle.com,
david.vrabel@...rix.com, Ben Guthro <benjamin.guthro@...rix.com>,
linux-kernel@...r.kernel.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
xen-devel@...ts.xensource.com
Subject: Re: [BUG?] Interrupts enabled after
xen_acpi_processor_resume+0x0/0x34 [xen_acpi_processor]
On Mon, Feb 10, 2014 at 09:37:27AM -0500, Konrad Rzeszutek Wilk wrote:
> > > But I'm not sure if that is good solution. It crate some not necessery
> > > sysfs directories and files. Additionaly it can restore CPU C-states
> > > after some other drivers resume, which prehaps require proper C-states.
> >
> > Yes.
> > >
> > > Hence maybe adding direct notify from xen core resume will be better
> > > idea (proposed patch below). Plese let me know what you think, I'll
> > > provide solution which you choose to bug reporters for testing.
> >
> > Let me think about it for a day or so.
>
> Sorry for the delay. I think this is fine.
I'm sorry for delay too. I provided test kernel with the patch to bug
reporter, but have not get any answer since two weeks now.
I'll post the patch in the next email, I hope someone can test it (I'm
not xen user). I'm pretty sure it fixes the problem, but not sure if it
does not cause some crash. To test is enough to perform suspend/resume
cycle (thought I'm not sure if suspended should be just guest or whole
system with hypervisor).
Thanks
Stanislaw
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists