All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Teddy Astie" <teddy.astie@vates.tech>
To: xen-devel@lists.xenproject.org
Cc: "Teddy Astie" <teddy.astie@vates.tech>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH v1 0/2] x86/pci: MMCFG improvements and always use it if available
Date: Wed, 07 Jan 2026 16:54:55 +0000	[thread overview]
Message-ID: <cover.1767804090.git.teddy.astie@vates.tech> (raw)

Currently, Xen uses legacy method to access the configuration space unless the
access cannot be made with it, where Xen fallbacks to MMCFG. This is not really
great, as MMCFG is more flexible and doesn't require a dedicated lock, so it would
be preferable to use it whenever possible.

Teddy Astie (2):
  x86/pci: Improve pci_mmcfg_{read,write} error handling
  x86/pci: Prefer using mmcfg for accessing configuration space

 xen/arch/x86/x86_64/mmconfig_64.c | 10 +++---
 xen/arch/x86/x86_64/pci.c         | 52 ++++++++++++++-----------------
 2 files changed, 28 insertions(+), 34 deletions(-)

-- 
2.52.0



--
Teddy Astie | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech



             reply	other threads:[~2026-01-07 16:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 16:54 Teddy Astie [this message]
2026-01-07 16:54 ` [PATCH v1 2/2] x86/pci: Prefer using mmcfg for accessing configuration space Teddy Astie
2026-01-08  9:56   ` Jan Beulich
2026-01-07 16:54 ` [PATCH v1 1/2] x86/pci: Improve pci_mmcfg_{read,write} error handling Teddy Astie
2026-01-08  9:51   ` Jan Beulich
2026-01-07 17:22 ` [PATCH v1 0/2] x86/pci: MMCFG improvements and always use it if available Roger Pau Monné
2026-01-07 17:58   ` Teddy Astie
2026-01-07 18:07     ` Andrew Cooper
2026-01-07 20:02       ` 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=cover.1767804090.git.teddy.astie@vates.tech \
    --to=teddy.astie@vates.tech \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.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.