From: Jan Beulich <JBeulich@suse.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: 'Petre Ovidiu PIRCALABU' <ppircalabu@bitdefender.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
KonradRzeszutek Wilk <konrad.wilk@oracle.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"Tim\(Xen.org\)" <tim@xen.org>,
George Dunlap <George.Dunlap@citrix.com>,
JulienGrall <julien.grall@arm.com>,
Tamas K Lengyel <tamas@tklengyel.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Alexandru Stefan ISAILA <aisaila@bitdefender.com>,
IanJackson <Ian.Jackson@citrix.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v2 07/10] vm_event: Add vm_event_ng interface
Date: Fri, 19 Jul 2019 12:59:34 +0000 [thread overview]
Message-ID: <96e2ece1-5460-52d5-d2a5-8123d8148441@suse.com> (raw)
In-Reply-To: <24e346edb9604148b5790369b4fce384@AMSPEX02CL03.citrite.net>
On 19.07.2019 14:37, Paul Durrant wrote:
>> From: Jan Beulich <JBeulich@suse.com>
>> Sent: 19 July 2019 13:32
>>
>> On 19.07.2019 14:11, Paul Durrant wrote:
>>>> -----Original Message-----
>>>> From: Petre Ovidiu PIRCALABU <ppircalabu@bitdefender.com>
>>>> Sent: 19 July 2019 12:24
>>>>
>>>> Sorry, my mistake. I meant to say it's shared with MD.
>>>>
>>>> Many thanks for your support,
>>>
>>> Ok, in that case please share with the ID instead.
>>
>> But that's exactly what we want to avoid: If sharing at all, then
>> please with the more privileged entity.
>
> Why? We're talking HVM guests only here IIUC so this is equivalent
> to IOREQ server...
Not sure: The main vm_event.c files live in common/ and arch/x86/
respectively, so I thought at least architecturally VM events were
possible for PV as well. If it's indeed HVM-only, then following
the IOREQ server model in its entirety would of course be fine.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-07-19 13:00 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 17:06 [Xen-devel] [PATCH v2 00/10] Per vcpu vm_event channels Petre Pircalabu
2019-07-16 17:06 ` [Xen-devel] [PATCH v2 01/10] vm_event: Define VM_EVENT type Petre Pircalabu
2019-07-16 20:59 ` Tamas K Lengyel
2019-07-17 7:59 ` Petre Ovidiu PIRCALABU
2019-07-17 8:49 ` Alexandru Stefan ISAILA
2019-07-17 9:57 ` Petre Ovidiu PIRCALABU
2019-07-16 17:06 ` [Xen-devel] [PATCH v2 02/10] vm_event: Remove "ring" suffix from vm_event_check_ring Petre Pircalabu
2019-07-17 9:11 ` Alexandru Stefan ISAILA
2019-07-16 17:06 ` [Xen-devel] [PATCH v2 03/10] vm_event: Add 'struct domain' backpointer to vm_event_domain Petre Pircalabu
2019-07-16 21:02 ` Tamas K Lengyel
2019-07-17 9:28 ` Jan Beulich
2019-07-16 17:06 ` [Xen-devel] [PATCH v2 04/10] vm_event: Simplify vm_event interface Petre Pircalabu
2019-07-16 21:04 ` Tamas K Lengyel
2019-07-17 11:13 ` Alexandru Stefan ISAILA
2019-07-16 17:06 ` [Xen-devel] [PATCH v2 05/10] vm_event: Move struct vm_event_domain to vm_event.c Petre Pircalabu
2019-07-17 9:31 ` Jan Beulich
2019-07-17 12:26 ` Petre Ovidiu PIRCALABU
2019-07-16 17:06 ` [Xen-devel] [PATCH v2 06/10] vm_event: Decouple implementation details from interface Petre Pircalabu
2019-07-16 17:06 ` [Xen-devel] [PATCH v2 07/10] vm_event: Add vm_event_ng interface Petre Pircalabu
2019-07-16 21:13 ` Tamas K Lengyel
2019-07-17 12:13 ` Petre Ovidiu PIRCALABU
2019-07-17 10:06 ` Jan Beulich
2019-07-17 12:38 ` Tamas K Lengyel
2019-07-17 13:12 ` Jan Beulich
2019-07-17 14:41 ` Petre Ovidiu PIRCALABU
2019-07-17 16:32 ` Jan Beulich
2019-07-17 18:42 ` Paul Durrant
2019-07-18 13:59 ` Petre Ovidiu PIRCALABU
2019-07-18 14:44 ` Jan Beulich
2019-07-18 14:55 ` Petre Ovidiu PIRCALABU
2019-07-31 12:53 ` Petre Ovidiu PIRCALABU
2019-07-31 13:09 ` Jan Beulich
2019-07-19 7:56 ` Paul Durrant
2019-07-19 8:22 ` Jan Beulich
2019-07-19 8:26 ` Paul Durrant
2019-07-19 11:23 ` Petre Ovidiu PIRCALABU
2019-07-19 12:11 ` Paul Durrant
2019-07-19 12:32 ` Jan Beulich
2019-07-19 12:37 ` Paul Durrant
2019-07-19 12:59 ` Jan Beulich [this message]
2019-07-19 17:40 ` Petre Ovidiu PIRCALABU
2019-07-22 7:58 ` Paul Durrant
2019-07-22 7:59 ` Jan Beulich
2019-07-22 10:44 ` Petre Ovidiu PIRCALABU
2019-07-17 13:42 ` Alexandru Stefan ISAILA
2019-07-17 14:46 ` Petre Ovidiu PIRCALABU
2019-07-16 17:06 ` [Xen-devel] [PATCH v2 08/10] xen-access: Use getopt_long for cmdline parsing Petre Pircalabu
2019-07-16 21:09 ` Tamas K Lengyel
2019-07-17 11:16 ` Alexandru Stefan ISAILA
2019-07-16 17:06 ` [Xen-devel] [PATCH v2 09/10] xen-access: Code cleanup Petre Pircalabu
2019-07-16 21:07 ` Tamas K Lengyel
2019-07-17 11:18 ` Alexandru Stefan ISAILA
2019-07-16 17:06 ` [Xen-devel] [PATCH v2 10/10] xen-access: Add support for vm_event_ng interface Petre Pircalabu
2019-07-16 20:45 ` [Xen-devel] [PATCH v2 00/10] Per vcpu vm_event channels Tamas K Lengyel
2019-07-17 9:14 ` Petre Ovidiu PIRCALABU
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=96e2ece1-5460-52d5-d2a5-8123d8148441@suse.com \
--to=jbeulich@suse.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=aisaila@bitdefender.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=ppircalabu@bitdefender.com \
--cc=rcojocaru@bitdefender.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tamas@tklengyel.com \
--cc=tim@xen.org \
--cc=wl@xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.