public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: "Ni, Ray" <ray.ni@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Wu, Hao A" <hao.a.wu@intel.com>,
	Pawel Polawski <ppolawsk@redhat.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	"Albecki, Mateusz" <mateusz.albecki@intel.com>,
	"Chang, Abner" <abner.chang@hpe.com>,
	Leif Lindholm <quic_llindhol@quicinc.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	Oliver Steffen <osteffen@redhat.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>,
	"Wang, Jian J" <jian.j.wang@intel.com>,
	"Justen, Jordan L" <jordan.l.justen@intel.com>
Subject: Re: [PATCH v7 1/6] MdeModulePkg/PciHostBridge: io range is not mandatory
Date: Thu, 2 Jun 2022 15:14:57 +0200	[thread overview]
Message-ID: <20220602131457.75zndaiipdosgiid@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAMj1kXHNh2B0+SH7U9kcCO7gAeYVaBBDdgRdZXP0PQBfhGmiqg@mail.gmail.com>

  Hi,

> I did a quick test with both ArmVirtQemu and microvm (using this
> series but omitting the MdeModulePkg), and I can confirm that not
> having a I/O resource window at all seems to work fine if none of the
> PCI devices have I/O BARs.
> 
> Gerd, do you remember why exactly this patch is needed? Is it related
> to devices that have I/O BARs but don't actually require them to
> function correctly?

Well, the difference seem to be pcie root ports.  When plugging my
virtio device into the root bus everything is fine:

  PCI Bus First Scanning
  PciBus: Discovered PCI @ [00|00|00]

  PciBus: Discovered PCI @ [00|01|00]
     BAR[1]: Type =  Mem32; Alignment = 0xFFF;	Length = 0x1000;	Offset = 0x14
     BAR[4]: Type = PMem64; Alignment = 0x3FFF;	Length = 0x4000;	Offset = 0x20
  [ ... ]
  PciHostBridge: NotifyPhase (AllocateResources)
   RootBridge: PciRoot(0x0)
    Mem64: Base/Length/Alignment = 6000000000/100000/FFFFF - Success
    Mem: Base/Length/Alignment = C0000000/100000/FFFFF - Success
  PciBus: HostBridge->NotifyPhase(AllocateResources) - Success

When plugging the virtio device into a pcie root port it doesn't work
and the log looks like this:

  PCI Bus First Scanning
  PciBus: Discovered PCI @ [00|00|00]

  PciBus: Discovered PPB @ [00|08|00]
     Padding: Type =  Mem32; Alignment = 0x1FFFFF;	Length = 0x200000
     Padding: Type =     Io; Alignment = 0x1FF;	Length = 0x200
     BAR[0]: Type =  Mem32; Alignment = 0xFFF;	Length = 0x1000;	Offset = 0x10

  PciBus: Discovered PCI @ [01|00|00]
     BAR[1]: Type =  Mem32; Alignment = 0xFFF;	Length = 0x1000;	Offset = 0x14
     BAR[4]: Type = PMem64; Alignment = 0x3FFF;	Length = 0x4000;	Offset = 0x20
  [ ... ]
  PciHostBridge: NotifyPhase (AllocateResources)
   RootBridge: PciRoot(0x0)
    Mem: Base/Length/Alignment = C0000000/300000/1FFFFF - Success
    Mem64: Base/Length/Alignment = 6000000000/100000/FFFFF - Success
    I/O: Base/Length/Alignment = FFFFFFFFFFFFFFFF/1000/FFF - Out Of Resource!
  [ ... ]
  PciHostBridge: NotifyPhase (AllocateResources)
   RootBridge: PciRoot(0x0)
    Mem64: Base/Length/Alignment = 6000000000/100000/FFFFF - Success
    Mem: Base/Length/Alignment = C0000000/200000/FFFFF - Success
    I/O: Base/Length/Alignment = FFFFFFFFFFFFFFFF/0/FFF - Out Of Resource!

So, it's apparently the io window of the pcie root port which causes
edk2 try allocate io resources.

take care,
  Gerd


  reply	other threads:[~2022-06-02 13:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  8:42 [PATCH v7 0/6] OvmfPkg/Microvm/pcie: add pcie support Gerd Hoffmann
2022-06-02  8:42 ` [PATCH v7 1/6] MdeModulePkg/PciHostBridge: io range is not mandatory Gerd Hoffmann
2022-06-02 10:14   ` Ni, Ray
2022-06-02 11:43     ` Ard Biesheuvel
2022-06-02 13:14       ` Gerd Hoffmann [this message]
2022-06-02 13:58         ` Ard Biesheuvel
2022-06-03  8:29           ` [edk2-devel] " Gerd Hoffmann
2022-06-03  8:30             ` Ard Biesheuvel
2022-06-02  8:42 ` [PATCH v7 2/6] OvmfPkg/FdtPciHostBridgeLib: " Gerd Hoffmann
2022-06-02  8:42 ` [PATCH v7 3/6] OvmfPkg/Platform: unfix PcdPciExpressBaseAddress Gerd Hoffmann
2022-06-02  8:42 ` [PATCH v7 4/6] OvmfPkg/Microvm/pcie: no vbeshim please Gerd Hoffmann
2022-06-02  8:42 ` [PATCH v7 5/6] OvmfPkg/Microvm/pcie: mPhysMemAddressWidth tweak Gerd Hoffmann
2022-06-02  8:42 ` [PATCH v7 6/6] OvmfPkg/Microvm/pcie: add pcie support Gerd Hoffmann
2022-06-03  9:12 ` [PATCH v7 0/6] " Ard Biesheuvel

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-list 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=20220602131457.75zndaiipdosgiid@sirius.home.kraxel.org \
    --to=devel@edk2.groups.io \
    /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