From: Jiri Kosina <jikos@kernel.org>
To: "Shah, Nehal-bakulchandra" <nbshah@amd.com>
Cc: Kurt Garloff <kurt@garloff.de>, Joerg Roedel <joro@8bytes.org>,
LKML <linux-kernel@vger.kernel.org>,
"Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@amd.com>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
"Singh, Sandeep" <Sandeep.Singh@amd.com>
Subject: Re: IOMMU vs Ryzen embedded EMMC controller
Date: Wed, 9 Oct 2019 21:25:00 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1910092124260.13160@cbobk.fhfr.pm> (raw)
In-Reply-To: <63913cd8-a0c5-61e3-2f52-139bade01afc@amd.com>
On Fri, 27 Sep 2019, Shah, Nehal-bakulchandra wrote:
> >>> Do you have BAR memory allocation failures in dmesg with IOMMU on?
> >
> > No. The device is *not* treated as PCI device and I still think that
> > this is the source of the evil.
> >
> >>> Actually, sharing both working and non-working dmesg, as well as
> >>> /proc/iomem contents, would be helpful.
> >> Yes, can you please grab dmesg from a boot with iommu enabled and add
> >> 'amd_iommu_dump' to the kernel command line? That should give some
> >> hints on what is going on.
> >
> > For now I attach a dmesg and iomem from the boot with IOMMU enabled.
> > Nothing much interesting without IOMMU, sdhci-acpi there just works --
> > let me know if you still want me to send the kernel msg.
> >
> > Thanks for looking into this!
> >
>
> I have added Suravee from AMD in the mail loop. He works on IOMMU part.
> As per my understanding, it needs a patch in IOMMU driver for adding
> support of EMMC. Note that on Ryzen platform we have EMMC 5.0 as ACPI
> device.
Friendly ping ... any news here?
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2019-10-09 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <643f99a4-4613-50af-57e4-5ea6ac975314@garloff.de>
2019-09-21 6:58 ` IOMMU vs Ryzen embedded EMMC controller Kurt Garloff
2019-09-25 15:27 ` Jiri Kosina
2019-09-25 15:42 ` Joerg Roedel
2019-09-27 9:47 ` Kurt Garloff
2019-09-27 10:30 ` Shah, Nehal-bakulchandra
2019-10-09 19:25 ` Jiri Kosina [this message]
2019-10-09 19:36 ` Suthikulpanit, Suravee
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=nycvar.YFH.7.76.1910092124260.13160@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=Sandeep.Singh@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=joro@8bytes.org \
--cc=kurt@garloff.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nbshah@amd.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).