xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "george.dunlap@eu.citrix.com" <george.dunlap@eu.citrix.com>,
	"Xu, YongweiX" <yongweix.xu@intel.com>,
	"Liu, SongtaoX" <songtaox.liu@intel.com>,
	"Tian, Yongxue" <yongxue.tian@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: test report for Xen 4.3 RC1
Date: Mon, 17 Jun 2013 16:36:34 -0400	[thread overview]
Message-ID: <20130617203634.GA2914@phenom.dumpdata.com> (raw)
In-Reply-To: <20130617203539.GA2887@phenom.dumpdata.com>

On Mon, Jun 17, 2013 at 04:35:39PM -0400, Konrad Rzeszutek Wilk wrote:
> > I just double checked on my AMD machines with v3.10-rc5 with
> > these extra patches:
> > 
> > ebe2886 x86/cpa: Use pte_attrs instead of pte_flags on CPA/set_p.._wb/wc operations.
> > 7c4ae96 Revert "xen/pat: Disable PAT support for now."
> > 729c6ec Revert "xen/pat: Disable PAT using pat_enabled value."
> > bd4fd16 microcode_xen: Add support for AMD family >= 15h
> > 6271c21 x86/microcode: check proper return code.
> > b9a48c8 xen: add CPU microcode update driver
> > c62566c cpu: make sure that cpu/online file created before KOBJ_ADD is emitted
> > 0790542 cpu: fix "crash_notes" and "crash_notes_size" leaks in register_cpu()
> > f90099b xen / ACPI / sleep: Register an acpi_suspend_lowlevel callback.
> > 29ca6e9 x86 / ACPI / sleep: Provide registration for acpi_suspend_lowlevel.
> > 
> > and it worked. Let me recompile a kernel without most of them to doublecheck
> > whether those patches are making the ACPI S3 suspend/resume working.
> 
> Still works. I removed all but:
> 
>  c62566c cpu: make sure that cpu/online file created before KOBJ_ADD is emitted
>  0790542 cpu: fix "crash_notes" and "crash_notes_size" leaks in register_cpu()
> 
> on top of 3.10-rc6 and the suspend/resume on the host works.

Correction. This is v3.10-rc6 + Rafaels' linux-next branch which had:

 f90099b xen / ACPI / sleep: Register an acpi_suspend_lowlevel callback.
 29ca6e9 x86 / ACPI / sleep: Provide registration for acpi_suspend_lowlevel.

  reply	other threads:[~2013-06-17 20:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16  4:10 test report for Xen 4.3 RC1 Ren, Yongjie
2013-06-17 14:23 ` Konrad Rzeszutek Wilk
2013-06-17 20:35   ` Konrad Rzeszutek Wilk
2013-06-17 20:36     ` Konrad Rzeszutek Wilk [this message]
2013-06-20  2:53   ` Ren, Yongjie
2013-06-21 18:17     ` Konrad Rzeszutek Wilk
2013-07-02  8:09       ` Ren, Yongjie
2013-07-02 13:36         ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2013-06-05 10:14 Ren, Yongjie
2013-06-05 14:50 ` Konrad Rzeszutek Wilk
2013-06-04 15:59 Ren, Yongjie
2013-06-04 16:35 ` Konrad Rzeszutek Wilk
2013-05-27  3:49 Ren, Yongjie
2013-05-28 15:15 ` Konrad Rzeszutek Wilk
2013-05-28 15:21   ` Konrad Rzeszutek Wilk
2013-05-28 15:24     ` George Dunlap
2013-11-11 10:22       ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130617203634.GA2914@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=songtaox.liu@intel.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yongjie.ren@intel.com \
    --cc=yongweix.xu@intel.com \
    --cc=yongxue.tian@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).