All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Nipun Gupta <nipun.gupta@amd.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"maz@kernel.org" <maz@kernel.org>, "jgg@ziepe.ca" <jgg@ziepe.ca>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "git (AMD-Xilinx)" <git@amd.com>,
	"Anand, Harpreet" <harpreet.anand@amd.com>,
	"Jansen Van Vuuren, Pieter" <pieter.jansen-van-vuuren@amd.com>,
	"Agarwal, Nikhil" <nikhil.agarwal@amd.com>,
	"Simek, Michal" <michal.simek@amd.com>,
	"Gangurde, Abhijit" <abhijit.gangurde@amd.com>,
	"Cascon, Pablo" <pablo.cascon@amd.com>
Subject: Re: [PATCH] cdx: add MSI support for CDX bus
Date: Mon, 15 May 2023 18:46:55 +0200	[thread overview]
Message-ID: <877ct9a6f4.ffs@tglx> (raw)
In-Reply-To: <8efbbe8f-62f8-4711-d069-44905c841709@amd.com>

Nipun!

On Mon, May 15 2023 at 18:39, Nipun Gupta wrote:
> On 5/12/2023 11:45 PM, Thomas Gleixner wrote:
>> On Fri, May 12 2023 at 19:50, Nipun Gupta wrote:
>>>
>>> As per your suggestion, we can add Firmware interaction code in the
>>> irq_bus_sync_xx APIs. Another option is to change the
>>> cdx_mcdi_rpc_async() API to atomic synchronous API.
>> 
>> I'm not a great fan of that. Depending on how long this update takes the
>> CPU will busy wait for it to complete with interrupts disabled and locks
>> held.
>
> Agree. we are also inclined towards using irq_bus_sync_xx APIs. This 
> would definitely solve the issue (#1 and #2) for the setup_irq which you 
> mentioned.
>
> For MSI affinity, since GIC-ITS always return IRQ_SET_MASK_OK_DONE, the 
> irq_chip_write_msi_msg does not get called.
>
> msi_domain_set_affinity(...)
>      ret = parent->chip->irq_set_affinity(...);
>      // For GIC ITS it always return IRQ_SET_MASK_OK_DONE
>      if (ret >= 0 && ret != IRQ_SET_MASK_OK_DONE) {
>          irq_chip_write_msi_msg(...);
>      }
> Since CDX bus is specific to ARM and uses GIC ITS, it seems we do not 
> need to do anything here. Can you please share your opinion on this?

That makes sense.

Thanks,

        tglx

      reply	other threads:[~2023-05-15 16:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 14:09 [PATCH] cdx: add MSI support for CDX bus Nipun Gupta
2023-05-09  8:01 ` Thomas Gleixner
2023-05-09 11:06   ` Gupta, Nipun
2023-05-09 22:01     ` Thomas Gleixner
2023-05-10 14:04       ` Nipun Gupta
2023-05-10 22:29         ` Thomas Gleixner
2023-05-10 23:52           ` Thomas Gleixner
2023-05-12 14:20           ` Nipun Gupta
2023-05-12 18:15             ` Thomas Gleixner
2023-05-15 13:09               ` Nipun Gupta
2023-05-15 16:46                 ` Thomas Gleixner [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=877ct9a6f4.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=abhijit.gangurde@amd.com \
    --cc=git@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=harpreet.anand@amd.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=michal.simek@amd.com \
    --cc=nikhil.agarwal@amd.com \
    --cc=nipun.gupta@amd.com \
    --cc=pablo.cascon@amd.com \
    --cc=pieter.jansen-van-vuuren@amd.com \
    /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.