From: Wei Wang <wei.wang2@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, xen-devel@lists.xensource.com,
Ian.Jackson@eu.citrix.com, Ian.Campbell@citrix.com
Subject: Re: [PATCH 1 of 6 V6] amd iommu: Add 2 hypercalls for libxc
Date: Thu, 8 Mar 2012 15:18:40 +0100 [thread overview]
Message-ID: <4F58BFC0.6070506@amd.com> (raw)
In-Reply-To: <4F58C3BD020000780007729C@nat28.tlf.novell.com>
On 03/08/2012 02:35 PM, Jan Beulich wrote:
>>>> On 08.03.12 at 14:21, Wei Wang<wei.wang2@amd.com> wrote:
>> # HG changeset patch
>> # User Wei Wang<wei.wang2@amd.com>
>> # Date 1331210211 -3600
>> # Node ID 810296995a893c1bec898a366f08520fbae755fb
>> # Parent f611200469159a960c3f0b975aa0f91ec768e29f
>> amd iommu: Add 2 hypercalls for libxc
>>
>> iommu_set_msi: used by qemu to inform hypervisor iommu vector number in
>> guest space. Hypervisor needs this vector to inject msi into guest after
>> writing PPR logs back to guest.
>>
>> iommu_bind_bdf: used by xl to bind virtual bdf to machine bdf for passthru
>> devices. IOMMU emulator receives iommu cmd from guest OS and then forwards
>> them to host iommu. Virtual device ids in guest iommu commands must be
>> converted into physical ids before sending them to real hardware.
>
> So patch 5 uses the latter one, but the former one is still dead code?
>
> Jan
>
>
Hi Jan,
The former one will be used by qemu. But Ian said we would not add new
features into qemu traditional,,So I am waiting for pci passthru patches
for upstream qemu being accepted and then I coudl send out my qemu
patch. I also had a prove-of-concept patch that was based on the old
qemu. I could rebase and resend it if necessary.
http://lists.xen.org/archives/html/xen-devel/2011-12/msg01269.html
thanks,
Wei
next prev parent reply other threads:[~2012-03-08 14:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 13:21 [PATCH 0 of 6 V6] amd iommu: support ats/gpgpu passthru on iommuv2 systems Wei Wang
2012-03-08 13:21 ` [PATCH 1 of 6 V6] amd iommu: Add 2 hypercalls for libxc Wei Wang
2012-03-08 13:35 ` Jan Beulich
2012-03-08 14:18 ` Wei Wang [this message]
2012-03-08 14:41 ` Jan Beulich
2012-03-12 11:25 ` Ian Jackson
2012-03-12 15:43 ` Wei Wang
2012-03-14 11:55 ` [Qemu-devel] [Xen-devel] " Ian Jackson
2012-03-14 11:55 ` Ian Jackson
2012-03-08 13:21 ` [PATCH 2 of 6 V6] amd iommu: call guest_iommu_set_base from hvmloader Wei Wang
2012-03-08 13:21 ` [PATCH 3 of 6 V6] hvmloader: Build IVRS table Wei Wang
2012-03-08 14:22 ` Zhang, Xiantao
2012-03-08 14:49 ` Wei Wang
2012-03-09 0:55 ` Zhang, Xiantao
2012-03-08 13:21 ` [PATCH 4 of 6 V6] libxc: add wrappers for new hypercalls Wei Wang
2012-03-08 13:21 ` [PATCH 5 of 6 V6] libxl: bind virtual bdf to physical bdf after device assignment Wei Wang
2012-03-08 13:21 ` [PATCH 6 of 6 V6] libxl: Introduce a new guest config file parameter Wei Wang
2012-03-14 14:02 ` [PATCH 0 of 6 V6] amd iommu: support ats/gpgpu passthru on iommuv2 systems Ian Jackson
2012-03-14 14:32 ` Wei Wang
2012-03-14 14:09 ` Ian Campbell
2012-03-14 14:48 ` Wei Wang
-- strict thread matches above, loose matches on Subject: below --
2012-09-26 14:46 [PATCH 1 of 6 V6] amd iommu: Add 2 hypercalls for libxc Wei Wang
2012-09-27 8:25 ` Jan Beulich
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=4F58BFC0.6070506@amd.com \
--to=wei.wang2@amd.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--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 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.