Displaying 4 results from an estimated 4 matches for "x86_swiotlb_enable".
2023 May 18
4
unexport swiotlb_active
Hi all,
this little series removes the last swiotlb API exposed to modules.
Diffstat:
arch/x86/include/asm/xen/swiotlb-xen.h | 6 ------
arch/x86/kernel/pci-dma.c | 28 ++++------------------------
drivers/gpu/drm/nouveau/nouveau_ttm.c | 10 +++-------
drivers/pci/xen-pcifront.c | 6 ------
kernel/dma/swiotlb.c | 1 -
5 files changed, 7
2023 May 18
0
[PATCH 1/4] x86: move a check out of pci_xen_swiotlb_init
...dma.c
index de6be0a3965ee4..f887b08ac5ffe4 100644
--- a/arch/x86/kernel/pci-dma.c
+++ b/arch/x86/kernel/pci-dma.c
@@ -74,8 +74,6 @@ static inline void __init pci_swiotlb_detect(void)
#ifdef CONFIG_SWIOTLB_XEN
static void __init pci_xen_swiotlb_init(void)
{
- if (!xen_initial_domain() && !x86_swiotlb_enable)
- return;
x86_swiotlb_enable = true;
x86_swiotlb_flags |= SWIOTLB_ANY;
swiotlb_init_remap(true, x86_swiotlb_flags, xen_swiotlb_fixup);
@@ -113,7 +111,8 @@ static inline void __init pci_xen_swiotlb_init(void)
void __init pci_iommu_alloc(void)
{
if (xen_pv_domain()) {
- pci_xen_swiotlb_i...
2023 Jun 12
1
[PATCH 2/4] x86: always initialize xen-swiotlb when xen-pcifront is enabling
...i_possible. You can
either add the patch to your series or merge it into your patch 2.
You need to modify your patch like this:
@@ -111,7 +90,10 @@ static inline void __init pci_xen_swiotlb_init(void)
void __init pci_iommu_alloc(void)
{
if (xen_pv_domain()) {
- if (xen_initial_domain() || x86_swiotlb_enable)
+ if (xen_initial_domain() ||
+ (IS_ENABLED(CONFIG_XEN_PCIDEV_FRONTEND) &&
+ xen_pv_pci_possible) ||
+ x86_swiotlb_enable)
pci_xen_swiotlb_init();
return;
}
Juergen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-xen-p...
2023 Jun 09
2
[PATCH 2/4] x86: always initialize xen-swiotlb when xen-pcifront is enabling
On 07.06.23 15:12, Christoph Hellwig wrote:
> On Mon, May 22, 2023 at 10:37:09AM +0200, Juergen Gross wrote:
>> In normal cases PCI passthrough in PV guests requires to start the guest
>> with e820_host=1. So it should be rather easy to limit allocating the
>> 64MB in PV guests to the cases where the memory map has non-RAM regions
>> especially in the first 1MB of the