From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Xuquan (Quan Xu)" <xuquan8@huawei.com>,
Venu Busireddy <venu.busireddy@oracle.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
StefanoStabellini <sstabellini@kernel.org>,
"George.Dunlap@eu.citrix.com" <George.Dunlap@eu.citrix.com>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Fanhenglong <fanhenglong@huawei.com>,
Jan Beulich <JBeulich@suse.com>,
"anthony.perard@citrix.com" <anthony.perard@citrix.com>
Subject: Re: question: xen/qemu - mmio mapping issues for device pass-through
Date: Tue, 21 Mar 2017 09:18:46 -0400 [thread overview]
Message-ID: <20170321131846.GB19381@char.us.oracle.com> (raw)
In-Reply-To: <E0A769A898ADB6449596C41F51EF62C6AF06AA@SZXEMI506-MBX.china.huawei.com>
. snip..
> support to pass-through large bar (pci-e bar > 4G) device..
Yes it does work.
>
> > I was assuming large BAR handling to work so far
> >(Konrad had done some adjustments there quite a while ago, from all I recall).
> >
>
>
> _iirc_ what Konrad mentioned was using qemu-trad..
Yes but we also did tests on qemu-xen and it worked. CCing Venu.
Venu, does passing in large BARs work with qemu-xen (aka 'xl')?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-21 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 13:55 question: xen/qemu - mmio mapping issues for device pass-through Xuquan (Quan Xu)
2017-03-16 14:05 ` Jan Beulich
2017-03-16 14:21 ` Xuquan (Quan Xu)
2017-03-16 15:31 ` Jan Beulich
2017-03-20 1:58 ` Xuquan (Quan Xu)
2017-03-20 7:34 ` Jan Beulich
2017-03-21 1:53 ` Xuquan (Quan Xu)
2017-03-21 7:38 ` Jan Beulich
2017-03-21 13:18 ` Konrad Rzeszutek Wilk [this message]
2017-03-21 13:22 ` Venu Busireddy
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=20170321131846.GB19381@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=fanhenglong@huawei.com \
--cc=ian.jackson@eu.citrix.com \
--cc=kevin.tian@intel.com \
--cc=sstabellini@kernel.org \
--cc=venu.busireddy@oracle.com \
--cc=xen-devel@lists.xen.org \
--cc=xuquan8@huawei.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).