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>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Anthony PERARD <anthony.perard@vates.tech>,
	Michal Orzel <michal.orzel@amd.com>,
	Stewart Hildebrand <stewart.hildebrand@amd.com>
Subject: Re: [PATCH v2 3/4] PCI: don't look for ext-caps when there's no extended cfg space
Date: Thu, 29 Jan 2026 09:53:16 +0100	[thread overview]
Message-ID: <aXsf_NFDfyJCcte1@Mac.lan> (raw)
In-Reply-To: <133c1cb0-bdb6-4c9a-bea8-c50f42ce58d7@suse.com>

On Mon, Jan 19, 2026 at 03:47:29PM +0100, Jan Beulich wrote:
> Avoid interpreting as extended capabilities what may be about anything. In
> doing so, vPCI then also won't mis-interpret data from beyond base config
> space anymore.
> 
> Fixes: 3b35911d709e ("Enable pci mmcfg and ATS for x86_64")
> 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>

> ---
> Because of the multiple prereq changes, despite the Fixes: tags I'm not
> quite sure whether to backport this. (I'm leaning towards "no".)

I won't backport, prereq changes are too intrusive.

Thanks, Roger.


  parent reply	other threads:[~2026-01-29  8:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 14:45 [PATCH v2 0/4] (v)PCI: extended capability handling Jan Beulich
2026-01-19 14:46 ` [PATCH v2 1/4] PCI: handle PCI->PCIe bridges as well in alloc_pdev() Jan Beulich
2026-01-19 22:02   ` Stewart Hildebrand
2026-01-28 14:27   ` Roger Pau Monné
2026-01-19 14:46 ` [PATCH v2 2/4] PCI: determine whether a device has extended config space Jan Beulich
2026-01-23 22:24   ` Stewart Hildebrand
2026-01-26  8:58     ` Jan Beulich
2026-01-27  4:13       ` Stewart Hildebrand
2026-01-27  9:01         ` Jan Beulich
2026-01-28 17:49   ` Roger Pau Monné
2026-01-29  8:15     ` Jan Beulich
2026-01-29 10:33       ` Roger Pau Monné
2026-01-29 11:43         ` Jan Beulich
2026-01-19 14:47 ` [PATCH v2 3/4] PCI: don't look for ext-caps when there's no extended cfg space Jan Beulich
2026-01-26 15:51   ` Stewart Hildebrand
2026-01-29  8:53   ` Roger Pau Monné [this message]
2026-01-19 14:48 ` [PATCH v2 4/4] vPCI/DomU: really no ext-caps without extended config space Jan Beulich
2026-01-26 15:52   ` Stewart Hildebrand
2026-01-29  9:19   ` Roger Pau Monné
2026-01-29 10:08     ` Jan Beulich
2026-01-29 10:51       ` Roger Pau Monné
2026-01-29 11:36         ` Jan Beulich

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=aXsf_NFDfyJCcte1@Mac.lan \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=sstabellini@kernel.org \
    --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.