From: Bjorn Helgaas <helgaas@kernel.org>
To: "Kallol Biswas [C]" <kallol.biswas@nutanix.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: uefi secureboot vm and IO window overlap
Date: Fri, 9 Dec 2022 14:56:17 -0600 [thread overview]
Message-ID: <20221209205617.GA1732532@bhelgaas> (raw)
In-Reply-To: <BL3PR02MB798651506589044302A23DFAFE1C9@BL3PR02MB7986.namprd02.prod.outlook.com>
Hi Kallol,
On Fri, Dec 09, 2022 at 06:44:42PM +0000, Kallol Biswas [C] wrote:
> We are observing an io window overlap issue in a secureboot enabled uefi vm.
>
> Linux displays:
> pci 0000:00:1d.0: can't claim BAR 4 [io 0x92a0-0x92bf]: address conflict with PCI Bus 0000:01 [io 0x9000-0x9fff]
>
> Eventually conflict gets resolved but we need to understand why get the conflict in the first place.
>
> Details:
>
> The VM is a uefi based VM and the issue shows up if secure boot is
> enabled. We have enabled ovmf log and uefi/ovmf programs a bridge
> IO window with the range 0x9000-0x91ff, but in Linux we see the same
> bridge is programmed with 0x9000-0x9fff. This results in an address
> conflict with subsequent devices.
Linux normally doesn't reassign bridge windows if the existing
configuration (typically from firmware) works.
Booting with "pci=earlydump" should dump the config before Linux
touches anything.
I see your response about being able to reproduce it where it's easier
to debug. If you need more help, please include the complete dmesg
log so we can see what's happening.
Bjorn
next prev parent reply other threads:[~2022-12-09 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 18:44 uefi secureboot vm and IO window overlap Kallol Biswas [C]
2022-12-09 20:04 ` Kallol Biswas [C]
2022-12-09 20:56 ` Bjorn Helgaas [this message]
2022-12-10 17:45 ` Kallol Biswas [C]
2022-12-13 21:30 ` Bjorn Helgaas
2023-06-07 21:41 ` Kallol Biswas [C]
2023-06-07 22:15 ` Bjorn Helgaas
2023-06-12 17:46 ` Kallol Biswas [C]
2023-06-12 18:00 ` Bjorn Helgaas
2022-12-10 17:46 ` Kallol Biswas [C]
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=20221209205617.GA1732532@bhelgaas \
--to=helgaas@kernel.org \
--cc=kallol.biswas@nutanix.com \
--cc=linux-pci@vger.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