ts.xenproject.org;
> Konrad Rzeszutek Wilk ; Daniel De Graaf
> ; Tim (Xen.org)
> Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
> HYPERVISOR_memory_op to acquire guest resources
>
> Hi Paul,
>
> On 27/10/17 16:19, Paul Durrant wrote:
> >> -Original Message-
...@lists.xenproject.org;
Konrad Rzeszutek Wilk ; Daniel De Graaf
; Tim (Xen.org)
Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
HYPERVISOR_memory_op to acquire guest resources
Hi,
On 26/10/17 16:39, Jan Beulich wrote:
On 26.10.17 at 17:32, wrote:
On 26/10/17 16:26, Jan Beulich wrote:
On
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 26 October 2017 16:27
> To: Paul Durrant
> Cc: Julien Grall ; Andrew Cooper
> ; Wei Liu ; George
> Dunlap ; Ian Jackson ;
> Stefano Stabellini ; xen-de...@lists.xenproject.org;
> Konrad Rzeszutek Wilk ; Daniel De G
ts.xenproject.org;
> Konrad Rzeszutek Wilk ; Daniel De Graaf
> ; Tim (Xen.org)
> Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
> HYPERVISOR_memory_op to acquire guest resources
>
> Hi,
>
> On 26/10/17 16:39, Jan Beulich wrote:
> >>>> On 26.10.17 at 17:
Hi,
On 26/10/17 16:39, Jan Beulich wrote:
On 26.10.17 at 17:32, wrote:
On 26/10/17 16:26, Jan Beulich wrote:
On 17.10.17 at 15:24, wrote:
+/* IN/OUT - If the tools domain is PV then, upon return, frame_list
+ * will be populated with the MFNs of the resource.
+ *
>>> On 26.10.17 at 17:32, wrote:
> On 26/10/17 16:26, Jan Beulich wrote:
> On 17.10.17 at 15:24, wrote:
>>> +/* IN/OUT - If the tools domain is PV then, upon return, frame_list
>>> + * will be populated with the MFNs of the resource.
>>> + * If the tools domain i
On 26/10/17 16:26, Jan Beulich wrote:
On 17.10.17 at 15:24, wrote:
+/* IN/OUT - If the tools domain is PV then, upon return, frame_list
+ * will be populated with the MFNs of the resource.
+ * If the tools domain is HVM then it is expected that, on
+ *
>>> On 17.10.17 at 15:24, wrote:
> @@ -535,6 +588,48 @@ int compat_memory_op(unsigned int cmd,
> XEN_GUEST_HANDLE_PARAM(void) compat)
> rc = -EFAULT;
> break;
>
> +case XENMEM_acquire_resource:
> +{
> +const xen_ulong_t *xen_frame_list =
i Liu ; Stefano
> Stabellini ; xen-de...@lists.xenproject.org; Konrad
> Rzeszutek Wilk ; Daniel De Graaf
> ; Tim (Xen.org)
> Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
> HYPERVISOR_memory_op to acquire guest resources
>
>
>
> On 20/10/17 11:10, Paul Durrant wrote:
> >
Stabellini ; xen-de...@lists.xenproject.org; Konrad
Rzeszutek Wilk ; Daniel De Graaf
; Tim (Xen.org)
Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
HYPERVISOR_memory_op to acquire guest resources
Hi Paul,
On 20/10/17 09:26, Paul Durrant wrote:
-Original Message-
From: J
i Liu ; Stefano
> Stabellini ; xen-de...@lists.xenproject.org; Konrad
> Rzeszutek Wilk ; Daniel De Graaf
> ; Tim (Xen.org)
> Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
> HYPERVISOR_memory_op to acquire guest resources
>
> Hi Paul,
>
> On 20/10/17 09:26, Paul Durra
; xen-de...@lists.xenproject.org; Konrad Rzeszutek
Wilk ; Daniel De Graaf ;
Tim (Xen.org)
Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
HYPERVISOR_memory_op to acquire guest resources
On 19.10.17 at 18:21, wrote:
Looking a bit more at the resource you can acquire from this hypercall
xen-de...@lists.xenproject.org; Konrad Rzeszutek
> Wilk ; Daniel De Graaf ;
> Tim (Xen.org)
> Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
> HYPERVISOR_memory_op to acquire guest resources
>
> >>> On 19.10.17 at 18:21, wrote:
> > Looking a bit more at the
>>> On 19.10.17 at 18:21, wrote:
> Looking a bit more at the resource you can acquire from this hypercall.
> Some of them are allocated using alloc_xenheap_page() so not assigned to
> a domain.
>
> So I am not sure how you can expect a function set_foreign_p2m_entry to
> take reference in that
>>> On 19.10.17 at 18:06, wrote:
> On 19/10/17 16:47, Jan Beulich wrote:
>> I don't understand: The refcounting is to be done by ARM-specific
>> code anyway, i.e. by the implementation of set_foreign_p2m_entry(),
>> not its caller. At least that's what I would have expected.
>
> I thought I said
Hi,
On 19/10/17 17:06, Julien Grall wrote:
On 19/10/17 16:47, Jan Beulich wrote:
On 19.10.17 at 17:37, wrote:
Hi,
On 19/10/17 16:11, Jan Beulich wrote:
On 19.10.17 at 16:49, wrote:
I'd prefer to make the whole thing x86-only since that's the only
platform
on which I can test it, and inde
Hi,
On 19/10/17 16:47, Jan Beulich wrote:
On 19.10.17 at 17:37, wrote:
Hi,
On 19/10/17 16:11, Jan Beulich wrote:
On 19.10.17 at 16:49, wrote:
I'd prefer to make the whole thing x86-only since that's the only platform
on which I can test it, and indeed the code used to be x86-only. Jan
obj
>>> On 19.10.17 at 17:37, wrote:
> Hi,
>
> On 19/10/17 16:11, Jan Beulich wrote:
> On 19.10.17 at 16:49, wrote:
> I'd prefer to make the whole thing x86-only since that's the only platform
on which I can test it, and indeed the code used to be x86-only. Jan
> objected
to this
Hi,
On 19/10/17 16:11, Jan Beulich wrote:
On 19.10.17 at 16:49, wrote:
I'd prefer to make the whole thing x86-only since that's the only platform
on which I can test it, and indeed the code used to be x86-only. Jan objected
to this so all I'm trying to achieve is that it builds for ARM. Please
>>> On 19.10.17 at 16:49, wrote:
>> > I'd prefer to make the whole thing x86-only since that's the only platform
>> on which I can test it, and indeed the code used to be x86-only. Jan objected
>> to this so all I'm trying to achieve is that it builds for ARM. Please can
>> you and
>> Jan reach a
> -Original Message-
[snip]
> >
> > I'd prefer to make the whole thing x86-only since that's the only platform
> on which I can test it, and indeed the code used to be x86-only. Jan objected
> to this so all I'm trying to achieve is that it builds for ARM. Please can
> you and
> Jan reach
Jackson ; Tim
(Xen.org) ; Julien Grall ; Jan Beulich
; Daniel De Graaf ; Roger
Pau Monne
Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
HYPERVISOR_memory_op to acquire guest resources
Hi,
On 10/19/2017 01:57 PM, Paul Durrant wrote:
-Original Message-
From: Julien Grall
Jackson ; Tim
> (Xen.org) ; Julien Grall ; Jan Beulich
> ; Daniel De Graaf ; Roger
> Pau Monne
> Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
> HYPERVISOR_memory_op to acquire guest resources
>
> Hi,
>
> On 10/19/2017 01:57 PM, Paul Durrant wrote:
>
; Ian Jackson ; Tim
(Xen.org) ; Julien Grall ; Jan Beulich
; Daniel De Graaf ; Roger
Pau Monne
Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
HYPERVISOR_memory_op to acquire guest resources
Hi,
On 17/10/17 14:24, Paul Durrant wrote:
Certain memory resources associated with a guest are not
Jackson ; Tim
> (Xen.org) ; Julien Grall ; Jan Beulich
> ; Daniel De Graaf ; Roger
> Pau Monne
> Subject: Re: [Xen-devel] [PATCH v12 05/11] x86/mm: add
> HYPERVISOR_memory_op to acquire guest resources
>
> Hi,
>
> On 17/10/17 14:24, Paul Durrant wrote:
> > Certain mem
Hi,
On 17/10/17 14:24, Paul Durrant wrote:
Certain memory resources associated with a guest are not necessarily
present in the guest P2M.
This patch adds the boilerplate for new memory op to allow such a resource
to be priv-mapped directly, by either a PV or HVM tools domain.
NOTE: Whilst the
On 10/17/2017 09:24 AM, Paul Durrant wrote:
Certain memory resources associated with a guest are not necessarily
present in the guest P2M.
This patch adds the boilerplate for new memory op to allow such a resource
to be priv-mapped directly, by either a PV or HVM tools domain.
NOTE: Whilst the
Certain memory resources associated with a guest are not necessarily
present in the guest P2M.
This patch adds the boilerplate for new memory op to allow such a resource
to be priv-mapped directly, by either a PV or HVM tools domain.
NOTE: Whilst the new op is not intrinsicly specific to the x86
28 matches
Mail list logo
