[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v3] xen: introduce VCPUOP_register_runstate_phys_memory_area hypercall
- To: Julien Grall <julien.grall@xxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>
- From: Andrii Anisov <andrii.anisov@xxxxxxxxx>
- Date: Tue, 11 Jun 2019 15:40:16 +0300
- Cc: Stefano Stabellini <sstabellini@xxxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "andrii_anisov@xxxxxxxx" <andrii_anisov@xxxxxxxx>, Roger Pau Monne <roger.pau@xxxxxxxxxx>
- Delivery-date: Tue, 11 Jun 2019 12:40:27 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
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@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
