From: Juergen Gross <jgross@suse.com>
To: Andrii Anisov <andrii.anisov@gmail.com>, xen-devel@lists.xen.org
Cc: "Julien Grall" <julien.grall@arm.com>,
"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: Tue, 5 Mar 2019 14:20:05 +0100 [thread overview]
Message-ID: <5a9a160a-042a-1f80-1c3f-af2660f6cb84@suse.com> (raw)
In-Reply-To: <1551791671-21703-1-git-send-email-andrii.anisov@gmail.com>
On 05/03/2019 14:14, Andrii Anisov wrote:
> From: Andrii Anisov <andrii_anisov@epam.com>
>
> Following discussion [1] it is introduced and implemented a runstate
> registration interface which uses guest's phys address instead of a virtual one.
> The new hypercall employes the same data structures as a predecessor, but
> expects the vcpu_runstate_info structure to not cross a page boundary.
> The interface is implemented in a way vcpu_runstate_info structure is mapped to
> the hypervisor on the hypercall processing and is directly accessed during its
> updates. This runstate area mapping follows vcpu_info structure registration.
>
> The series is tested for ARM64. Build tested for x86. I'd appreciate if someone could
> check it with x86.
> The Linux kernel patch is here [2]. Though it is for 4.14.
>
> [1] https://lists.xenproject.org/archives/html/xen-devel/2019-02/msg00416.html
> [2] https://github.com/aanisov/linux/commit/ba34d2780f57ea43f81810cd695aace7b55c0f29
>
> Andrii Anisov (2):
> xen: introduce VCPUOP_register_runstate_phys_memory_area hypercall
> xen: implement VCPUOP_register_runstate_phys_memory_area
>
> xen/arch/arm/domain.c | 59 +++++++++++++++++++--------
> xen/arch/x86/domain.c | 87 ++++++++++++++++++++++++++++------------
> xen/common/domain.c | 95 +++++++++++++++++++++++++++++++++++++++++++-
> xen/include/asm-arm/domain.h | 2 +
> xen/include/public/vcpu.h | 16 ++++++++
> xen/include/xen/domain.h | 5 +++
> xen/include/xen/sched.h | 7 ++++
> 7 files changed, 227 insertions(+), 44 deletions(-)
>
No new features for 4.12. This series will have to wait until 4.13.
Juergen
_______________________________________________
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-05 13:20 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 ` Juergen Gross [this message]
2019-03-05 13:32 ` [PATCH 0/2 for-4.12] Introduce runstate area registration with phys address 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
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=5a9a160a-042a-1f80-1c3f-af2660f6cb84@suse.com \
--to=jgross@suse.com \
--cc=andrii.anisov@gmail.com \
--cc=andrii_anisov@epam.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.