From: Anthony PERARD <anthony.perard@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Xen Devel <xen-devel@lists.xensource.com>,
Shan Haitao <haitao.shan@intel.com>,
QEMU-devel <qemu-devel@nongnu.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH V6 10/11] Introduce Xen PCI Passthrough, MSI (3/3)
Date: Tue, 14 Feb 2012 13:46:55 +0000 [thread overview]
Message-ID: <CAJJyHj+TKcE6241itt9ECeraEOxSPvFVCZwAZABmc6x0ROADow@mail.gmail.com> (raw)
In-Reply-To: <4F3A6C010200007800072E67@nat28.tlf.novell.com>
On Tue, Feb 14, 2012 at 13:13, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 13.02.12 at 13:20, Anthony PERARD <anthony.perard@citrix.com> wrote:
>> From: Jiang Yunhong <yunhong.jiang@intel.com>
>>
>> A more complete history can be found here:
>> git://xenbits.xensource.com/qemu-xen-unstable.git
>
> This needs to be updated to include the changes in
> http://xenbits.xen.org/gitweb/?p=qemu-xen-unstable.git;a=commitdiff;h=bb36d632e4cabf47882adff07a45c6702c4a5b30
> (and hopefully the broken function that got fixed in
> http://xenbits.xen.org/gitweb/?p=qemu-xen-unstable.git;a=commitdiff;h=8cc8a3651c9c5bc2d0086d12f4b870fc525b9387
> didn't even make it into this patch set).
For the first patch/link, the 'volatile' variable should already be in
the patch (without a separate patch :( ). For the second, yes,
unregister_iomem is done by other functions in QEMU.
> In particular it must be avoided
> to map the MSI-X table with PROT_WRITE, and the respective MMIO
> range should not get assigned to the guest at all.
I will check that.
Regards,
--
Anthony PERARD
next prev parent reply other threads:[~2012-02-14 13:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 12:20 [Qemu-devel] [PATCH V6 00/11] Xen PCI Passthrough Anthony PERARD
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 01/11] pci_ids: Add INTEL_82599_VF id Anthony PERARD
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 02/11] pci_regs: Fix value of PCI_EXP_TYPE_RC_EC Anthony PERARD
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 03/11] pci_regs: Add PCI_EXP_TYPE_PCIE_BRIDGE Anthony PERARD
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 04/11] configure: Introduce --enable-xen-pci-passthrough Anthony PERARD
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 05/11] Introduce HostPCIDevice to access a pci device on the host Anthony PERARD
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 06/11] pci.c: Add pci_check_bar_overlap Anthony PERARD
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 07/11] Introduce Xen PCI Passthrough, qdevice (1/3) Anthony PERARD
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 08/11] Introduce Xen PCI Passthrough, PCI config space helpers (2/3) Anthony PERARD
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 09/11] Introduce apic-msidef.h Anthony PERARD
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 10/11] Introduce Xen PCI Passthrough, MSI (3/3) Anthony PERARD
2012-02-14 13:13 ` [Qemu-devel] [Xen-devel] " Jan Beulich
2012-02-14 13:46 ` Anthony PERARD [this message]
2012-02-14 14:00 ` Jan Beulich
2012-02-13 12:20 ` [Qemu-devel] [PATCH V6 11/11] pci: Do not check if a bus exist in pci_parse_devaddr Anthony PERARD
2012-02-13 12:53 ` Michael S. Tsirkin
2012-02-13 15:24 ` Anthony PERARD
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=CAJJyHj+TKcE6241itt9ECeraEOxSPvFVCZwAZABmc6x0ROADow@mail.gmail.com \
--to=anthony.perard@citrix.com \
--cc=JBeulich@suse.com \
--cc=haitao.shan@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).