From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] Revert "HAX iommu/intel: Ignore igfx_off"
Date: Thu, 15 Sep 2022 08:53:16 +0100 [thread overview]
Message-ID: <500be188-d8e0-2bc6-4f54-13a8784c0321@linux.intel.com> (raw)
In-Reply-To: <20220914203545.4057637-1-lucas.demarchi@intel.com>
On 14/09/2022 21:35, Lucas De Marchi wrote:
> This reverts commit 58f44e349cfc10a4f2208fd806829c8fd046480b.
>
> To be removed from the topic/core-for-CI branch. If CI's config is
> setting that, it just shouldn't do it. Looking at a random current CI
> execution, the command line is:
>
> Command line: BOOT_IMAGE=/boot/drm_intel root=/dev/nvme0n1p2 \
> rootwait fsck.repair=yes nmi_watchdog=panic,auto panic=5 \
> softdog.soft_panic=5 drm.debug=0xe log_buf_len=1M trace_clock=global 3 \
> modprobe.blacklist=i915,snd_hda_intel ro
>
> So it should be safe to remove this commit.
It's a patch which can silently bite so no complaints from me to remove
it - just please upgrade the check from a "random current CI execution"
to something stronger. Ack from CI folks would do.
Regards,
Tvrtko
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/iommu/intel/iommu.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index 598c9b86dfd8..1f2cd43cf9bc 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -323,6 +323,8 @@ static int __init intel_iommu_setup(char *str)
> no_platform_optin = 1;
> pr_info("IOMMU disabled\n");
> } else if (!strncmp(str, "igfx_off", 8)) {
> + dmar_map_gfx = 0;
> + pr_info("Disable GFX device mapping\n");
> } else if (!strncmp(str, "forcedac", 8)) {
> pr_warn("intel_iommu=forcedac deprecated; use iommu.forcedac instead\n");
> iommu_dma_forcedac = true;
next prev parent reply other threads:[~2022-09-15 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 20:35 [Intel-gfx] [PATCH] Revert "HAX iommu/intel: Ignore igfx_off" Lucas De Marchi
2022-09-14 21:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-09-15 7:53 ` Tvrtko Ursulin [this message]
2022-09-15 8:09 ` [Intel-gfx] [PATCH] " Lucas De Marchi
2022-09-15 8:23 ` Tvrtko Ursulin
2022-09-15 17:26 ` Lucas De Marchi
2022-09-15 13:40 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
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=500be188-d8e0-2bc6-4f54-13a8784c0321@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.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