From: Petre Ovidiu PIRCALABU <ppircalabu@bitdefender.com>
To: Tamas K Lengyel <tamas@tklengyel.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Razvan Cojocaru" <rcojocaru@bitdefender.com>,
"Wei Liu" <wl@xen.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"George Dunlap" <George.Dunlap@eu.citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Tim Deegan" <tim@xen.org>, "Julien Grall" <julien.grall@arm.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Alexandru Stefan ISAILA" <aisaila@bitdefender.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v2 00/10] Per vcpu vm_event channels
Date: Wed, 17 Jul 2019 09:14:06 +0000 [thread overview]
Message-ID: <d7868b396957fd0455f14e79c1e0f28985361809.camel@bitdefender.com> (raw)
In-Reply-To: <CABfawhmXfCRfM_YpDVRJLVpNDKLct+NJvraeHS2V_298SqSusw@mail.gmail.com>
On Tue, 2019-07-16 at 14:45 -0600, Tamas K Lengyel wrote:
> On Tue, Jul 16, 2019 at 11:06 AM Petre Pircalabu
> <ppircalabu@bitdefender.com> wrote:
> >
> > This patchset adds a new mechanism of sending synchronous vm_event
> > requests and handling vm_event responses without using a ring.
> > As each synchronous request pauses the vcpu until the corresponding
> > response is handled, it can be stored in a slotted memory buffer
> > (one per vcpu) shared between the hypervisor and the controlling
> > domain.
> >
> > The main advantages of this approach are:
> > * the ability to dynamicaly allocate the necessary memory used to
> > hold
> > the requests/responses (the size of
> > vm_event_request_t/vm_event_response_t
> > can grow unrestricted by the ring's one page limitation)
> > * the ring's waitqueue logic is unnecessary in this case because
> > the
> > vcpu sending the request is blocked until a response is received.
>
> Could you please push a git branch for this somewhere?
>
> Thanks,
> Tamas
I've pushed this changes to my github xen fork:
https://github.com/petrepircalabu/xen/tree/vm_event_ng/devel
The tag for patchset is per_cpu_vm_event_channels_v2.
Many thanks for your support,
Petre
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-07-17 9:14 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
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 [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=d7868b396957fd0455f14e79c1e0f28985361809.camel@bitdefender.com \
--to=ppircalabu@bitdefender.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=aisaila@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.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.