From: Juergen Gross <jgross@suse.com>
To: Christoph Hellwig <hch@lst.de>,
Stefano Stabellini <sstabellini@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
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>
Cc: xen-devel@lists.xenproject.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] x86: always initialize xen-swiotlb when xen-pcifront is enabling
Date: Tue, 27 Jun 2023 09:19:18 +0200 [thread overview]
Message-ID: <660606b7-7c11-1c7a-fda4-2fdaf4d2a389@suse.com> (raw)
In-Reply-To: <20230612142542.111581-3-hch@lst.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 391 bytes --]
On 12.06.23 16:25, Christoph Hellwig wrote:
> Remove the dangerous late initialization of xen-swiotlb in
> pci_xen_swiotlb_init_late and instead just always initialize
> xen-swiotlb in the boot code if CONFIG_XEN_PCIDEV_FRONTEND is
> enabled and Xen PV PCI is possible.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2023-06-27 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 14:25 unexport swiotlb_active v2 Christoph Hellwig
2023-06-12 14:25 ` [PATCH 1/3] xen/pci: add flag for PCI passthrough being possible Christoph Hellwig
2023-06-12 14:25 ` [PATCH 2/3] x86: always initialize xen-swiotlb when xen-pcifront is enabling Christoph Hellwig
2023-06-27 7:19 ` Juergen Gross [this message]
2023-06-12 14:25 ` [PATCH 3/3] swiotlb: unexport is_swiotlb_active Christoph Hellwig
2023-06-27 7:19 ` Juergen Gross
2023-06-19 9:19 ` unexport swiotlb_active v2 Christoph Hellwig
2023-06-27 17:18 ` Petr Tesařík
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=660606b7-7c11-1c7a-fda4-2fdaf4d2a389@suse.com \
--to=jgross@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®