linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Juergen Gross <jgross@suse.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	David Airlie <airlied@linux.ie>
Subject: Re: [BISECTED] v4.15-rc: Boot regression on x86_64/AMD
Date: Wed, 10 Jan 2018 13:29:22 +0100	[thread overview]
Message-ID: <773c150c-a9e6-1246-50ee-2c468490db95@amd.com> (raw)
In-Reply-To: <20180109183856.GD31640@bhelgaas-glaptop.roam.corp.google.com>

Am 09.01.2018 um 19:38 schrieb Bjorn Helgaas:
> I don't like to add new parameters because I think it's an
> unreasonable burden on users and it makes it hard for distros, but I
> understand the desire to use this functionality.  What would you think
> of adding a "pci=big_root_window" parameter that logs an info message
> and taints the kernel with TAINT_FIRMWARE_WORKAROUND?  Then there's at
> least some clue that we're in uncharted territory.

Done, patches for this are in your inbox.

Additionally to that I cleaned up the 256GB patch a bit more, e.g. added 
a comment where the 0xfd00000000 limit comes from and updated the commit 
message.

Please review and/or comment,
Christian.

  reply	other threads:[~2018-01-10 12:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 22:04 [BISECTED] v4.15-rc: Boot regression on x86_64/AMD Aaro Koskinen
2018-01-06  0:00 ` Linus Torvalds
2018-01-06  2:10   ` Aaro Koskinen
2018-01-06 12:02     ` Aaro Koskinen
2018-01-06 16:47       ` Christian König
2018-01-06 17:58         ` Aaro Koskinen
2018-01-08 23:23   ` Bjorn Helgaas
2018-01-09 10:37     ` Christian König
2018-01-09 18:38       ` Bjorn Helgaas
2018-01-10 12:29         ` Christian König [this message]
2018-01-09 19:18       ` Linus Torvalds
2018-01-09 19:31         ` Christian König
2018-01-09 19:57           ` Linus Torvalds

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=773c150c-a9e6-1246-50ee-2c468490db95@amd.com \
    --to=christian.koenig@amd.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=helgaas@kernel.org \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).