All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Stewart Hildebrand <stewart.hildebrand@amd.com>
Subject: Re: [PATCH v3 4/6] vPCI: really no ext-caps without extended config space
Date: Thu, 29 Jan 2026 15:13:50 +0100	[thread overview]
Message-ID: <aXtrHszjdhVsaRLZ@Mac.lan> (raw)
In-Reply-To: <d7ef6302-9034-45da-97d7-25c76204b2fd@suse.com>

On Thu, Jan 29, 2026 at 02:09:27PM +0100, Jan Beulich wrote:
> For DomU-s, whether to emulate accesses to the first 32 bits of extended
> config space as read-as-zero or read-as-all-ones depends on whether a
> device actually has extended config space. If it doesn't, read-as-zero
> isn't correct; not getting this right may confuse functions like Linux
> 6.19-rc's pci_ext_cfg_is_aliased().
> 
> For Dom0 this then simply allows dropping a later conditional.
> 
> Fixes: a845b50c12f3 ("vpci/header: Emulate extended capability list for dom0")
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Acked-by: Roger Pau Monné <roger.pau@citrix.com>

Thanks, Roger.


  reply	other threads:[~2026-01-29 14:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 13:05 [PATCH v3 0/6] (v)PCI: extended capability handling Jan Beulich
2026-01-29 13:07 ` [PATCH v3 1/6] PCI: handle PCI->PCIe bridges as well in free_pdev() Jan Beulich
2026-01-29 13:49   ` Roger Pau Monné
2026-01-29 13:08 ` [PATCH v3 2/6] PCI: determine whether a device has extended config space Jan Beulich
2026-01-29 14:09   ` Roger Pau Monné
2026-01-29 14:17     ` Jan Beulich
2026-02-02  9:14   ` Jan Beulich
2026-02-02  9:21     ` Roger Pau Monné
2026-01-29 13:08 ` [PATCH v3 3/6] PCI: don't look for ext-caps when there's no extended cfg space Jan Beulich
2026-01-29 13:09 ` [PATCH v3 4/6] vPCI: really no ext-caps without extended config space Jan Beulich
2026-01-29 14:13   ` Roger Pau Monné [this message]
2026-01-29 13:10 ` [PATCH v3 5/6] x86/PCI: avoid re-evaluation of extended config space accessibility Jan Beulich
2026-01-29 15:32   ` Roger Pau Monné
2026-01-29 15:47     ` Jan Beulich
2026-02-02  8:51   ` Jan Beulich
2026-02-02  9:14     ` Roger Pau Monné
2026-02-02  9:30       ` Jan Beulich
2026-02-02 10:13         ` Roger Pau Monné
2026-02-02 14:40           ` Jan Beulich
2026-02-02 15:18             ` Roger Pau Monné
2026-02-03 14:48               ` Jan Beulich
2026-02-03 17:19                 ` Roger Pau Monné
2026-02-02 19:25     ` Stewart Hildebrand
2026-01-29 13:10 ` [PATCH v3 6/6] vPCI: re-init extended-capability lists when MMCFG availability changed Jan Beulich
2026-01-29 15:40   ` Roger Pau Monné
2026-01-29 15:54     ` Jan Beulich
2026-01-29 17:41       ` Roger Pau Monné

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=aXtrHszjdhVsaRLZ@Mac.lan \
    --to=roger.pau@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=stewart.hildebrand@amd.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.