xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ben Guthro <ben@guthro.net>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <juergen.gross@ts.fujitsu.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	keir@xen.org, xen-devel <xen-devel@lists.xen.org>
Subject: Re: dump with xen-unstable & linux 3.2.17
Date: Thu, 31 May 2012 12:18:42 -0400	[thread overview]
Message-ID: <CAOvdn6UdFCZXFVS5ZBpAg9wxVb1ifLFuFuvMuj+T4OEJyy23uA@mail.gmail.com> (raw)
In-Reply-To: <4FC7B32F0200007800087786@nat28.tlf.novell.com>

On Thu, May 31, 2012 at 12:06 PM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 31.05.12 at 17:52, Ben Guthro <ben@guthro.net> wrote:
>> 1. The changeset mentioned below needed to be reverted, as it was
>> removing the CPUS at suspend time.
>
> I assume you refer to the one line change, not the full c/s?
> Juergen would have to tell us whether reverting that would
> break something else.

I reverted the whole c/s - but I think the one line change would be sufficient.

>
>> 2. The linux xen watchdog driver (drivers/watchdog/xen_wdt.c) seems to
>> be enabling itsself on resume, even if you tell it not to.
>> I worked around this by just turning off watchdogs in my kernel
>> config...because I wasn't using them anyhow.
>
> That was a problem up to 3.3, but was fixed in 3.4 afaict. What
> kernel version did you see this with?
>

3.2.17 + some of konrad's branches
...so that makes sense.


> Jan
>
>> On Fri, May 25, 2012 at 9:20 AM, Ben Guthro <ben@guthro.net> wrote:
>>> Changed parts:
>>>
>>> diff --git a/xen/common/schedule.c b/xen/common/schedule.c
>>> index 0854f55..95cb2b4 100644
>>> --- a/xen/common/schedule.c
>>> +++ b/xen/common/schedule.c
>>> @@ -543,7 +543,7 @@ int cpu_disable_scheduler(unsigned int cpu)
>>>     int    ret = 0;
>>>
>>>     c = per_cpu(cpupool, cpu);
>>> -    if ( (c == NULL) || (system_state == SYS_STATE_suspend) )
>>> +    if ( (c == NULL) )
>>>         return ret;
>>>
>>>     for_each_domain_in_cpupool ( d, c )
>
>

  reply	other threads:[~2012-05-31 16:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 21:20 dump with xen-unstable & linux 3.2.17 Ben Guthro
2012-05-21 14:55 ` Jan Beulich
2012-05-21 19:12   ` Ben Guthro
2012-05-21 19:49     ` Ben Guthro
2012-05-22 15:38       ` Ben Guthro
2012-05-22 16:08         ` Jan Beulich
2012-05-22 16:21           ` Ben Guthro
2012-05-22 17:34             ` Konrad Rzeszutek Wilk
2012-05-22 17:55               ` Ben Guthro
2012-05-22 18:00                 ` Konrad Rzeszutek Wilk
2012-05-22 18:26                   ` Ben Guthro
2012-05-22 21:00                     ` Ben Guthro
2012-05-23  9:39                       ` Jan Beulich
2012-05-23 11:00                         ` Juergen Gross
2012-05-25 13:20                           ` Ben Guthro
2012-05-31 15:52                             ` Ben Guthro
2012-05-31 16:06                               ` Jan Beulich
2012-05-31 16:18                                 ` Ben Guthro [this message]
2012-06-01  6:54                                 ` Dietmar Hahn

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=CAOvdn6UdFCZXFVS5ZBpAg9wxVb1ifLFuFuvMuj+T4OEJyy23uA@mail.gmail.com \
    --to=ben@guthro.net \
    --cc=JBeulich@suse.com \
    --cc=juergen.gross@ts.fujitsu.com \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xen.org \
    /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).