From: "Jürgen Groß" <jgross@suse.com>
To: Sergey Temerkhanov <s.temerkhanov@gmail.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 0/2] Xen: Use a dedicated pointer for IRQ data
Date: Fri, 21 Aug 2020 12:18:31 +0200 [thread overview]
Message-ID: <ccc1883f-876f-c1ea-bd68-b3c8ab267a8f@suse.com> (raw)
In-Reply-To: <20200821071547.18894-1-s.temerkhanov@gmail.com>
On 21.08.20 09:15, Sergey Temerkhanov wrote:
> Use a dedicated pointer for IRQ data to avoid conflicts with some
> other parts of the kernel code which my use handler_data for their
> own purposes while still running on Xen
>
> Sergey Temerkhanov (2):
> Xen: Use a dedicated irq_info structure pointer
> Xen: Rename irq_info structure
>
> drivers/xen/events/events_2l.c | 2 +-
> drivers/xen/events/events_base.c | 80 +++++++++++++---------------
> drivers/xen/events/events_fifo.c | 5 +-
> drivers/xen/events/events_internal.h | 12 ++---
> include/linux/irq.h | 17 ++++++
> kernel/irq/chip.c | 14 +++++
> 6 files changed, 78 insertions(+), 52 deletions(-)
>
Did you see any specific problem where handler_data is written by
another component?
In case this is a real problem I don't think your approach will be
accepted, especially the IRQ subsystem maintainers probably won't
like it.
And please include the maintainers of the files you are modifying in
the recipients list of the patch(es).
Juergen
next prev parent reply other threads:[~2020-08-21 10:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 22:09 Xen 4.14.0 is busted on Dell 300x IoT Gateways Roman Shaposhnik
2020-08-18 22:20 ` Andrew Cooper
2020-08-18 22:34 ` Roman Shaposhnik
2020-08-21 1:39 ` Stefano Stabellini
2020-08-21 7:15 ` [PATCH 0/2] Xen: Use a dedicated pointer for IRQ data Sergey Temerkhanov
2020-08-21 7:15 ` [PATCH 1/2] Xen: Use a dedicated irq_info structure pointer Sergey Temerkhanov
2020-08-21 7:15 ` [PATCH 2/2] Xen: Rename irq_info structure Sergey Temerkhanov
2020-08-21 10:18 ` Jürgen Groß [this message]
2020-08-21 11:19 ` [PATCH 0/2] Xen: Use a dedicated pointer for IRQ data Sergei Temerkhanov
2020-08-21 12:17 ` Jürgen Groß
2020-08-21 20:07 ` Thomas Gleixner
2020-08-21 20:38 ` Sergei Temerkhanov
2020-08-22 0:16 ` Thomas Gleixner
2020-08-25 3:14 ` Stefano Stabellini
2020-08-25 8:58 ` Thomas Gleixner
2020-08-25 13:49 ` Jürgen Groß
2020-08-25 15:22 ` [PATCH] xen/events: Use chip data for storing per IRQ XEN data pointer, Thomas Gleixner
2020-08-25 15:43 ` [PATCH] xen/events: Use chip data for storing per IRQ XEN data pointer Jürgen Groß
2020-08-25 22:04 ` Roman Shaposhnik
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=ccc1883f-876f-c1ea-bd68-b3c8ab267a8f@suse.com \
--to=jgross@suse.com \
--cc=s.temerkhanov@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).