All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis <tachyon_gun@web.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Jan Beulich" <jbeulich@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Aw: Re:  Re: Re: [help] Xen 4.14.5 on Devuan 4.0 Chimaera, regression from Xen 4.0.1
Date: Sun, 19 Mar 2023 20:38:58 +0100	[thread overview]
Message-ID: <trinity-b7bc2797-26a7-455a-8080-8d33234171c9-1679254738309@3c-app-webde-bap20> (raw)
In-Reply-To: <e5a4689e-27e1-6992-65f8-c59b669aeaf1@citrix.com>

On 14.03.2023 16:11, Andrew Cooper wrote:
> On 14/03/2023 2:53 pm, Denis wrote:
> > On 14.03.2023 07:37; Jan Beulich wrote:
> >> On 14.03.2023 02:15, Denis wrote:
> >>> On 13.03.2023 10:36, Jan wrote
> >>>> On 10.03.2023 21:50, Denis wrote:
> >>>>> Should I test something else?
> >>>> ... there was no request for any further testing here, for the moment.
> >>> ah...sorry, going by "Would be nice to have this confirmed forthe system
> >>> in question, i.e. without Xen underneath Linux" I thought I could test
> >>> something which might help shed some light on all of this.
> >> Well, yes, that Linux-without-Xen test would still be useful to have
> >> results from. I didn't account for this in my earlier reply because
> >> I had asked for it before already, and I did take "something else"
> >> for meaning anything that might have turned up as useful from the new
> >> data you had provided.
> > What tests could I do or what info should I provide to help?
> 
> Can you please rebuild Xen with this patch:
> 
> diff --git a/xen/drivers/passthrough/amd/iommu_acpi.c
> b/xen/drivers/passthrough/amd/iommu_acpi.c
> index 2fdebd2d74c9..747eae25f56c 100644
> --- a/xen/drivers/passthrough/amd/iommu_acpi.c
> +++ b/xen/drivers/passthrough/amd/iommu_acpi.c
> @@ -1033,7 +1033,7 @@ static int __init parse_ivrs_table(struct
> acpi_table_header *table)
>      const struct acpi_ivrs_header *ivrs_block;
>      unsigned long length;
>      unsigned int apic;
> -    bool_t sb_ioapic = !iommu_intremap;
> +    bool_t sb_ioapic = 1;
>      int error = 0;
>  
>      BUG_ON(!table);
> 
> which should cause the behaviour to revert back to that of Xen 4.0.1 
> (i.e. it will fully ignore the checks relating to the southbridge ioapic).
> 
> Confirm that with this, and booting Xen simply with `iommu=1` that full
> DMA remapping and interrupt remapping is considered active.
> 
> 
> Then, can you play around with passing the soundblaster through to VMs. 
> Looking at the LSPCI you provided, it only supports legacy line interrupts.
> 
> Does the device work fine, or do you get a bunch of errors on `xl dmesg`
> about IO page faults (which is a generic "IOMMU said no to something"
> message)?

Sorry, it took my awhile to get it done.

The relevant things are enabled again, passthrough works (even the PCI Audigy2) 
and the devices are recognzied in the HVM domU.

As you suspected, there are a few IO page faults at the end of the boot process
(from my limited understanding it's maybe related to 
"00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 41)")

I'll attach the "xl dmesg" output file.


Denis


  parent reply	other threads:[~2023-03-19 19:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <trinity-8973751a-6742-4309-b02d-0b4c38f4206e-1678390468345@3c-app-webde-bap36>
2023-03-09 20:37 ` [help] Xen 4.14.5 on Devuan 4.0 Chimaera, regression from Xen 4.0.1 Andrew Cooper
2023-03-10  8:51   ` Jan Beulich
2023-03-10 20:50     ` Denis
2023-03-13  9:36       ` Jan Beulich
2023-03-13 11:43         ` Andrew Cooper
2023-03-13 11:54           ` Jan Beulich
2023-03-14  1:29             ` Aw: " Denis
2023-03-14  1:15         ` Denis
2023-03-14  6:37           ` Jan Beulich
2023-03-14 14:53             ` Aw: " Denis
2023-03-14 15:11               ` Andrew Cooper
2023-03-14 16:48                 ` Denis
2023-03-14 17:12                   ` Andrew Cooper
2023-03-14 19:12                     ` Aw: " Denis
2023-03-16 15:59                 ` Aw: " Jan Beulich
2023-03-19 19:42                   ` Denis
2023-03-19 19:38                 ` Denis [this message]
2023-03-20 11:01                   ` Aw: Re: Re: " Andrew Cooper
2023-03-20 12:46                     ` Denis
2023-03-20 14:23                       ` Jan Beulich
2023-03-14 15:37               ` Aw: Re: " Jan Beulich
2023-03-14 16:45                 ` Denis
2023-03-14 16:59                   ` Jan Beulich
2023-03-14 19:09                     ` Aw: " Denis
2023-03-15  8:11                       ` Jan Beulich

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=trinity-b7bc2797-26a7-455a-8080-8d33234171c9-1679254738309@3c-app-webde-bap20 \
    --to=tachyon_gun@web.de \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.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.