qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [4261] Errors while registering ioports are not fatal (Glauber Costa).
Date: Sat, 26 Apr 2008 23:18:08 +0200	[thread overview]
Message-ID: <fb249edb0804261418h33d1bb23jea13da47c0511070@mail.gmail.com> (raw)
In-Reply-To: <481393DB.2030101@codemonkey.ws>

On 26/04/2008, Anthony Liguori <anthony@codemonkey.ws> wrote:
> andrzej zaborowski wrote:
>
> > On 26/04/2008, Paul Brook <paul@codesourcery.com> wrote:
> >
> >
> > > On Saturday 26 April 2008, Andrzej Zaborowski wrote:
> > >  > Revision: 4261
> > >  >
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4261
> > >  > Author:   balrog
> > >  > Date:     2008-04-26 16:04:29 +0000 (Sat, 26 Apr 2008)
> > >  >
> > >  > Log Message:
> > >  > -----------
> > >  > Errors while registering ioports are not fatal (Glauber Costa).
> > >
> > >  Why shouldn't they be fatal? How can this be anything other than a
> serious bug
> > >  in the device emulation?
> > >
> > >
> >
> > This change is perhaps not useful, it would be useful with hot-plugged
> > / proxied pci devices.  I think they are desirable features. But the
> > patchsets submitted turn out to depend on too much kvm code to ever
> > work alone so I might just as well revert :(
> >
> >
>
>  It's not at all kvm specific.  Even if QEMU never merged PCI hotplug
> (although I see no reason why not to), it's the right direction to move
> toward.

Right, what I mean is I missed the fact that there had been more
changes which didn't go into qemu on which Marcelo Tosatti's patches
depended and it seems like this included rather significant changes.

Regards

      reply	other threads:[~2008-04-26 21:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26 16:04 [Qemu-devel] [4261] Errors while registering ioports are not fatal (Glauber Costa) Andrzej Zaborowski
2008-04-26 19:26 ` Paul Brook
2008-04-26 19:36   ` Anthony Liguori
2008-04-26 19:57     ` Paul Brook
2008-04-26 20:33       ` Anthony Liguori
2008-04-26 20:45       ` Glauber Costa
2008-04-26 19:57   ` andrzej zaborowski
2008-04-26 20:08     ` Paul Brook
2008-04-26 20:38       ` Anthony Liguori
2008-04-26 20:54         ` Paul Brook
2008-04-26 21:09           ` Anthony Liguori
2008-04-26 21:29             ` Paul Brook
2008-04-26 20:39     ` Glauber Costa
2008-04-26 20:43     ` Anthony Liguori
2008-04-26 21:18       ` andrzej zaborowski [this message]

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=fb249edb0804261418h33d1bb23jea13da47c0511070@mail.gmail.com \
    --to=balrogg@gmail.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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).