[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VdZrcouWXor1DjdzzWEsUC87+CkD4ZqMd165H-QXMgvRQ@mail.gmail.com>
Date: Thu, 25 Aug 2022 11:29:57 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Liao Chang <liaochang1@...wei.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Marc Zyngier <maz@...nel.org>,
Samuel Holland <samuel@...lland.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Michael Kelley <mikelley@...rosoft.com>,
Jianmin Lv <lvjianmin@...ngson.cn>,
Mark Rutland <mark.rutland@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] irqchip/gic-v3-its: Release the allocated but
unmapped bits in LPI maps
On Thu, Aug 25, 2022 at 9:11 AM Liao Chang <liaochang1@...wei.com> wrote:
>
> If one hwirq allocated in ITS domain followed by some unmapped bits, the
> number of unmapped bits will be recorded, so that this hwirq and
> following unmapped bits could be released both.
...
> + /*
> + * In order to free dangling hwirq bits, kernel uses the irq_data
the kernel
> + * of hwirq which is followed by dangling bits to record dangling
> + * number.
> + */
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists