From: Jan Beulich <jbeulich@suse.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Vincent Guittot" <vincent.guittot@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
stratos-dev@op-lists.linaro.org,
"Erik Schilling" <erik.schilling@linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
"Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>
Subject: Re: [PATCH V3 1/2] xen: Update dm_op.h from Xen public header
Date: Tue, 25 Jul 2023 09:49:51 +0200 [thread overview]
Message-ID: <920ede72-c2fb-c814-7b1c-aa488e400f83@suse.com> (raw)
In-Reply-To: <20230725074218.zcgbkkx5pfgszimu@vireshk-i7>
On 25.07.2023 09:42, Viresh Kumar wrote:
> On 25-07-23, 09:18, Jan Beulich wrote:
>> I question that use, btw, but it is not up to me to decide whether to
>> accept such a layering violation in Linux. dm-op is, as its name says,
>> for device models to use. Your intended use doesn't fall in that
>> category, aiui. Imo the present contents of dm_op.h in Linux is indeed
>> all a kernel is supposed to know about, unless it was to gain in-kernel
>> device models.
>
> Is there any other way by which an interrupt can be raised for the
> guest VM ? I was only aware of this method and so implemented it like
> this.
>
> I am open to suggestions on this.
Well. I don't know your requirements. Generally I would suggest using
event channels, not interrupts, when talking about injecting events
into guests. If it strictly needs to be an interrupt, then I guess a
non-dm-op means would need introducing if none already exists.
Jan
next prev parent reply other threads:[~2023-07-25 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 6:47 Viresh Kumar
2023-07-25 6:47 ` [PATCH V3 2/2] xen: privcmd: Add support for irqfd Viresh Kumar
2023-07-25 8:42 ` Juergen Gross
2023-07-25 7:04 ` [PATCH V3 1/2] xen: Update dm_op.h from Xen public header Jan Beulich
2023-07-25 7:09 ` Viresh Kumar
2023-07-25 7:18 ` Jan Beulich
2023-07-25 7:42 ` Viresh Kumar
2023-07-25 7:49 ` Jan Beulich [this message]
2023-07-25 7:54 ` 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=920ede72-c2fb-c814-7b1c-aa488e400f83@suse.com \
--to=jbeulich@suse.com \
--cc=alex.bennee@linaro.org \
--cc=erik.schilling@linaro.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=mathieu.poirier@linaro.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=stratos-dev@op-lists.linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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®