From: Vasant Hegde <vashegde@amd.com>
To: Eric Wagner <ewagner12@gmail.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
Robin Murphy <robin.murphy@arm.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: Kernel 6.7 regression doesn't boot if using AMD eGPU
Date: Wed, 17 Apr 2024 14:27:03 +0530 [thread overview]
Message-ID: <6a83ebdc-0c9f-47d2-967b-d4ddea039da5@amd.com> (raw)
In-Reply-To: <CAHudX3w63VPCjP5mxOePPosa+KkUw7eMRcJF=MJ-ktNO7CwXdg@mail.gmail.com>
On 4/17/2024 7:46 AM, Eric Wagner wrote:
> On Tue, Apr 16, 2024 at 6:53 AM Vasant Hegde <vashegde@amd.com> wrote:
>>
>> Hi Eric,
>>
>
.../...
>>>
>>>
>>> As it booted ok with Robin's patch above, these changes to
>>> drivers/iommu/amd/iommu.c didn't seem to make a difference for me. I was testing
>>> with amd iommu v2 off in the kernel config and I also have TSME enabled in the
>>> BIOS if that matters.
>>
>> TMSE is transparent to OS. So its fine.
>>
>> -Vasant
>>
> Output of lspci -vvv and /proc/cmdline attached.
Thanks Eric.
-Vasant
next prev parent reply other threads:[~2024-04-17 8:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 22:04 Kernel 6.7 regression doesn't boot if using AMD eGPU Eric Wagner
2024-04-14 0:01 ` Bagas Sanjaya
2024-04-15 8:04 ` Joerg Roedel
2024-04-15 16:30 ` Jason Gunthorpe
2024-04-15 18:57 ` Eric Wagner
2024-04-15 21:44 ` Robin Murphy
2024-04-16 0:39 ` Jason Gunthorpe
[not found] ` <CAHudX3x-ofB=-K6UwWpf4r7Ge9AQbvLQ2qq2C7N-R5LG2qMz7Q@mail.gmail.com>
2024-04-16 10:53 ` Vasant Hegde
2024-04-16 11:39 ` Jason Gunthorpe
2024-04-17 2:16 ` Eric Wagner
2024-04-17 8:57 ` Vasant Hegde [this message]
2024-04-16 11:25 ` Robin Murphy
2024-04-16 11:49 ` Jason Gunthorpe
2024-04-17 8:48 ` Vasant Hegde
2024-04-16 12:44 ` Vasant Hegde
2024-04-17 10:36 ` Robin Murphy
2024-04-18 5:01 ` Vasant Hegde
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=6a83ebdc-0c9f-47d2-967b-d4ddea039da5@amd.com \
--to=vashegde@amd.com \
--cc=ewagner12@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
/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