The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com
Cc: x86@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
	dlazar@gmail.com, hdegoede@redhat.com
Subject: Re: [PATCH 1/2] x86/apic: Allow reprogramming IOAPIC pins the first time for non-legacy IRQs
Date: Mon, 23 Oct 2023 08:26:58 -0500	[thread overview]
Message-ID: <89a51be4-38f9-4a9e-85fb-52c48a8fd433@amd.com> (raw)
In-Reply-To: <20231020033806.88063-1-mario.limonciello@amd.com>

On 10/19/2023 22:38, Mario Limonciello wrote:
> If the system is set up without legacy IRQs configured
> acpi_register_gsi_ioapic() still needs to be able to program the IOAPIC
> to match the values from _CRS which might not match what is already
> programmed to the IOAPIC.
> 
> Reported-by: dlazar@gmail.com
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218003
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
>   arch/x86/kernel/apic/io_apic.c | 8 ++------
>   1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
> index 00da6cf6b07d..27dd279dcc7b 100644
> --- a/arch/x86/kernel/apic/io_apic.c
> +++ b/arch/x86/kernel/apic/io_apic.c
> @@ -928,12 +928,8 @@ static bool mp_check_pin_attr(int irq, struct irq_alloc_info *info)
>   {
>   	struct mp_chip_data *data = irq_get_chip_data(irq);
>   
> -	/*
> -	 * setup_IO_APIC_irqs() programs all legacy IRQs with default trigger
> -	 * and polarity attributes. So allow the first user to reprogram the
> -	 * pin with real trigger and polarity attributes.
> -	 */
> -	if (irq < nr_legacy_irqs() && data->count == 1) {
> +	/* allow the first user to reprogram the pin with real trigger and polarity */
> +	if (data->count == 1) {
>   		if (info->ioapic.is_level != data->is_level)
>   			mp_register_handler(irq, info->ioapic.is_level);
>   		data->entry.is_level = data->is_level = info->ioapic.is_level;

David mentioned it on the Bugzilla, but for the benefit of those not 
looking there, this series is confirmed to fix the problem.

      parent reply	other threads:[~2023-10-23 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20  3:38 [PATCH 1/2] x86/apic: Allow reprogramming IOAPIC pins the first time for non-legacy IRQs Mario Limonciello
2023-10-20  3:38 ` [PATCH 2/2] x86/irq/i8259: Configure null pic to have one legacy IRQ Mario Limonciello
2023-10-23 13:26 ` Mario Limonciello [this message]

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=89a51be4-38f9-4a9e-85fb-52c48a8fd433@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dlazar@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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