From: Avi Kivity <avi@qumranet.com>
To: Glauber de Oliveira Costa <gcosta@redhat.com>
Cc: kvm-devel@lists.sourceforge.net, mtosatti@redhat.com,
qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: Re: [PATCH 0/3] Qemu crashes with pci passthrough
Date: Fri, 18 Apr 2008 19:27:07 +0300 [thread overview]
Message-ID: <4808CBDB.3030206@qumranet.com> (raw)
In-Reply-To: <12084217752458-git-send-email-gcosta@redhat.com>
Glauber de Oliveira Costa wrote:
> Hi,
>
> I've got some qemu crashes while trying to passthrough an ide device
> to a kvm guest. After some investigation, it turned out that
> register_ioport_{read/write} will abort on errors instead of returning
> a meaningful error.
>
> However, even if we do return an error, the asynchronous nature of pci
> config space mapping updates makes it a little bit hard to treat.
>
> This series of patches basically treats errors in the mapping functions in
> the pci layer. If anything goes wrong, we unregister the pci device, unmapping
> any mappings that happened to be sucessfull already.
>
> After these patches are applied, a lot of warnings appears. And, you know,
> everytime there is a warning, god kills a kitten. But I'm not planning on
> touching the other pieces of qemu code for this until we set up (or not) in
> this solution
>
> Comments are very welcome, specially from qemu folks (since it is a bit invasive)
>
>
Have you considered, instead of rolling back the changes you already
made before the failure, to have a function which checks if an ioport
registration will be successful? This may simplify the code.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Glauber de Oliveira Costa <gcosta@redhat.com>
Cc: kvm-devel@lists.sourceforge.net, mtosatti@redhat.com,
qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: [Qemu-devel] Re: [kvm-devel] [PATCH 0/3] Qemu crashes with pci passthrough
Date: Fri, 18 Apr 2008 19:27:07 +0300 [thread overview]
Message-ID: <4808CBDB.3030206@qumranet.com> (raw)
In-Reply-To: <12084217752458-git-send-email-gcosta@redhat.com>
Glauber de Oliveira Costa wrote:
> Hi,
>
> I've got some qemu crashes while trying to passthrough an ide device
> to a kvm guest. After some investigation, it turned out that
> register_ioport_{read/write} will abort on errors instead of returning
> a meaningful error.
>
> However, even if we do return an error, the asynchronous nature of pci
> config space mapping updates makes it a little bit hard to treat.
>
> This series of patches basically treats errors in the mapping functions in
> the pci layer. If anything goes wrong, we unregister the pci device, unmapping
> any mappings that happened to be sucessfull already.
>
> After these patches are applied, a lot of warnings appears. And, you know,
> everytime there is a warning, god kills a kitten. But I'm not planning on
> touching the other pieces of qemu code for this until we set up (or not) in
> this solution
>
> Comments are very welcome, specially from qemu folks (since it is a bit invasive)
>
>
Have you considered, instead of rolling back the changes you already
made before the failure, to have a function which checks if an ioport
registration will be successful? This may simplify the code.
--
Any sufficiently difficult bug is indistinguishable from a feature.
next prev parent reply other threads:[~2008-04-18 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 8:42 [PATCH 0/3] Qemu crashes with pci passthrough Glauber de Oliveira Costa
2008-04-17 8:42 ` [Qemu-devel] " Glauber de Oliveira Costa
2008-04-17 8:42 ` [PATCH 1/3] don't exit on errors while registering ioports Glauber de Oliveira Costa
2008-04-17 8:42 ` [Qemu-devel] " Glauber de Oliveira Costa
2008-04-17 8:42 ` [PATCH 2/3] map regions as registered Glauber de Oliveira Costa
2008-04-17 8:42 ` [Qemu-devel] " Glauber de Oliveira Costa
2008-04-17 8:42 ` [PATCH 3/3] propagate errors from ioport registering up to pci level Glauber de Oliveira Costa
2008-04-17 8:42 ` [Qemu-devel] " Glauber de Oliveira Costa
2008-04-18 16:27 ` Avi Kivity [this message]
2008-04-18 16:27 ` [Qemu-devel] Re: [kvm-devel] [PATCH 0/3] Qemu crashes with pci passthrough Avi Kivity
2008-04-19 21:11 ` [Qemu-devel] " Glauber Costa
2008-04-19 21:11 ` [Qemu-devel] Re: [kvm-devel] " Glauber Costa
2008-04-24 13:25 ` [Qemu-devel] " Glauber Costa
2008-04-24 13:25 ` [Qemu-devel] Re: [kvm-devel] " Glauber Costa
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=4808CBDB.3030206@qumranet.com \
--to=avi@qumranet.com \
--cc=aurelien@aurel32.net \
--cc=gcosta@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=mtosatti@redhat.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 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.