[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20111201143548.GA28114@phenom.dumpdata.com>
Date: Thu, 1 Dec 2011 09:35:48 -0500
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: Borislav Petkov <bp@...64.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, tglx@...utronix.de,
mingo@...hat.com, hpa@...or.com, x86@...nel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux SCSI List <linux-scsi@...r.kernel.org>,
Linux ACPI <linux-acpi@...r.kernel.org>,
Network Development <netdev@...r.kernel.org>,
Linux Wireless List <linux-wireless@...r.kernel.org>,
DRI <dri-devel@...ts.freedesktop.org>,
Florian Mickler <florian@...kler.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux PM List <linux-pm@...ts.linux-foundation.org>,
Maciej Rutecki <maciej.rutecki@...il.com>,
deepthi@...ux.vnet.ibm.com
Subject: Re: 3.2-rc2+: Reported regressions from 3.0 and 3.1
> >From what I can see, you get the following callchain:
>
> start_kernel
> |-> setup_arch
> |-> x86_init.oem.arch_setup = xen_arch_setup
> ....
> |-> check_bugs
> |-> identify_boot_cpu
> |-> identify_cpu
> |-> select_idle_routine
>
>
> so xen_arch_setup will set pm_idle and select_idle_routine will honour
> it. I'm being told this is run either in the dom0 or the paravirt guest
> and if so, I don't see any issue with this for baremetal. So you can
> have my ACK provided this is tested on baremetal too.
Tested on baremetal and there were no abnormalities. Thanks!
--
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