From: Demi Marie Obenour <demiobenour@gmail.com>
To: val@invisiblethingslab.com
Cc: jgross@suse.com, linux-kernel@vger.kernel.org,
oleksandr_tyshchenko@epam.com, sstabellini@kernel.org,
xen-devel@lists.xenproject.org
Subject: Re: [RFC PATCH] xen: privcmd: fix ioeventfd/ioreq crashing PV domain
Date: Sat, 18 Oct 2025 21:07:05 -0400 [thread overview]
Message-ID: <b12612a9-8593-4e0d-b5fa-14b30eaf2647@gmail.com> (raw)
In-Reply-To: <1dc70410-310a-4a00-8c47-0eebdb023267@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 637 bytes --]
On 10/18/25 20:42, Demi Marie Obenour wrote:
> I'm pretty sure Xen doesn't support ioeventfd at all yet. There are
> two options:
>
> 1. Port the backend to use an ioreq server instead of ioeventfd.
> 2. Modify Linux (and possibly Xen) to support ioeventfd.
>
> Which virtio device are you trying to implement? virtio-GPU will need
> a lot of additional work and it would probably be best to discuss
> this privately (over a call or similar). Others are likely to be
> significantly easier.
Whoops, I got confused and didn't see you were using a Xen-native
frontend.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-10-19 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 19:57 [RFC PATCH] xen: privcmd: fix ioeventfd/ioreq crashing PV domain Val Packett
2025-10-19 0:42 ` Demi Marie Obenour
2025-10-19 1:07 ` Demi Marie Obenour [this message]
2025-11-04 12:15 ` Jürgen Groß
2025-11-04 23:05 ` Demi Marie Obenour
2025-11-04 23:06 ` Demi Marie Obenour
2025-11-05 1:16 ` Val Packett
2025-11-05 20:42 ` Demi Marie Obenour
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=b12612a9-8593-4e0d-b5fa-14b30eaf2647@gmail.com \
--to=demiobenour@gmail.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=val@invisiblethingslab.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).