From: Juergen Gross <jgross@suse.com>
To: Oleksandr Tyshchenko <Oleksandr_Tyshchenko@epam.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 7/7] xen/events: remove some info_for_irq() calls in pirq handling
Date: Wed, 15 Nov 2023 08:41:08 +0100 [thread overview]
Message-ID: <dfcd84b8-4fb2-42fa-9346-fa447992f8cd@suse.com> (raw)
In-Reply-To: <1a62fc9a-7bd2-4fed-a690-0a12f2724044@epam.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1165 bytes --]
On 14.11.23 19:16, Oleksandr Tyshchenko wrote:
>
>
> On 16.10.23 09:28, Juergen Gross wrote:
>
> Hello Juergen
>
>
>> Instead of the IRQ number user the struct irq_info pointer as parameter
>> in the internal pirq related functions. This allows to drop some calls
>> of info_for_irq().
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>
>
> Looks good, so
>
> Reviewed-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
>
>
> Just one NIT below ...
>
>
> [snip]
>
>>
>> -static void pirq_query_unmask(int irq)
>> +static void pirq_query_unmask(struct irq_info *info)
>> {
>> struct physdev_irq_status_query irq_status;
>> - struct irq_info *info = info_for_irq(irq);
>>
>> BUG_ON(info->type != IRQT_PIRQ);
>>
>> - irq_status.irq = pirq_from_irq(irq);
>> + irq_status.irq = info->u.pirq.pirq;
>
>
> ... what is the reason to open-code pirq_from_irq() here?
> For example, __startup_pirq() continues to use helper in almost the same
> situation ...
Good catch. I'll change that, especially as it allows to remove the BUG_ON()
which is in the helper already.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2023-11-15 7:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 6:28 [PATCH 0/7] xen/events: do some cleanups in events_base.c Juergen Gross
2023-10-16 6:28 ` [PATCH 1/7] xen/events: fix delayed eoi list handling Juergen Gross
2023-11-13 13:51 ` Oleksandr Tyshchenko
2023-10-16 6:28 ` [PATCH 2/7] xen/events: remove unused functions Juergen Gross
2023-11-13 14:20 ` Oleksandr Tyshchenko
2023-10-16 6:28 ` [PATCH 3/7] xen/events: reduce externally visible helper functions Juergen Gross
2023-11-13 15:53 ` Oleksandr Tyshchenko
2023-10-16 6:28 ` [PATCH 4/7] xen/events: remove some simple helpers from events_base.c Juergen Gross
2023-11-13 17:35 ` Oleksandr Tyshchenko
2023-11-14 8:28 ` Juergen Gross
2023-10-16 6:28 ` [PATCH 5/7] xen/events: drop xen_allocate_irqs_dynamic() Juergen Gross
2023-11-14 8:20 ` Oleksandr Tyshchenko
2023-11-14 8:35 ` Juergen Gross
2023-11-14 18:29 ` Oleksandr Tyshchenko
2023-10-16 6:28 ` [PATCH 6/7] xen/events: modify internal [un]bind interfaces Juergen Gross
2023-11-14 13:45 ` Oleksandr Tyshchenko
2023-10-16 6:28 ` [PATCH 7/7] xen/events: remove some info_for_irq() calls in pirq handling Juergen Gross
2023-11-14 18:16 ` Oleksandr Tyshchenko
2023-11-15 7:41 ` Juergen Gross [this message]
2023-11-13 7:14 ` [PATCH 0/7] xen/events: do some cleanups in events_base.c Juergen Gross
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=dfcd84b8-4fb2-42fa-9346-fa447992f8cd@suse.com \
--to=jgross@suse.com \
--cc=Oleksandr_Tyshchenko@epam.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox