From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel <dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: CONFIG_AMDGPU triggers full rebuild
Date: Fri, 25 Sep 2020 16:54:46 +0200 [thread overview]
Message-ID: <5d0d4c05-a42a-a3d2-87a1-8520ab64a062@gmail.com> (raw)
In-Reply-To: <e7f5e4ae-7a6a-0a3c-666c-05180a8fe726@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 614 bytes --]
Maybe MMU notifiers? But honestly I don't know for sure.
Christian.
Am 25.09.20 um 16:29 schrieb Thomas Zimmermann:
> Hi,
>
> whenever I change the option CONFIG_AMDGPU, I have to rebuild the whole
> kernel. I guess it auto-selects some architecture-specific feature. That
> full rebuild might be avoidable if I could enable that feature permanently.
>
> Any ideas what this could be and how to avoid the full rebuilt?
>
> Best regards
> Thomas
>
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
[-- Attachment #1.2: Type: text/html, Size: 1269 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-09-25 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 14:29 CONFIG_AMDGPU triggers full rebuild Thomas Zimmermann
2020-09-25 14:54 ` Christian König [this message]
2020-09-25 15:04 ` Thomas Zimmermann
2020-09-28 16:17 ` Felix Kuehling
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=5d0d4c05-a42a-a3d2-87a1-8520ab64a062@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
/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