From: Thomas Gleixner <tglx@linutronix.de>
To: Bjorn Helgaas <helgaas@kernel.org>,
Roger Pau Monne <roger.pau@citrix.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
linux-pci@vger.kernel.org, Juergen Gross <jgross@suse.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v2 3/3] pci/msi: remove pci_msi_ignore_mask
Date: Fri, 14 Feb 2025 12:53:20 +0100 [thread overview]
Message-ID: <87y0y8ivyn.ffs@tglx> (raw)
In-Reply-To: <20250205151731.GA915292@bhelgaas>
On Wed, Feb 05 2025 at 09:17, Bjorn Helgaas wrote:
>> Albeit Devices behind a VMD bridge are not known to Xen, that doesn't mean
>> Linux cannot use them. By inhibiting the usage of
>> VMD_FEAT_CAN_BYPASS_MSI_REMAP and the removal of the pci_msi_ignore_mask
>> bodge devices behind a VMD bridge do work fine when use from a Linux Xen
>> hardware domain. That's the whole point of the series.
>>
>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>
> Needs an ack from Thomas.
No objections from my side (aside of your change log comments).
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2025-02-14 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 10:33 [PATCH v2 0/3] xen: fix usage of devices behind a VMD bridge Roger Pau Monne
2025-01-14 10:33 ` [PATCH v2 1/3] xen/pci: do not register devices with segments >= 0x10000 Roger Pau Monne
2025-02-14 17:20 ` Bjorn Helgaas
2025-01-14 10:33 ` [PATCH v2 2/3] vmd: disable MSI remapping bypass under Xen Roger Pau Monne
2025-02-14 17:23 ` Bjorn Helgaas
2025-01-14 10:33 ` [PATCH v2 3/3] pci/msi: remove pci_msi_ignore_mask Roger Pau Monne
2025-02-05 15:17 ` Bjorn Helgaas
2025-02-06 8:33 ` Roger Pau Monné
2025-02-06 16:02 ` Bjorn Helgaas
2025-02-14 11:53 ` Thomas Gleixner [this message]
2025-02-05 14:37 ` [PATCH v2 0/3] xen: fix usage of devices behind a VMD bridge Roger Pau Monné
2025-02-14 17:17 ` Bjorn Helgaas
2025-02-14 18:46 ` Jürgen Groß
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=87y0y8ivyn.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=roger.pau@citrix.com \
--cc=x86@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox