All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Steven Hand <Steven.Hand@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Unstableness in grant table block drivers
Date: Wed, 13 Apr 2005 20:46:50 -0500	[thread overview]
Message-ID: <425DCB8A.5050405@us.ibm.com> (raw)
In-Reply-To: <E1DLt2A-0002y2-00@mta1.cl.cam.ac.uk>

Steven Hand wrote:

>Have you made any progress in further identifying or narrowing down 
>these bugs? Detailed bug reports or, better, patches, are always more
>useful than general reports of issues. 
>  
>
This is where having a bugzilla would really help out.  At this stage, I 
don't know that much but enough that I could enter something in 
bugzilla.  As I learn more, we could add more detail until there was 
enough that someone (or I) could actually fix it.

>We've not seen any bugs ourselves but obviously if it's biting you 
>regularly then may be worth while disabling in your config. I'm 
>loathe to disable it by default in the general config since this 
>won't help us uncover and fix whatever bugs are present. 
>  
>
That's why I suggested just sending a note to the list.  Bugs need to be 
found and that's what xen-unstable should be for.  I'm happy to leave it 
enabled by default but wanted to let the rest of the list know that if 
they run into stability problems that might be a good place to start 
looking.

Regards,
Anthony Liguori

  reply	other threads:[~2005-04-14  1:46 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <aliguori@us.ibm.com>
2005-04-14  1:18 ` Unstableness in grant table block drivers Anthony Liguori
2005-04-14  1:20   ` Steven Hand
2005-04-14  1:46     ` Anthony Liguori [this message]
2005-04-14  1:53     ` Kip Macy
2005-04-14  2:27       ` Anthony Liguori
2005-04-14  2:55         ` Kip Macy
2005-04-16  1:32 Ian Pratt
2005-04-16 15:39 ` Ryan Harper
2005-04-18 16:38   ` Christopher Clark
2005-04-18 16:45     ` Ryan Harper
2005-04-18 20:51     ` Ryan Harper
2005-04-20 18:52       ` Christopher Clark
2005-04-20 19:37         ` Ryan Harper
2005-04-22 18:57           ` Ryan Harper
2005-04-22 19:06             ` Anthony Liguori
2005-05-12  1:50         ` Xiaofeng Ling
  -- strict thread matches above, loose matches on Subject: below --
2005-04-15 22:30 Ian Pratt
2005-04-16  1:18 ` Christopher Clark
2005-04-16  1:32   ` Christopher Clark
2005-04-16  3:03     ` David Hopwood
2005-04-14 10:24 Ian Pratt
2005-04-14 10:34 ` Ge van Geldorp
     [not found] <E1DLu58-0005lx-KR@host-192-168-0-1-bcn-london>
2005-04-14 10:17 ` Ge van Geldorp
2005-04-14  1:16 Ian Pratt
2005-04-14  1:43 ` Anthony Liguori
2005-04-14  2:04   ` Christopher Clark
2005-04-14  2:17     ` Kip Macy
2005-04-14  2:25     ` Anthony Liguori
2005-04-14 15:00     ` Ryan Harper
2005-04-14 16:34       ` Christopher Clark
2005-04-14 17:28         ` Ryan Harper
2005-04-15 18:45           ` Christopher Clark
2005-04-15 21:14             ` Ryan Harper
2005-04-15 21:32               ` Kip Macy
2005-04-15 21:41                 ` Ryan Harper
2005-04-15 21:46                   ` Kip Macy
2005-04-15 21:50                     ` Ryan Harper
2005-04-15 21:52                 ` Ryan Harper
2005-04-15 22:07                   ` Christopher Clark
2005-04-15 22:08                     ` Ryan Harper

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=425DCB8A.5050405@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=Steven.Hand@cl.cam.ac.uk \
    --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.