From: Andrii Anisov <andrii.anisov@gmail.com>
To: Julien Grall <julien.grall@arm.com>, Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
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>,
xen-devel <xen-devel@lists.xenproject.org>,
"andrii_anisov@epam.com" <andrii_anisov@epam.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v3] xen: introduce VCPUOP_register_runstate_phys_memory_area hypercall
Date: Tue, 11 Jun 2019 15:40:16 +0300 [thread overview]
Message-ID: <e30fd795-1f90-5da5-8578-7ce75075d689@gmail.com> (raw)
In-Reply-To: <4af4bd1e-17c1-d128-05af-865c5b79cb88@arm.com>
On 11.06.19 15:32, Julien Grall wrote:
> Did you expect Xen to be fully preemptible?
>
> The function to do the scheduling is schedule(). This is either call from a softirq or directly in a few places (e.g wait()).
>
> The only place in this path where do_softirq() will be called is on return to the guest (see leave_hypervisor_tail).
Right you are! I forgot that bit. We will not pass through it on serving timer irq interrupted us in hyp mode.
--
Sincerely,
Andrii Anisov.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-06-11 12:40 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 18:12 [PATCH RFC 2] [DO NOT APPLY] introduce VCPUOP_register_runstate_phys_memory_area hypercall Andrii Anisov
2019-05-24 18:12 ` [Xen-devel] " Andrii Anisov
2019-05-24 18:12 ` [PATCH v3] Introduce runstate area registration with phys address Andrii Anisov
2019-05-24 18:12 ` [Xen-devel] " Andrii Anisov
2019-05-24 18:12 ` [PATCH v3] xen: introduce VCPUOP_register_runstate_phys_memory_area hypercall Andrii Anisov
2019-05-24 18:12 ` [Xen-devel] " Andrii Anisov
2019-06-07 14:23 ` Jan Beulich
2019-06-10 11:44 ` Julien Grall
2019-06-11 9:10 ` Jan Beulich
2019-06-11 10:22 ` Andrii Anisov
2019-06-11 12:12 ` Julien Grall
2019-06-11 12:26 ` Andrii Anisov
2019-06-11 12:32 ` Julien Grall
2019-06-11 12:40 ` Andrii Anisov [this message]
2019-06-13 12:21 ` Andrii Anisov
2019-06-13 12:39 ` Jan Beulich
2019-06-13 12:32 ` Andrii Anisov
2019-06-13 12:41 ` Jan Beulich
2019-06-13 12:48 ` Julien Grall
2019-06-13 12:58 ` Jan Beulich
2019-06-13 13:14 ` Julien Grall
2019-06-13 13:40 ` Jan Beulich
2019-06-13 14:41 ` Julien Grall
2019-06-14 14:36 ` Andrii Anisov
2019-06-14 14:39 ` Julien Grall
2019-06-14 15:11 ` Andrii Anisov
2019-06-14 15:24 ` Julien Grall
2019-06-14 16:11 ` Andrii Anisov
2019-06-14 16:20 ` Julien Grall
2019-06-14 16:25 ` Andrii Anisov
2019-06-17 6:27 ` Jan Beulich
2019-06-14 15:42 ` Jan Beulich
2019-06-14 16:23 ` Andrii Anisov
2019-06-17 6:28 ` Jan Beulich
2019-06-18 15:32 ` Andrii Anisov
2019-06-18 15:44 ` Jan Beulich
2019-06-11 16:09 ` Andrii Anisov
2019-06-12 7:27 ` Jan Beulich
2019-06-13 12:17 ` Andrii Anisov
2019-06-13 12:36 ` Jan Beulich
2019-06-11 16:13 ` Andrii Anisov
2019-05-24 18:12 ` [PATCH RFC 1] [DO NOT APPLY] " Andrii Anisov
2019-05-24 18:12 ` [Xen-devel] " Andrii Anisov
2019-05-28 8:59 ` [PATCH RFC 2] " Julien Grall
2019-05-28 8:59 ` [Xen-devel] " Julien Grall
2019-05-28 9:17 ` Andrii Anisov
2019-05-28 9:17 ` [Xen-devel] " Andrii Anisov
2019-05-28 9:23 ` Julien Grall
2019-05-28 9:23 ` [Xen-devel] " Julien Grall
2019-05-28 9:36 ` Andrii Anisov
2019-05-28 9:36 ` [Xen-devel] " Andrii Anisov
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=e30fd795-1f90-5da5-8578-7ce75075d689@gmail.com \
--to=andrii.anisov@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=andrii_anisov@epam.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.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).