From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Prasad Joshi <prasadjoshi124@gmail.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: A query on frame buffers
Date: Tue, 11 Jan 2011 18:17:56 +0000 [thread overview]
Message-ID: <20110111181756.GI14017@dumpdata.com> (raw)
In-Reply-To: <AANLkTimJ=WwnCtUNzQcxwHgHZp_bqQwt8YfiXm=g0gv-@mail.gmail.com>
> > What motherboard is this?
>
> ASUS M4A89TD Pro/USB3, it is mentioned on the link
> http://wiki.xensource.com/xenwiki/VTdHowTo
I am not sure how the implementation of the IOMMU
in the Xen hypervisor is different from the Linux implementation.
Usually it is lock-step, but it might be different.
Also, Xen's QEMU has different mechanism for handling PCI passthrough
so ...
Lots of variables to figure out why it does not work for you.
It might make sense to start first with a working case and from there
start switching over to KVM.
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Prasad Joshi <prasadjoshi124@gmail.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: A query on frame buffers
Date: Tue, 11 Jan 2011 13:17:56 -0500 [thread overview]
Message-ID: <20110111181756.GI14017@dumpdata.com> (raw)
In-Reply-To: <AANLkTimJ=WwnCtUNzQcxwHgHZp_bqQwt8YfiXm=g0gv-@mail.gmail.com>
> > What motherboard is this?
>
> ASUS M4A89TD Pro/USB3, it is mentioned on the link
> http://wiki.xensource.com/xenwiki/VTdHowTo
I am not sure how the implementation of the IOMMU
in the Xen hypervisor is different from the Linux implementation.
Usually it is lock-step, but it might be different.
Also, Xen's QEMU has different mechanism for handling PCI passthrough
so ...
Lots of variables to figure out why it does not work for you.
It might make sense to start first with a working case and from there
start switching over to KVM.
next prev parent reply other threads:[~2011-01-11 18:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 4:51 A query on frame buffers Prasad Joshi
2010-12-27 15:30 ` Konrad Rzeszutek Wilk
2011-01-07 2:42 ` Prasad Joshi
2011-01-07 9:00 ` Michel Dänzer
2011-01-07 9:00 ` Michel Dänzer
2011-01-07 16:58 ` Konrad Rzeszutek Wilk
2011-01-07 16:58 ` Konrad Rzeszutek Wilk
2011-01-07 17:47 ` Prasad Joshi
2011-01-07 17:47 ` Prasad Joshi
2011-01-07 19:24 ` Konrad Rzeszutek Wilk
2011-01-07 19:24 ` Konrad Rzeszutek Wilk
2011-01-08 2:12 ` Prasad Joshi
2011-01-08 2:12 ` Prasad Joshi
2011-01-10 12:31 ` Prasad Joshi
2011-01-10 12:31 ` Prasad Joshi
2011-01-10 18:17 ` Konrad Rzeszutek Wilk
2011-01-10 18:17 ` Konrad Rzeszutek Wilk
2011-01-10 19:57 ` Prasad Joshi
2011-01-10 19:57 ` Prasad Joshi
2011-01-10 20:24 ` Konrad Rzeszutek Wilk
2011-01-10 20:24 ` Konrad Rzeszutek Wilk
2011-01-11 16:58 ` Prasad Joshi
2011-01-11 17:10 ` Alex Deucher
2011-01-11 17:10 ` Alex Deucher
2011-01-11 18:17 ` Konrad Rzeszutek Wilk [this message]
2011-01-11 18:17 ` Konrad Rzeszutek Wilk
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=20110111181756.GI14017@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=prasadjoshi124@gmail.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.