[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [RFC 0/6] XEN scheduling hardening
- To: "andrii.anisov@xxxxxxxxx" <andrii.anisov@xxxxxxxxx>, Juergen Gross <JGross@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: Dario Faggioli <dfaggioli@xxxxxxxx>
- Date: Mon, 29 Jul 2019 18:46:06 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=suse.com;dmarc=pass action=none header.from=suse.com;dkim=pass header.d=suse.com;arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mnYhwJGjRdblARjXgQg0zTOfcEkedHDlcSuzKC/fe5k=; b=hcfaH+zr96HuDxV041iCILIJX8fvnlO27rHKwHalXX4PMLI+vXtWTTMKqOQpoWRyCMD3HDFuoGm5w3PA2bCWVW0qrgNlqaY26pUkZobMyr7NxInsukreh0Nf5oDNScaIsEpZC5nCOCAHx9RUBFQTdJvUeul6Wfi16SLFtkMZgtL4Wd5PEOGiAxff62LpGn0fQDO4R5XDHGqbjrjU869NuSbxplEJfaROK7sncGcJyOLiBDGQDR/kCC4PEdIuLVH3uWpaHiCNGm2aWHalUdwHG+tHqT1xYWTWNum6IV387QVXAu2fVBFAj/lgpCOhr8l+KzAg/csaE0c89DsMSlVdmA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hboY9mmj9o/H3d1Kjy7gbisEOAAHAWiuRpzGhzDiwLEVl2Rbj3c9weYqtol3ywR+e70smLmdWAoy8O49kRxyCjgC+hdg2OHHrpRtiFJzB2vBFih7wNTViH3xghStpNliMT3N5Yos/doVWSnxYmYHohUpUG3Zrbyp1GL6xTu6nNEvcoylxObqOGrwxWBwbLZf5VO/CfewpMUPlr/J3ZtA2aHWE9tvR7dnGub9w8RKqBB1NDlJj6JbY8hqQNSRpw2TayP5noyE2tYh3vjFLmta6Nbc5UJdjbsnhL6zO856gvmQSmPT0k7+mCJBdC2kYa1ngbGwpGaINzgnKVMuUWrAzg==
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=dfaggioli@xxxxxxxx;
- Cc: "sstabellini@xxxxxxxxxx" <sstabellini@xxxxxxxxxx>, "andrii_anisov@xxxxxxxx" <andrii_anisov@xxxxxxxx>, "george.dunlap@xxxxxxxxxxxxx" <george.dunlap@xxxxxxxxxxxxx>, "andrew.cooper3@xxxxxxxxxx" <andrew.cooper3@xxxxxxxxxx>, "tim@xxxxxxx" <tim@xxxxxxx>, "julien.grall@xxxxxxx" <julien.grall@xxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>
- Delivery-date: Mon, 29 Jul 2019 18:47:39 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Thread-index: AQHVQ6vC3g8obmh8ekWZSTh5IAudE6bhsdtQgABCjIA=
- Thread-topic: [Xen-devel] [RFC 0/6] XEN scheduling hardening
On Mon, 2019-07-29 at 17:47 +0300, Andrii Anisov wrote:
> On 26.07.19 15:14, Juergen Gross wrote:
> > > >
> > Tasklets are sometimes used to perform async actions which can't be
> > done
> > in guest vcpu context.
> > [...]
> > Like switching a domain to shadow mode for L1TF
> > mitigation,
>
> Sorry I'm not really aware what L1TF mitigation is.
> But
>
> > or marshalling all cpus for stop_machine().
>
> I think I faced some time ago. When fixed a noticeable lag in video
> playback at the moment of the other domain reboot.
>
No, stop_machine() is not about a VM being shutdown/killed/stopped.
It's, let's say, about all the (physical) CPU in the host having to do
something, in a coordinated way.
Check the comment in xen/include/xen/stop_machine.h
> > You don't want
> > to be able to block tasklets, you want them to run as soon as
> > possible.
>
> Should it really be done in the way of breaking scheduling? What if
> the system has RT requirements?
>
It's possible, I guess, that we can implement some of the things that
are done in tasklets (either stop_machine() or something else)
differently, and in a way that is less disruptive for scheduling and
determinism.
But, if it is, it's not going to be as easy as <<let's run tasklet at
domain priority, and be done with it>>, I'm afraid. :-(
Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
