From: Jan Beulich <jbeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>
Subject: Re: [PATCH for-4.20 2/3] x86/PCI: init segments earlier
Date: Mon, 3 Feb 2025 14:03:14 +0100 [thread overview]
Message-ID: <37df8931-c9f4-4af2-a099-b2bb4539bffe@suse.com> (raw)
In-Reply-To: <e7eff762-ff80-440e-8a92-e5a5e09a97ce@suse.com>
On 03.02.2025 14:00, Jan Beulich wrote:
> On 03.02.2025 13:45, Roger Pau Monné wrote:
>> On Thu, Jan 30, 2025 at 12:12:31PM +0100, Jan Beulich wrote:
>>> --- a/xen/arch/x86/x86_64/mmconfig-shared.c
>>> +++ b/xen/arch/x86/x86_64/mmconfig-shared.c
>>> @@ -402,8 +402,6 @@ void __init acpi_mmcfg_init(void)
>>> {
>>> bool valid = true;
>>>
>>> - pci_segments_init();
>>> -
>>> /* MMCONFIG disabled */
>>> if ((pci_probe & PCI_PROBE_MMCONF) == 0)
>>> return;
>>> --- a/xen/drivers/passthrough/x86/iommu.c
>>> +++ b/xen/drivers/passthrough/x86/iommu.c
>>> @@ -55,6 +55,8 @@ void __init acpi_iommu_init(void)
>>> {
>>> int ret = -ENODEV;
>>>
>>> + pci_segments_init();
>>
>> My preference might be to just place the pci_segments_init() call in
>> __start_xen(),
>
> As said in reply to Andrew - I was considering doing so as an alternative
> to the moving done here. I can certainly do so, in case some non-negative
> reply comes back from him.
Oh, and: With further adjustments following from what Andrew had outlined,
I'm actually moving the invocation of what was pci_segments_init() back to
where it's now. (Which doesn't mean that couldn't be done from
__start_xen(); just mentioning it.)
Jan
next prev parent reply other threads:[~2025-02-03 13:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 11:10 [PATCH for-4.20 0/3] AMD/IOMMU: assorted corrections Jan Beulich
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 [this message]
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=37df8931-c9f4-4af2-a099-b2bb4539bffe@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.