linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Myron Stowe" <myron.stowe@redhat.com>,
	"Juha-Pekka Heikkila" <juhapekka.heikkila@gmail.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"H . Peter Anvin" <hpa@zytor.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/2] x86/PCI: Ignore E820 reservations for bridge windows on newer systems
Date: Thu, 14 Oct 2021 20:39:41 +0200	[thread overview]
Message-ID: <20211014183943.27717-1-hdegoede@redhat.com> (raw)

Hi All,

Here is v5 of my patch to address the E820 reservations vs PCI host bridge
windows issue which is causing touchpad and/or thunderbolt issues on many
different laptop models.

Changes in v5:
- Drop mention of Windows behavior from the commit msg, replace with a
  reference to the specs
- Improve documentation in Documentation/admin-guide/kernel-parameters.txt
- Reword the big comment added, use "PCI host bridge window" in it and drop
  all references to Windows
- Add a second patch moving the arch/x86/pci/acpi.c printk-s to pr_info/warn

Changes in v4:
- Rewrap the big comment block to fit in 80 columns

I believe that this is ready for merging now.

Bjorn, can you review/ack this please ?

x86/tip folks it would be ideal if you can pick this up and send at
least the first patch as a fix to Linus for 5.15. This fixes a bug which
has been plaguing a lot of users (see all the bug links in the commit msg).

Regards,

Hans


Hans de Goede (2):
  x86/PCI: Ignore E820 reservations for bridge windows on newer systems
  x86/PCI/ACPI: Replace printk calls with pr_info/pr_warn calls

 .../admin-guide/kernel-parameters.txt         |  9 ++++
 arch/x86/include/asm/pci_x86.h                | 10 ++++
 arch/x86/kernel/resource.c                    |  4 ++
 arch/x86/pci/acpi.c                           | 49 +++++++++++++++----
 arch/x86/pci/common.c                         |  6 +++
 5 files changed, 68 insertions(+), 10 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-10-14 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 18:39 Hans de Goede [this message]
2021-10-14 18:39 ` [PATCH v5 1/2] x86/PCI: Ignore E820 reservations for bridge windows on newer systems Hans de Goede
2021-10-15 20:03   ` Bjorn Helgaas
2021-10-15 20:15     ` Hans de Goede
2021-10-19 21:52   ` Bjorn Helgaas
2021-10-19 21:55     ` Bjorn Helgaas
2021-10-21 11:30     ` Hans de Goede
2021-10-14 18:39 ` [PATCH v5 2/2] x86/PCI/ACPI: Replace printk calls with pr_info/pr_warn calls Hans de Goede

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=20211014183943.27717-1-hdegoede@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=juhapekka.heikkila@gmail.com \
    --cc=kw@linux.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mingo@redhat.com \
    --cc=myron.stowe@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).