From: "Glauber Costa" <glommer@gmail.com>
To: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Avi Kivity <avi@qumranet.com>,
balrogg@gmail.com, paul@codesourcery.com
Subject: Re: [Qemu-devel] [4261] Errors while registering ioports are not fatal (Glauber Costa).
Date: Sat, 26 Apr 2008 17:39:48 -0300 [thread overview]
Message-ID: <5d6222a80804261339y279f5364k6f7cefcd540d6be4@mail.gmail.com> (raw)
In-Reply-To: <fb249edb0804261257o4849aa57n823d3e51a1824d9b@mail.gmail.com>
On Sat, Apr 26, 2008 at 4:57 PM, andrzej zaborowski <balrogg@gmail.com> 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 :(
Yes, reverting is probably better. I must confess I was surprised to
see this going in alone.
It is highly kvm dependant, because it was written in the context of
pci passtrough. In the mails I sent,
qemu-devel copied, I explicitly said it was an RFC. Reason?
As aliguori said, the callers must all be fixed, and it was not
something I was willing to do if the patches were not to be accepted.
Unfortunately the patches got no attention at the time, but I'm happy
to see the it happening now.
As for being dependant of kvm code, the patches were written in the
context of kvm pci-passthrough. And that´s why.
> You might not want qemu to quit a running session if it's possible to
> continue running, even if there turns out to be a serious bug.
>
> Regards
>
>
>
--
Glauber Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
next prev parent reply other threads:[~2008-04-26 20:40 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 [this message]
2008-04-26 20:43 ` Anthony Liguori
2008-04-26 21:18 ` andrzej zaborowski
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=5d6222a80804261339y279f5364k6f7cefcd540d6be4@mail.gmail.com \
--to=glommer@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=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).