From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Xen4.2 S3 regression?
Date: Mon, 24 Sep 2012 10:04:11 -0400
Message-ID: <20120924140411.GH31618@phenom.dumpdata.com>
References: <CAOvdn6XKPOMNn6AjuYvZvPXRRJffN3po5GXe1Yh1-m0hisMK_w@mail.gmail.com>
	<CC8273A0.4C9DD%keir@xen.org>
	<50605E9A020000780009D486@nat28.tlf.novell.com>
	<CAOvdn6XmB6rj3_QVU+59V8p24Y5G47AWxVEM=id02JWXkuhibQ@mail.gmail.com>
	<5060640B020000780009D4D2@nat28.tlf.novell.com>
	<CAOvdn6XLy8zR2rb2MEyi2aT9LQiFvFLY_H02p181mTsVLVTZkw@mail.gmail.com>
	<20120924122203.GG8912@reaktio.net>
	<CAOvdn6XV4eoA-FfFns1xhx7HCUqXc7KHxZwyKuT4FHG8s3R5RQ@mail.gmail.com>
	<CAAnFQG9PLQjdh6Ab6=Y5ZGM1s4nGdLekKU=pcKNMxt4rmt_RKA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <CAAnFQG9PLQjdh6Ab6=Y5ZGM1s4nGdLekKU=pcKNMxt4rmt_RKA@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Javier Marcet <jmarcet@gmail.com>
Cc: Keir Fraser <keir@xen.org>, john.baboval@citrix.com, xen-devel <xen-devel@lists.xen.org>, Ben Guthro <ben@guthro.net>, Jan Beulich <JBeulich@suse.com>, Thomas Goetz <thomas.goetz@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Mon, Sep 24, 2012 at 02:37:22PM +0200, Javier Marcet wrote:
> On Mon, Sep 24, 2012 at 2:27 PM, Ben Guthro <ben@guthro.net> wrote:
> 
> Hi Ben,
> 
> >> >    I see - Konrad - do you have a changeset I can look for with the
> >> > features
> >> >    Jan describes?
> >>
> >> xen-acpi-processor driver was merged to upstream Linux kernel v3.4.
> >>
> >
> > I see - so the advanced methods are not being used then

You mean with the v3.5 kernel? I would think they would be used..

> > This same kernel does work with Xen-4.0.x though. Is there an assumption in
> > the code that ties Xen-4.2 to a newer kernel?
> 
> I'm being bitten by this bug with a 3.5 kernel and Xen 4.2

Huh? How so?