From: Rahul Singh <Rahul.Singh@arm.com>
To: Juergen Gross <jgross@suse.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Jane Malalane <jane.malalane@citrix.com>
Subject: Re: [PATCH v3] xen/evtchn: Introduce new IOCTL to bind static evtchn
Date: Thu, 27 Jul 2023 08:27:22 +0000 [thread overview]
Message-ID: <5EB0D195-8DEF-4817-89DC-62BAEB888720@arm.com> (raw)
In-Reply-To: <270ed8f7-c645-502e-39c5-c93823037b9c@suse.com>
HI Juergen,
> On 27 Jul 2023, at 6:54 am, Juergen Gross <jgross@suse.com> wrote:
>
> On 18.07.23 13:31, Rahul Singh wrote:
>> Xen 4.17 supports the creation of static evtchns. To allow user space
>> application to bind static evtchns introduce new ioctl
>> "IOCTL_EVTCHN_BIND_STATIC". Existing IOCTL doing more than binding
>> that’s why we need to introduce the new IOCTL to only bind the static
>> event channels.
>> Static evtchns to be available for use during the lifetime of the
>> guest. When the application exits, __unbind_from_irq() ends up being
>> called from release() file operations because of that static evtchns
>> are getting closed. To avoid closing the static event channel, add the
>> new bool variable "is_static" in "struct irq_info" to mark the event
>> channel static when creating the event channel to avoid closing the
>> static evtchn.
>> Also, take this opportunity to remove the open-coded version of the
>> evtchn close in drivers/xen/evtchn.c file and use xen_evtchn_close().
>> Signed-off-by: Rahul Singh <rahul.singh@arm.com>
>
> Pushed to xen/tip.git for-linus-6.5a
Thanks.
Regards,
Rahul
prev parent reply other threads:[~2023-07-27 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 11:31 Rahul Singh
2023-07-18 14:50 ` Oleksandr Tyshchenko
2023-07-20 0:22 ` Stefano Stabellini
2023-07-27 5:54 ` Juergen Gross
2023-07-27 8:27 ` Rahul Singh [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=5EB0D195-8DEF-4817-89DC-62BAEB888720@arm.com \
--to=rahul.singh@arm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dwmw@amazon.co.uk \
--cc=jane.malalane@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--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
all inboxes | Powered by JetHome®