> -Original Message-
> From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> Sent: Tuesday, March 31, 2015 7:56 AM
> To: Wu, Feng
> Cc: h...@zytor.com; t...@linutronix.de; mi...@redhat.com; x...@kernel.org;
> g...@kernel.org; pbonz...@redhat.com; dw...@infradead.org;
> j...@8bytes.org; ale
Hi Joerg,
Thank you so much, I'll try asking BIOS engineer to deliver us a new
BIOS for testing.
Best regards,
AceLan Kao.
2015-03-31 0:09 GMT+08:00 Joerg Roedel :
> Hi AceLan,
>
> On Fri, Mar 27, 2015 at 08:48:22AM +0800, AceLan Kao wrote:
>> Very thanks for your time.
>> This is the log bootin
On Mon, Mar 30, 2015 at 04:46:55AM +, Wu, Feng wrote:
>
>
> > -Original Message-
> > From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> > Sent: Saturday, March 28, 2015 3:30 AM
> > To: Wu, Feng
> > Cc: h...@zytor.com; t...@linutronix.de; mi...@redhat.com; x...@kernel.org;
> > g...@k
Hi Joerg,
On Thu, Mar 26, 2015 at 12:43:03PM +, Joerg Roedel wrote:
> Changes v1-v2:
>
> * Rebased to v4.0-rc5
> * Converted domain-types to a bit-field
>
> Hi,
>
> here is patch-set to replace the existing domain_init and
> domain_destroy iommu-ops with the new domain_alloc and
Hi AceLan,
On Fri, Mar 27, 2015 at 08:48:22AM +0800, AceLan Kao wrote:
> Very thanks for your time.
> This is the log booting with kernel 4.0rc5 without fglrx loaded.
Thanks, it scheds some light on the issue. See below.
> [0.080177] AMD-Vi: device: 00:00.2 cap: 0040 seg: 0 flags: b8 info 00
Hi Jerome,
On Thu, Mar 26, 2015 at 01:58:58PM -0400, Jerome Glisse wrote:
> Of course if dev.archdata.dma_ops is pointing to nommu_dma_ops then every
> things is fine, but here i am wondering for the case where the ops are
> actualy amd_iommu_dma_ops. In the first place ie at iommu initialization
