All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] pci_bridge: fix abort due to memory region API violation
Date: Mon, 29 Oct 2012 17:57:01 +0200	[thread overview]
Message-ID: <508EA74D.1040603@redhat.com> (raw)
In-Reply-To: <1351525013-9829-1-git-send-email-mdroth@linux.vnet.ibm.com>

On 10/29/2012 05:36 PM, Michael Roth wrote:
> 2be0e25f added an assertion that memory_region_destroy() is not called
> during a transaction. pci_bridge_update_mappings() wants to do this so
> that it can remove existing subregions and add new ones in their
> place as an atomic operation.
> 
> Work around this by storing away the old subregions and destroying them
> after the transaction is complete.
> 

An equivalent patch was already posted, see
http://thread.gmane.org/gmane.comp.emulators.qemu/177418/focus=177853.


-- 
error compiling committee.c: too many arguments to function

      reply	other threads:[~2012-10-29 15:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 15:36 [Qemu-devel] [PATCH] pci_bridge: fix abort due to memory region API violation Michael Roth
2012-10-29 15:57 ` Avi Kivity [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=508EA74D.1040603@redhat.com \
    --to=avi@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@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.