From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org, wei.liu2@citrix.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH 1/2] libxl: Wait until QEMU removed the device before tearing it down
Date: Fri, 14 Nov 2014 11:37:17 -0500 [thread overview]
Message-ID: <54662FBD.1010605@oracle.com> (raw)
In-Reply-To: <21606.11847.373254.124439@mariner.uk.xensource.com>
On 11/14/2014 11:31 AM, Ian Jackson wrote:
> Boris Ostrovsky writes ("Re: [PATCH 1/2] libxl: Wait until QEMU removed the device before tearing it down"):
>
>> On 11/14/2014 11:01 AM, Ian Jackson wrote:
>>> What call to xc_physdev_unmap_pirq ? I see one in the PV path.
>> At the skip1 label.
> `goto skip1' only appears in the PV path AFAICT.
>
Right, this is all about PV code path.
-boris
next prev parent reply other threads:[~2014-11-14 16:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 23:16 [PATCH 0/2] Two fixes for libxl's PCI detach operation Boris Ostrovsky
2014-11-10 23:16 ` [PATCH 1/2] libxl: Wait until QEMU removed the device before tearing it down Boris Ostrovsky
2014-11-14 14:41 ` Ian Jackson
2014-11-14 15:30 ` Boris Ostrovsky
2014-11-14 16:01 ` Ian Jackson
2014-11-14 16:24 ` Boris Ostrovsky
2014-11-14 16:31 ` Ian Jackson
2014-11-14 16:37 ` Boris Ostrovsky [this message]
2014-11-14 16:36 ` Ian Jackson
2014-11-14 16:58 ` Boris Ostrovsky
2014-11-14 17:45 ` Sander Eikelenboom
2014-11-14 18:07 ` Ian Jackson
2014-11-14 19:24 ` Sander Eikelenboom
2014-11-14 21:09 ` Boris Ostrovsky
2014-11-14 21:20 ` Sander Eikelenboom
2014-11-14 21:38 ` Boris Ostrovsky
2014-11-14 21:50 ` Sander Eikelenboom
2014-11-14 16:19 ` Ian Jackson
2014-11-14 17:09 ` Boris Ostrovsky
2014-11-14 17:33 ` Ian Jackson
2014-11-10 23:16 ` [PATCH 2/2] libxl: Simplify cleanup in do_pci_remove() Boris Ostrovsky
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=54662FBD.1010605@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.