From: Andrii Anisov <andrii.anisov@gmail.com>
To: Julien Grall <julien.grall@arm.com>,
Juergen Gross <jgross@suse.com>,
xen-devel@lists.xen.org
Cc: "Andrii Anisov" <andrii_anisov@epam.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 0/2 for-4.12] Introduce runstate area registration with phys address
Date: Thu, 7 Mar 2019 15:07:56 +0200 [thread overview]
Message-ID: <4df7d4f7-6d69-7913-e33e-7eed45ba9bc7@gmail.com> (raw)
In-Reply-To: <c2a8bc2a-4443-77ae-0764-7e67e06d3474@arm.com>
On 05.03.19 16:30, Julien Grall wrote:
> On 3/5/19 2:11 PM, Andrii Anisov wrote:
>> It is not an annoyance, but inaccurate runstate info passed (actually not passed) to KPTI enabled guests.
> The runstate is actually updated just not for the guest.
That is what I said.
> It will be done at the next context switch.
It *may* be done at one of the next context switches.
> But I am not convinced you will actually see a major differences in number here. Do you have figures?
No, no figures to measure inaccuracy. Yet its existence is obvious.
--
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-03-07 13:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 13:14 [PATCH 0/2 for-4.12] Introduce runstate area registration with phys address Andrii Anisov
2019-03-05 13:14 ` [PATCH 1/2 for-4.12] xen: introduce VCPUOP_register_runstate_phys_memory_area hypercall Andrii Anisov
2019-03-14 8:45 ` Jan Beulich
2019-03-05 13:14 ` [PATCH 2/2 for-4.12] xen: implement VCPUOP_register_runstate_phys_memory_area Andrii Anisov
2019-03-14 9:05 ` Jan Beulich
2019-03-05 13:20 ` [PATCH 0/2 for-4.12] Introduce runstate area registration with phys address Juergen Gross
2019-03-05 13:32 ` Andrii Anisov
2019-03-05 13:39 ` Julien Grall
2019-03-05 14:11 ` Andrii Anisov
2019-03-05 14:30 ` Julien Grall
2019-03-07 13:07 ` Andrii Anisov [this message]
2019-03-05 13:44 ` Juergen Gross
2019-03-05 13:50 ` Andrii Anisov
2019-03-05 13:56 ` Julien Grall
2019-03-07 13:01 ` Andrii Anisov
2019-03-07 14:02 ` Julien Grall
2019-03-07 14:34 ` Andrii Anisov
2019-03-07 15:17 ` Julien Grall
2019-03-07 15:20 ` Julien Grall
2019-03-07 16:16 ` Roger Pau Monné
2019-03-07 16:36 ` Julien Grall
2019-03-07 17:15 ` Roger Pau Monné
2019-03-07 18:00 ` Julien Grall
2019-03-08 6:28 ` Juergen Gross
2019-03-08 10:15 ` Julien Grall
2019-03-08 10:18 ` Juergen Gross
2019-03-08 10:31 ` Julien Grall
2019-03-18 11:31 ` Andrii Anisov
2019-03-18 12:25 ` Julien Grall
2019-03-18 13:38 ` Andrii Anisov
2019-03-21 19:05 ` Julien Grall
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=4df7d4f7-6d69-7913-e33e-7eed45ba9bc7@gmail.com \
--to=andrii.anisov@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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.