All of lore.kernel.org
 help / color / mirror / Atom feed
From: Murillo Fernandes Bernardes <mfb@br.ibm.com>
To: Stefan Berger <stefanb@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Fix device removal on net and block frontend drivers
Date: Mon, 21 Nov 2005 14:33:31 -0200	[thread overview]
Message-ID: <200511211433.31356.mfb@br.ibm.com> (raw)
In-Reply-To: <OFF62890E7.04A4E81C-ON852570C0.00583310-852570C0.00589280@us.ibm.com>

On Monday 21 November 2005 14:07, Stefan Berger wrote:
> xen-devel-bounces@lists.xensource.com wrote on 11/21/2005 10:43:01 AM:
> > Frontend devices are not being unregistered when in closed state. The
> > following patch fix that.
> >
> > Fix bug #420.
> >
> > Makes "05_attach_and_dettach_device_repeatedly_pos" and
> > "09_attach_and_dettach_device_check_data_pos" tests pass.
>
> Did you test this with suspending / resuming a dom U? The reason I am
> asking is that when suspending the driver immediately gets into state
> 'Closed' and when resuming into state 'Connected',  but now your device is
> unregistered.

No, I did not test suspend/resume.

I really don't see why it should get into Closed on suspend, but anyway, is 
this really hapenning? I could not find any switch to Closed into suspend's 
code, neither on resume.

How to test suspend/resume on a domU? It does not have /sys/power/state 
neither /proc/sleep.

-- 
Murillo Fernandes Bernardes
IBM Linux Technology Center

  reply	other threads:[~2005-11-21 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 15:43 [PATCH] Fix device removal on net and block frontend drivers Murillo Fernandes Bernardes
2005-11-21 16:07 ` Stefan Berger
2005-11-21 16:33   ` Murillo Fernandes Bernardes [this message]
2005-11-21 16:49     ` Stefan Berger
2005-11-21 18:31       ` Ewan Mellor
2005-11-21 20:02         ` Stefan Berger
2005-11-21 21:11         ` Murillo Fernandes Bernardes
2005-11-21 17:48 ` Adam Heath
2005-11-21 18:40   ` Ewan Mellor
2005-11-21 21:30     ` Adam Heath

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=200511211433.31356.mfb@br.ibm.com \
    --to=mfb@br.ibm.com \
    --cc=stefanb@us.ibm.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.