linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rui Salvaterra <rsalvaterra@gmail.com>
To: Marc Zyngier <maz@kernel.org>
Cc: tglx@linutronix.de, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED] 5.15-rc1: Broken AHCI on NVIDIA ION (MCP79)
Date: Thu, 7 Oct 2021 13:03:28 +0100	[thread overview]
Message-ID: <CALjTZvbsvsD6abpw0H5D4ngUXPrgM2mDV0DX5BQi0z8cd-yxzA@mail.gmail.com> (raw)
In-Reply-To: <87bl41qkrh.wl-maz@kernel.org>

Hi again, Marc,

On Thu, 7 Oct 2021 at 09:52, Marc Zyngier <maz@kernel.org> wrote:
>
[snipped]
>
> I guess this is the relevant device?

Pretty much, yes.

> It is interesting that it
> advertises not supporting interrupt masking... Can you, you, out of
> curiosity, give the following hack a go? I would expect things to
> behave badly too (and maybe be even worse). But one way or another, it
> may give us a hint.
>
> Thanks,
>
>         M.
>
> diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
> index 0099a00af361..b3c0b9d07f17 100644
> --- a/drivers/pci/msi.c
> +++ b/drivers/pci/msi.c
> @@ -205,7 +205,7 @@ static void __pci_msi_mask_desc(struct msi_desc *desc, u32 mask)
>
>         if (desc->msi_attrib.is_msix)
>                 pci_msix_mask(desc);
> -       else if (desc->msi_attrib.maskbit)
> +       else //if (desc->msi_attrib.maskbit)
>                 pci_msi_mask(desc, mask);
>  }
>
> @@ -216,7 +216,7 @@ static void __pci_msi_unmask_desc(struct msi_desc *desc, u32 mask)
>
>         if (desc->msi_attrib.is_msix)
>                 pci_msix_unmask(desc);
> -       else if (desc->msi_attrib.maskbit)
> +       else //if (desc->msi_attrib.maskbit)
>                 pci_msi_unmask(desc, mask);
>  }

Hm. You belive the controller is lying? :) Sure thing, I'll give it a
spin and let you know the result.

Thanks,
Rui

  reply	other threads:[~2021-10-07 12:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06  8:50 [REGRESSION][BISECTED] 5.15-rc1: Broken AHCI on NVIDIA ION (MCP79) Rui Salvaterra
2021-10-06 11:00 ` Marc Zyngier
2021-10-06 11:06   ` Rui Salvaterra
2021-10-07  8:52     ` Marc Zyngier
2021-10-07 12:03       ` Rui Salvaterra [this message]
2021-10-07 12:15         ` Marc Zyngier
2021-10-07 13:11           ` Rui Salvaterra
2021-10-07 14:42             ` Marc Zyngier
2021-10-07 14:50               ` Rui Salvaterra
2021-10-07 15:03                 ` Marc Zyngier
2021-10-07 16:13                   ` Rui Salvaterra
2021-10-06 11:44 ` Rui Salvaterra
2021-10-06 11:48   ` Rui Salvaterra
2021-10-11 18:47 ` Josef Johansson
2021-10-11 19:34   ` Josef Johansson
2021-10-12  5:37     ` Josef Johansson
2021-10-12 13:07       ` Jason Andryuk
2021-10-12 13:33         ` Josef Johansson
2021-10-12 15:17           ` Josef Johansson
2021-10-12 11:34   ` Marc Zyngier
2021-10-12 12:33     ` Josef Johansson
2021-10-31 22:51       ` Rui Salvaterra
2021-11-01 11:21         ` Marc Zyngier
2021-11-01 11:36           ` Rui Salvaterra
     [not found] <1374495046.4164334.1635737050153@localhost>
2021-11-01 11:06 ` Rui Salvaterra

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=CALjTZvbsvsD6abpw0H5D4ngUXPrgM2mDV0DX5BQi0z8cd-yxzA@mail.gmail.com \
    --to=rsalvaterra@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).