From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>
Subject: [PATCH for-4.20 0/3] AMD/IOMMU: assorted corrections
Date: Thu, 30 Jan 2025 12:10:56 +0100 [thread overview]
Message-ID: <2bb9d3c4-0761-4d63-8193-29293e35eb04@suse.com> (raw)
The three patches are functionally independent, and they're presented
here merely in the order I came to notice the respective issues. At least
patch 2 wants seriously considering for 4.20.
1: AMD/IOMMU: drop stray MSI enabling
2: x86/PCI: init segments earlier
3: AMD/IOMMU: log IVHD contents
Jan
next reply other threads:[~2025-01-30 11:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 11:10 Jan Beulich [this message]
2025-01-30 11:11 ` [PATCH for-4.20? 1/3] AMD/IOMMU: drop stray MSI enabling Jan Beulich
2025-01-31 18:46 ` Jason Andryuk
2025-02-02 13:50 ` Andrew Cooper
2025-02-03 8:41 ` Jan Beulich
2025-02-03 14:19 ` Andrew Cooper
2025-02-03 15:53 ` Jan Beulich
2025-02-03 16:19 ` Andrew Cooper
2025-01-30 11:12 ` [PATCH for-4.20 2/3] x86/PCI: init segments earlier Jan Beulich
2025-01-31 18:47 ` Jason Andryuk
2025-02-02 14:46 ` Andrew Cooper
2025-02-03 9:09 ` Jan Beulich
2025-02-03 15:31 ` Andrew Cooper
2025-02-03 12:45 ` Roger Pau Monné
2025-02-03 13:00 ` Jan Beulich
2025-02-03 13:03 ` Jan Beulich
2025-02-03 14:23 ` Andrew Cooper
2025-02-03 15:55 ` Jan Beulich
2025-01-30 11:13 ` [PATCH for-4.20? 3/3] AMD/IOMMU: log IVHD contents Jan Beulich
2025-01-31 18:47 ` Jason Andryuk
2025-02-02 13:57 ` Andrew Cooper
2025-01-31 11:18 ` [PATCH for-4.20 0/3] AMD/IOMMU: assorted corrections Oleksii Kurochko
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=2bb9d3c4-0761-4d63-8193-29293e35eb04@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=oleksii.kurochko@gmail.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.